03-22-2019 8:44 AM
We are seeing all email to txt messages sent via the @mms.att.net domain getting deferred and eventually fail. The reply message indicates there may be an issue with your servers:
status=deferred (host mx3a.txt.att.net[184.108.40.206] said: 452 4.1.0 <email@example.com> requested action aborted: try again later (in reply to MAIL FROM command ))
We are receiving this message from the following relay servers:
Can you please let me know if there is something we need to do on our side to get these messages through?
03-23-2019 9:37 AM
We're happy to help provide assiatnce with your inquiry!
To get started, are you having issues with using the email-to-text feature? Have you been experiencing this error for quite some time?
Fill us in more details so we can take a look.
Dwight, AT&T Community Specialist
03-25-2019 6:49 AM
Yes, this pertains to the email to txt feature. It has been happening for quite some time. Since at least January. This has been an issue for others as well as indicated in this thread: https://forums.att.com/t5/Data-Messaging-Features-Internet/Email-to-Text-gets-452/m-p/5779924?advanc...
03-25-2019 7:27 AM
We'd be more than happy to take a closer look into why Email-to-text has stopped working for you. We'll need some more details in order for us to better assist you. Have you made sure that you're sending the emails to the correct cell phone number, and that the phone number is formatted properly with the correct @firstname.lastname@example.org for text/picture or video messages? Also, what kind of email domain are you using? Are the receivers of these text messages using the default messaging app on their cell phone, or a 3rd party messaging app? Please let us know. We'll be patiently awaiting your response.
Sean, AT&T Community Specialist
03-25-2019 7:49 AM
As far as I know the recipient's cell number/address is correct and they are using the default messaging app. We have thousands of recipients we send to each day across multiple vendors, and it appears only those sent to the @mms.att.net domain are failing. My suspicion is that these messages may be txt but for whatever reason are being sent via the @mms.att.net domain. Has there been a somewhat recent change in message format enforcement that would cause txt formatted email-to-txt messages sent via mms.att.net to fail where they had previously been successful?
03-25-2019 8:46 AM
Thank you for informing us. When composing a new email to send to a 10-digit wireless number, you will only use @mms.att.net for picture and video email-to-text messages. For standard email-to-text messages, you will need to use @txt.att.net. Let us know if this helps.
Sean, AT&T Community
04-24-2019 8:23 AM
Our issue is resolved (for now). We were being rate limited due to sending approx. 10,000 messages daily. After several messages to email@example.com the rate limiting has been lifted and messages are being delivered as expected.
Visit these related resourcesView Text Message Help!