Notices

Wut?
That is like mixing fixed definitions (house vs mice or a bed is a pillow or ...). Unbelievable!

And: I never had a full-sized SIM phone (started with S4/2110).

Have had some family issues so I have been unable to test. I am contemplating hiring a programmer (I know some but this is beyond my scope) provided it is reasonable, to update fmms for the good of the community.

Since I don't know a whole lot about MMS protocols and the seperate data connections, but still want a way to send mms, for a temp fix I am developing a set of 3 python scripts.

When opened the "MMS Sender" Script will utilize smtplib to login to my gmail. It will seek user input of a name which it plugs into a contacts script and return all the contact info for the contact.

The user then enters the phone number which is run through the provider script and http://www.freecarrierlookup.com/
to return the MMS provider email.

This email is then plugged into an smtp email, the attachment selected and the email/MMS sent.

So in theory MMS can still be sent with only a couple steps to the user. Currently I have the contacts search done, and a good portion of the smtp/email script done

Nice approach.

But what about pestering provider of receivers why your MMS does not get delivered?
If you provide them answer of your provider that everything is sent out they should react and check on their side.
Possibly you may also aks your friend(s) to do so either.

I can try...but I'm not sure I will make much progress. I will pursue it, but you know how providers can be, I have no doubt it will turn into a blame war between the two.

If anyone else is interested I should have the scripts ready in a week or so and can provide them to others for improvement/modification.

It will also likely contain 4 scripts:
mms will open smtp and call all the others
contacts will lookup/return contact info
provider will lookup mms email and import it to smtp
attach will call the file explorer for the picture/file and import to smtp

it appears fmms is now fully broken on tmobile. all incoming mms say (push) and don't retreive.

this may be the end for my N900

You got latest revision from devel repo, right?
That one has a "logger" in case the incoming MMS cannot be decoded. Please have a read a few pages back (sorry, of course in the newer FIX thread) and see if you can retrieve that raw MMS.

I can confirm Swordfish II's comment, as of February 24 I can no longer download MMS messages. They come through ok in the push folder but it hangs and fails when retrieving the message

Here's the full log dump after loading fMMS and then attempting to retrieve a message from 2/27:

http://pastie.org/pastes/9989551/tex...decy6hb5wqlqaq

I tried connecting directly to http://snq2mosget.msg.eng.t-mobile.com/mms/wapenc and received a 501, however that could be any number of issues/missing headers that I don't have time now to test.

My hunch is that T-Mobile killed support for this, shut the machines down, or just have a server error that no one has noticed or fixed.

Reads as timeout, no access to given URls.
First guess is they changed settings for MMS retrieval. Did you check latest settings with provider (speaking about fMMS or fAPN settings)? proxy, msc, ...

Does it happens only to me that every mms received fails with "impossible to retrieve" even if in the .fmms/mms/XXXXX/ folder are present all the message parts perfectly downloaded and decoded?