Forum Discussion
boundaryRMS123
I recently upgraded to iphone 15 and now whenever I try to forward a text to someone via email the email is blank except for ---boundaryRMS123---. Can anyone help? I've tried the mail reset and phone reset, turning on/off messages, etc.
I guess I'll thow in my two cents as well. We've used text to email for responding to our company scheduling person for years until it stopped working last week. Email to text still works, just NOT text to email. TMOBILE...please help!!
- AspenroofsRoaming Rookie
MINE TOO! I spent an hour on the phone with support yesterday
- magenta9595035Newbie Caller
Hello - I think this was the result of a software update. My phone did the exact same and I had no clue what happened. I went to the Tmobile store , they had never seen anything like this . So, I called Samsung Tech care. The representative told me there had been a software update. At the time I assumed it was Samsung but, Im not sure after reading this . Anyway- yesterday my phone got a lot of pop ups asking for permission . Allow Message, Allow Voice, Allow camera , etc to have access. I allowed , then tried sending an image and it worked perfectly. I have an older samsung so maybe it took time to work . Not sure who did what , but, now its working . I hope this issue gets resolved for everyone .
- THEONEHARMSENRoaming Rookie
mgpappa wrote:
I use text to email when messaging a friend who doesn't have access to a phone at work. This started happening to me on 9/28 as well. It was perfectly fine beforehand. I went into a T-Mobile yesterday and they reset my network and made adjustments to my settings. Nothing worked.
As of last night 10/4/23, the error was fixed and I am now able to send both photos and normal text to e-mail with no issues. Is your error now fixed too?
- THEONEHARMSENRoaming Rookie
magenta9595035 wrote:
Hello - I think this was the result of a software update. My phone did the exact same and I had no clue what happened. I went to the Tmobile store , they had never seen anything like this . So, I called Samsung Tech care. The representative told me there had been a software update. At the time I assumed it was Samsung but, Im not sure after reading this . Anyway- yesterday my phone got a lot of pop ups asking for permission . Allow Message, Allow Voice, Allow camera , etc to have access. I allowed , then tried sending an image and it worked perfectly. I have an older samsung so maybe it took time to work . Not sure who did what , but, now its working . I hope this issue gets resolved for everyone .
As of last night 10/4/23, the error was fixed and I am now able to send both photos and normal text to e-mail with no issues. Is your error now fixed too?
- THEONEHARMSENRoaming Rookie
As of 9/29/23 I am no longer able to send texts to e-mail addresses. I continue to get the following error: boundaryRMS123
- THEONEHARMSENRoaming Rookie
Dannygirl wrote:
I just got off the telephone with T-Mobile Agent, Quan'Day. She entered a Ticket, # 75239534, she said please give the engineers two to three days to investigate. Hopefully, this will be resolved very soon. Thx
As of last night 10/4/23, the error was fixed and I am now able to send both photos and normal text to e-mail with no issues. Is your error now fixed too?
- fireguy_6364Modem Master
THEONEHARMSEN wrote:
THEONEHARMSEN wrote:
As of 9/29/23 I am no longer able to send texts to e-mail addresses. I continue to get the following error: boundaryRMS123
As of last night 10/4/23, the error was fixed and I am now able to send both photos and normal text to e-mail with no issues. Is your error now fixed too?
just quote one person. when you do the same message to multiple people over and over the system will flag you as a spammer.
- rdr28momRoaming Rookie
THEONEHARMSEN wrote:
THEONEHARMSEN wrote:
As of 9/29/23 I am no longer able to send texts to e-mail addresses. I continue to get the following error: boundaryRMS123
As of last night 10/4/23, the error was fixed and I am now able to send both photos and normal text to e-mail with no issues. Is your error now fixed too?
Sí