@jdstrand thank for the logs you sent me. I see there two interesting things:
1. The traffic for the MMS proxy is going through WiFi instead of the cellular connection. This is a bug in the 03mmsproxy which is executed by NetworkManager. Apparently it does not create routes properly when it needs to resolve a host name. This is a similar bug that the patched ofono I sent you was solving. The difference is that for contexts that support internet+mms at the same time (as T-Mobile's) the routing is made by NM instead of ofono, and that's why the new ofono did not change things.
2. Unusually, the MMSC is accessible via internet, so ubuntu-upload-manager can reach it anyway. However, the server responds with result "HTTP/1.0 302 Found". Apparently this can mean URL re-direction (but the response does specify the same URL as the request!) or a request to change the POST u-u-m used to a GET. But maybe it is just the error it returns when trying to access from wifi instead of using the cellular connection.
I have added lxc-android-config to the bug (03mmsproxy resides there) and ubuntu-dowload-manager (package that includes the uploader) to address point 1 and 2 respectively.
@jdstrand thank for the logs you sent me. I see there two interesting things:
1. The traffic for the MMS proxy is going through WiFi instead of the cellular connection. This is a bug in the 03mmsproxy which is executed by NetworkManager. Apparently it does not create routes properly when it needs to resolve a host name. This is a similar bug that the patched ofono I sent you was solving. The difference is that for contexts that support internet+mms at the same time (as T-Mobile's) the routing is made by NM instead of ofono, and that's why the new ofono did not change things.
2. Unusually, the MMSC is accessible via internet, so ubuntu- upload- manager can reach it anyway. However, the server responds with result "HTTP/1.0 302 Found". Apparently this can mean URL re-direction (but the response does specify the same URL as the request!) or a request to change the POST u-u-m used to a GET. But maybe it is just the error it returns when trying to access from wifi instead of using the cellular connection.
I have added lxc-android-config to the bug (03mmsproxy resides there) and ubuntu- dowload- manager (package that includes the uploader) to address point 1 and 2 respectively.
[1] https:/ /en.wikipedia. org/wiki/ HTTP_302