Could you do 'cat /home/user/.fmms/mms/<transactionid>/AAAA' and guess what type it is? (Transactionid is the string below sender in the "main view")
root@n900:~# cat /home/user/.fmms/mms/m5psspdst21efnpf313@/AAAA <smil><head><layout><root-layout width="100%" height="100%" background-color="#FFFFFF"/><region id="Image" width="100%" height="83%" top="0%" left="0%" fit="meet"/><region id="Text" width="100%" height="17%" top="84%" left="0%" fit="scroll"/></layout></head><body><par dur="4000ms"><img src="DSC00747.jpg" region="Image"/><text src="smil.txt" region="Text"><param name="foreground-color" value="#000000"/></text></par></body></smil>
Hmm, did it hang because you changed connection? It really shouldn't - as long as the new connection is up before the actual sending process starts it should be fine, but yes, better error handling is on "the list" as well :)
How long does it get stuck? It got a timeout of about 60 seconds before giving up on connecting to where the MMS is hosted (think it's 60 seconds, might be 20 or 30 :P).
The setting in fMMS is so far only for connecting if no other connection is active (and getting the proxy settings from), not currently possible to have it autoconnect in the background etc, also being looked into how to solve ;)
Thanks for the well structured feedback!
Wheter or not Conversation integration is possible or not time will tell, but most other parts of integrating it with the the OS (share via and stuff like that) should be possible in the future :)