How did it go for you?
Hello @hackman238
Apologies for not supplying the MMS logs earlier.
These are the logs from mms-egine.log
Is this line relevant?
2024-04-24 15:24:51 [mms-task-send] ERROR: Missing Message-ID
Do note, that I had just replaced the T-Mobile SIM card with a new one, a fresh one that had been only used on the Sony Xperia 10 III at hand.
Also, on the same phone, I can receive media MMS, but I cannot send any media MMS.
Thank you
2024-04-24 15:24:19 [mms-engine] Version 1.0.81 starting
2024-04-24 15:24:19 [mms-engine] Attaching to system bus
2024-04-24 15:24:19 [dbusaccess] Parsing "1;group(privileged)=allow"
2024-04-24 15:24:19 [ofonoext] Bus connected
2024-04-24 15:24:19 [mms-engine] Bus acquired, starting...
2024-04-24 15:24:19 [ofonoext] Name 'org.ofono' is owned by :1.9
2024-04-24 15:24:19 [mms-engine] Acquired service name 'org.nemomobile.MmsEngine'
2024-04-24 15:24:19 [ofonoext] Interface version 8
2024-04-24 15:24:19 [mms-ofono] Modem '/ril_0'
2024-04-24 15:24:19 [mms-connman-nemo] Default SIM at /ril_0
2024-04-24 15:24:19 [mms-ofono] Name 'org.ofono' is owned by :1.9
2024-04-24 15:24:20 [mms-ofono] 2 modem(s) found
2024-04-24 15:24:20 [mms-ofono] SIM ril_0 is present
2024-04-24 15:24:49 [dbusaccess] Parsing /proc/6551/status
2024-04-24 15:24:49 [mms-attachment] /tmp/mms_obEIvB/mms2024-04-24T152419/msg/4258/encode/t-2-4_4937441879_o.gif: image/gif; name=t-2-4_4937441879_o.gif
2024-04-24 15:24:49 [mms-attachment] /tmp/mms_obEIvB/mms2024-04-24T152419/msg/4258/encode/2.txt: no conversion required
2024-04-24 15:24:49 [mms-attachment] /tmp/mms_obEIvB/mms2024-04-24T152419/msg/4258/encode/2.txt: text/plain; charset=utf-8; name=2.txt
2024-04-24 15:24:49 [mms-attachment] /tmp/mms_obEIvB/mms2024-04-24T152419/msg/4258/encode/smil: application/smil; charset=utf-8; name=smil
2024-04-24 15:24:49 [mms-dispatcher] Encode[4258] READY
2024-04-24 15:24:49 [mms-settings-dconf] Attaching to /imsi/310260313386119/mms/
2024-04-24 15:24:49 [mms-settings-dconf] max-message-size = 1048576
2024-04-24 15:24:49 [mms-task-encode] Created /tmp/mms_obEIvB/mms2024-04-24T152419/msg/4258/m-send.req (43527 bytes)
2024-04-24 15:24:49 [mms-task] Encode[4258] READY -> WORKING
2024-04-24 15:24:49 [mms-task] Encode[4258] WORKING -> DONE
2024-04-24 15:24:49 [mms-dispatcher] Encode[4258] DONE
2024-04-24 15:24:49 [mms-dispatcher] Send[4258] READY
2024-04-24 15:24:49 [mms-task] Send[4258] READY -> NEED_CONNECTION
2024-04-24 15:24:49 [mms-connection-nemo] MMS modem path /ril_0
2024-04-24 15:24:49 [mms-ofono] ril_0: not attached
2024-04-24 15:24:49 [mms-connection-nemo] MMS context /ril_0/context2
2024-04-24 15:24:49 [mms-connection-nemo] MessageProxy: 10.188.239.145
2024-04-24 15:24:49 [mms-connection-nemo] MessageCenter: http://10.188.239.145/mms/wapenc
2024-04-24 15:24:49 [mms-connection-nemo] Activate /ril_0/context2
2024-04-24 15:24:49 [mms-ofono] Activating /ril_0/context2
2024-04-24 15:24:49 [dbusaccess] Parsing /proc/7508/status
2024-04-24 15:24:50 [mms-ofono] Settings.Interface: rmnet_data2
2024-04-24 15:24:50 [mms-ofono] Settings.Method: static
2024-04-24 15:24:50 [mms-ofono] Settings.Address: xx.xx.202.31
2024-04-24 15:24:50 [mms-ofono] Settings.Netmask: 255.255.255.192
2024-04-24 15:24:50 [mms-ofono] Settings.Gateway: xx.xx.202.32
2024-04-24 15:24:50 [mms-ofono] Settings.DomainNameServers: 10.177.0.34 10.177.0.210
2024-04-24 15:24:50 [mms-ofono] Interface: rmnet_data2
2024-04-24 15:24:50 [mms-connection-nemo] Interface: rmnet_data2
2024-04-24 15:24:50 [mms-ofono] IPv6.Settings.Interface: rmnet_data2
2024-04-24 15:24:50 [mms-ofono] Context /ril_0/context2 is active
2024-04-24 15:24:50 [mms-connection-nemo] Connection 310260313386xxx opened
2024-04-24 15:24:50 [mms-dispatcher] 310260313386119 OPEN
2024-04-24 15:24:50 [mms-dispatcher] Send[4258] NEED_CONNECTION
2024-04-24 15:24:50 [mms-task-http] MMS interface address xx.xx.202.31
2024-04-24 15:24:50 [mms-task-http] MMS proxy 10.188.239.145
2024-04-24 15:24:50 [mms-task-http] /tmp/mms_obEIvB/mms2024-04-24T152419/msg/4258/m-send.req (43527 bytes) -> http://10.188.239.145/mms/wapenc -> /tmp/mms_obEIvB/mms2024-04-24T152419/msg/4258/m-send.conf
2024-04-24 15:24:50 [mms-transfer-list] Transfer /msg/4258/Send started
2024-04-24 15:24:50 [mms-task] Send[4258] NEED_CONNECTION -> TRANSMITTING
2024-04-24 15:24:50 [mms-ofono] Settings.Netmask: 255.255.255.255
2024-04-24 15:24:50 [mms-transfer-list] Update flags => 0x11
2024-04-24 15:24:50 [mms-ofono] IPv6.Settings.Address: xxxx:fb90:b720:cea8:e8ba:dea8:c583:5258
2024-04-24 15:24:50 [mms-ofono] IPv6.Settings.Gateway: xxxx:0000:0000:0000:10a1:d38c:f388:2f15
2024-04-24 15:24:50 [mms-ofono] IPv6.Settings.PrefixLength: 64
2024-04-24 15:24:50 [mms-ofono] IPv6.Settings.DomainNameServers: xxxx:976a:0000:0000:0000:0000:0000:0009 xxxx:976a:0000:0000:0000:0000:0000:0010
2024-04-24 15:24:51 [mms-task-http] HTTP status 200 [application/vnd.wap.mms-message] 18 byte(s)
2024-04-24 15:24:51 [mms-task] Send[4258] TRANSMITTING -> DONE
2024-04-24 15:24:51 [mms-transfer-list] Transfer /msg/4258/Send finished
2024-04-24 15:24:51 [mms-task-send] ERROR: Missing Message-ID
2024-04-24 15:24:51 [mms-dispatcher] Send[4258] DONE
2024-04-24 15:25:01 [mms-connection-nemo] Deactivate /ril_0/context2
2024-04-24 15:25:01 [mms-ofono] Deactivating /ril_0/context2
2024-04-24 15:25:01 [mms-ofono] IPv6.Settings.PrefixLength: 0
2024-04-24 15:25:01 [mms-ofono] Interface: <none>
2024-04-24 15:25:01 [mms-ofono] Context /ril_0/context2 is not active
2024-04-24 15:25:01 [mms-dispatcher] 310260313386119 CLOSED
2024-04-24 15:25:01 [mms-connection-nemo] Released /ril_0
2024-04-24 15:25:01 [mms-engine] All done
i am also TMO in USA on 10III. i also cannot send MMS. receive works fine, but only when connected to wifi.
i suspect IPv6 issues. ive tried many combinations of settings/proxies/IPs/etc (10.188.239.158 seems to work best) and none have ever worked for me in 4.5.
however, mms send USED to work, before 4.5, but only OFF the wifi. (back then, there was the permanent-retry-failure bug, which was the worst, so this is at least better.)
…but reflashing 4.4 did not work, so something may have changed on T-Mobile’s side in the mean time.
as an aside, T-Mobile Digits works quite well in SFOS android-app-support with microg, and this is how i send the occasional MMS message when i have to.
I am also on TMO in USA on 10III. My MMS send and receive works just fine. I’m sorry to sound like a broken record, but I have additional data points that appear to support my theory as posted in previous messages.
When I traveled out of the country and came back, upon landing at the airport I received another automatic message from TMO with the settings for their network. MMSes failed. I put back in the settings I posted a few years ago in this thread and MMS still didn’t work. I called TMO, go through the painful process of speaking with a Tier-1 technician who has no idea what is going on. Eventually they relent and submit a ticket for escalation to Tier-2 techs. Within a day or two, MMSes just start working and I usually find out from someone sending me a pic or group chat.
Once I successfully receive one, I then send one. That works and I move on with life.
This is on cellular. I rarely use WiFi.
A couple of months ago, something happened on the TMO end. I hadn’t left the country or changed anything and I spontaneously couldn’t send/receive photos, though group texts appeared to be working. After multiple reboots and 24 hours of messing with it, I called TMO tech support again. Same rigamarole and Tier-2 ticket. Two days later, mid-day my phone receives a photo MMS that someone had sent. I try again and all is fine.
I am convinced that there is nothing I can do on the phone to make it work. It’s been five or six times now where when this functionality ceases, I call TMO and Tier-2 does something and then it works again. I have asked to have Tier-2 call/text/email me what they do so I can abbreviate the process in the future, but that has been to no avail. I never hear from them.
My son has a 10II and his MMS send/receive is fine, as well. I always have him, specifically, help with troubleshooting because I always have this lurking concern that TMO will implement some policy wherein our not-officially-supported X10 models will be cut off. But his has always worked when mine fails and we both have the same settings. That’s another data point for why I believe it’s a setting on TMO’s end.
I hope this helps.
And for what it’s worth for U.S. TMO users, though in completely the wrong thread, I have an M365 Exchange account that syncs email and calendar, as well as a second email account with my own on-prem Exchange 2019 server that syncs email, calendar and contacts. Both have worked flawlessly. I don’t know why M365 works well for me, even with 2FA, and doesn’t work for others.
I say this to say that I am reticent to upgrade to a 10V because I almost feel like I have a special phone when I read the trials other U.S.-based users are enduring.
I’m happy to try and help try different things if it will help the community at large. I wish all users could have the max possible usage from their SFOS devices.
1 Like
OK, I should clarify as I now reread through the entire thread. I use the settings below:
T-Mobile
epc.tmobile.com
Dual
None
10.188.239.145
80
http://mms.msg.eng.t-mobile.com/mms/wapenc
4 Likes
AAAARGH. mms send works again! i was using apn=fast.t-mobile.com, as that was the only way i could make it work at all in 4.4, before all the mms fixes in 4.5.
i used the same proxy IP, with port blank, and mmsc=http://10.188.239.145/mms/wapenc.
thank you!!
4 Likes
Yay! I’m so happy to be useful to at least one SFOS person!
6 Likes
Hello,
I confirm that with a Xperia 10 III and Sailfish OS 4.5, It’s almost impossible to send or receive MMS with Mobile Data active.
Since I bought the Xperia 10 III to use SailfishOS (more than 6 months), I’ve tried to send or receive MMS with 2 providers, Bouygues and SFR via Prixtel.
With Bouygues after some months without success, Bouygues send me a SMS about a technical problem, after that It was possible to send and receive MMS but it’s take some long minutes.
But with SFR via Prixtel, nothing.
For Bouygues and SFR all parameters was tested.
After the update of SailfishOs some weeks ago, sending and receiving few MMS was possible, but it always takes some minutes. Just after, I’ve try to restore the configuration to the default values and after nothing. With Bouygues, after the update, some few MMS could be sent and received but after it was impossible.
Now, I’ve stopped the Mobile Data and I can send and receive the MMS without any problems and this operations are fast.
Just now, I’ve activate the Mobile Data and send from an other phone a MMS. After some minutes, the MMS is always “Waiting”. I’ve canceled the downloading, stop the Mobile Data and ‘Retry’ the reception of the MMS, the MMS wais immediately downloaded.
The test was done from my Xperia 10 III (SailfishOS) to the XPeria 10 III (itself) or with the WPeria and other smartphones or old phones.
It"s not a problem with SFR or Bouygues because there is no problem with Ubuntu Touch on a Xiaomi Poco F1.
At this point, for me with a Sony Xperia 10 III :
- it is necessary to stop the Mobile Data to send or receive a MMS;
- the operator is not the problem;
- build 4.5.0.25 (Struven ketju), Device adaptation 1.0.1.23;
- the configuration of the ‘Data access point’ or ‘MMS access point’ isn’t the problem, the last try was ‘Protocol: Dual’;
- [EDIT] after few minutes, I can receive a MMS but I can’t send one
[Edit] Thank you for the tip about ‘Mobile data’ ==> The tip was not a permanent solution.
I just chime in here without any great knowledge about these topics, and with my input probably not being the solution to the particular issues discussed here. But for somebody who encounter MMS problems it may at some time be useful to know about the following matters that previously has prevented MMS from working on my SFOS phone:
- In the SMS app settings there is a setting for Maximum message size. Setting this to extra large once solved my problems. (Can be carrier specific issues.)
- My phone had a twin SIM card that per definition from the carrier would not receive MMS. (also likely carrier specific.)
Hey @teleshoes and @Ras72 , you helped me too!! I also noticed my send/receive was cutting out all of a sudden, much more so than the usual rigamarole.
These settings just work – thank you so much for sharing!
And that’s at least two SFOS people you are useful to 
2 Likes
In the SMS app settings there is a setting for Maximum message size. Setting this to extra large once solved my problems. (Can be carrier specific issues.)
Thank you @espen for this, modification done.
After a shutdown and a power on after one day of delay, the MMS could be sent when the ‘Mobile data’ is off.
This seems to be a stable situation. The MMS are sent and receive without troubles.
If the ‘Mobile data’ is active during the reception of a MMS, to stop the ‘Mobile data’ allow the reception of the MMS.
This is tested without the @espen 's advice.
The network is SFR via Prixtel.
Thank you 
I’ve found that canceling the download & restarting it helps the first time, helps.