
New Member
•
1 Message
Email to Text is not working
Email to text is not working, the intended recipients are not receiving anything at all, not even an error message. Emailing through Outlook hosted by GoDaddy. The email to email function is working fine, it is just email to text that is not working.
ATTHelp
Community Support
•
221.4K Messages
4 months ago
Hi there @hgmc98 we'll be happy to help you out with email-to-texts messages.
We'd like a bit of context, to better understand the scope of your issue based on your initial message. We do have some questions we would like to ask, so we can look into more troubleshooting options.
We look forward to hearing back from you with the results.
Holcy, AT&T Community Specialist
0
0
CrabSalad
New Member
•
3 Messages
4 months ago
Same issue, AT&T is randomly rejecting identical email to text messages. Using Office365 as our email relay. These messages are all what O365 received in response from AT&T.
worked fine at 4:41 am.
Status: Office 365 successfully sent the message to the following external address:<br/><br/><b>External address:</b> xxxxxxxxxx@txt.att.net
6/2/2023, 4:41 AM | Send external | Message sent to att-e2xms-east.mx.a.cloudfilter.net at 35.172.238.88 using TLS1.2 with AES256
*****
2 hours later at 6:53am, same email to text alert is rejected by AT&T.
Status: Office 365 received the message that you specified, but couldn't deliver it to the recipient (xxxxxxxxx@txt.att.net) due to the following error:<br /><br /><b>Error:</b> 550 5.1.1 <xxxxxxxxxx@txt.att.net> recipient address rejected<br /><br />A non-delivery report (NDR) message was sent to (ORIGINALSENDER). The NDR might provide more details about why the email message wasn't delivered and how to fix the issue.
6/2/2023, 6:53 AM | Fail | Reason: [{LED=550 5.1.1 <xxxxxxxxxx@txt.att.net> recipient address rejected};{MSG=};{FQDN=att-e2xms-east.mx.a.cloudfilter.net};{IP=35.172.238.88};{LRT=6/2/2023 12:53:03 PM}]. OutboundProxyTargetIP: 35.172.238.88. OutboundProxyTargetHostName: att-e2xms-east.mx.a.cloudfilter.net
****
Another 1.5 hours later, working again.
Status: Office 365 successfully sent the message to the following external address:<br/><br/><b>External address:</b> xxxxxxxxxx@txt.att.net
6/2/2023, 8:17 AM | Send external | Message sent to att-e2xms-west.mx.a.cloudfilter.net at 35.82.99.184 using TLS1.2 with AES256
(edited)
0
0
jmendez_RCFCU
New Member
•
4 Messages
4 months ago
We are experiencing this same issue. We have systems that send codes via SMS using the @txt.att.net email address. The messages are not being received.
0
0
MoceriIT
New Member
•
2 Messages
3 months ago
We are experiencing similar issues from a third party system. We were using mms.att.net which worked for several years no issue then a couple months ago some phones stopped receiving the messages or became sporadic. Then a couple weeks ago we switched it to send to the txt.att.net and started working for everyone. Now as of June16th we are no longer receiving our text alerts.
0
CrabSalad
New Member
•
3 Messages
3 months ago
Opened a ticket with AT&T chat. My email to text has been working for a few days now. Hope you are all having better connectivity too.
[ATT] : I have checked that for you , since email upgrading activity is going on, that is the reason you are facing issues with. It was escalated already , they are working on it for you.
[Me] : When can I expect that the email upgrading will be completed?
[ATT] : Once done you will be notified. Also I have placed my request too for you from my end and this is the ticket request I--xxxxxxxx .
[ATT] : It will be completing by today as they are completed the activity , still they are working with the server sync issues.
0
jmendez_RCFCU
New Member
•
4 Messages
3 months ago
Thanks for the update - I hope it works well for you.
0
0