Hello,
Our application sends emails to text through mandrillapp.com and just recently our clients are reporting that the from address is showing as bounce-md_RANDOMNUMBER @ mandrillapp.com . Mandrill support suggested setting a custom return path header and that works but the from is now showing bounce-md_RANDOMNUMBER @ mail.ourdomain.co . It's very random and some of our messages come through fine showing a from address of info @ ourdomain.com .
Has anyone else seen this, has anyone figured out a workaround. Any help is much appreciated.
Thank you,
Steven
@StevePenn, we are seeing the same thing with messages from our one of our applications which sends out notifications using email to text. Once received via text, the sender's email address, both username and domain, has been modified to "bounce.xxLongRandomNumberxx @ XXXXXX.ourdomain.com".
I doubt that Verizon is going to offer a lot of support as their email-to-text-faqs page (https://www.verizon.com/about/account-security/email-to-text-faqs) says "Email-to-text is not intended for business/non-consumer (also known as A2P) messages" and then lists various providers of Enterprise Messaging solutions.
Your post is the only one I have been able to find in my searches of the internet, but you aren't the only one it's happening to. We don't have a workaround yet. If we figure something out, I will post the update.
Thank you,
Eric
@StevePenn, I contacted our email relay service who confirmed that they were not changing the original sender of the email. They also stated that "Verizon is incorrectly reading the return-path instead of the sender address in the headers." Our email relay service also had the ability to force "maintain return path" .
As I also had a ticket open with Verizon, I went through the troubleshooting steps requested later when the Verizon tech contacted me. They asked me to turn off email-to-text by sending a text to 4040 as the following link shows https://www.verizon.com/about/account-security/email-to-text-faqs. While it was off, Verizon went through the process of "syncing my account". I asked if I could re-enable email-to-text and I was told to "leave it off if you don't want to experience the same issue, leave it disabled." (That is not an option, Verizon! I'm trying to fix email-to-text, not disable it.)
After this, the messages in my chat stopped sending and I was forced to close the chat.
Since the changes made, I have not received any of the text messages which have bounce.LongRandomNumber in the original sender. If I were to guess what fixed it, I would say it's the "maintain return path" that our email relay service enabled. My confidence in Verizon Tech Support is shaken at this point.
Hope this helps!
EricSchmidt
Start a new topic or ask questions in the open forum.
