Forum Discussion
email to text gateway now sending blank emails?
I have several people I communicate with via email-to-text. Normally, it works fine.
Over the past couple of weeks, something has changed. When I mail from stat.colostate.edu
(or even gmail.com) to a tmomail address, they receive it fine. When they reply, however,
the message is blank save for this in the body:
---boundaryRMS123--
All mail from @tmomail.net arrives with this line:
Content-Type: multipart/related;Type="text/html";boundary="-boundaryRMS123"
and as late as Sep 8, emails that arrived in my inbox had five parts: the html bit at the top, followed by the text bit and then 3 .gif bits. Sometime after that, it changed and now I get the one line in the body and nothing else.
Any advice is greatly appreciated.
Cheers.
- MaxKeno22Network Novice
Same here ---boundaryRMS123-- just started on 09/29/2023. Text from cell to my work email address???
- DQ4UTransmission Trainee
I just noticed after having to update my cell phone a few days ago all my texts I send to email for backup everything is empty I'm not the only one spoke to people on the phone which was useless went into the store at least one of the employees checked on his phone and yes there is a problem
If I send a message from my email to text messaging that one shows up I don't know what is wrong with T-Mobile
- DogLadyNewbie Caller
This just started this morning (10/1/23) on my phone. After reading that I should use a subject line in plain text, I just resent two text-to-email messages again. Still doesn’t work -- I just got “---boundaryRMS123---” message repeatedly. Any ideas?
- erikjayNewbie Caller
Same issue as of September 28, 2023. All text-to-emails arrive with no message (due to the fact that there is no subject line when sending a text). I hope T-mobile will get this fixed asap. I will call for the 3rd time during normal business hours and hopefully get some answers.
- H_CNewbie Caller
I have a small website for our running club. The runners text their times to the website’s email address after a run. I noticed on Friday 9/29/23 that messages received no longer had Base64 encoding but had ---boundaryRMS123-- instead. If I include a subject field in the text with the runners time as the subject then the message is recognized. How do I decode boundaryRMS123?
Related Content
- 3 years ago
- 2 years ago
- 2 years ago
- 2 years ago