This error (also called Sender Address Verification) occurs when the recipient server performs an MX lookup on the envelope.mail-from address, then fails to locate the MX records for the sending domain.
You might see this manifest in a few different ways; here are the most common:
- 550 Verification failed for <email@example.com>\nUnrouteable address\nSender verify failed
- Domain of sender address firstname.lastname@example.org does not exist
- 550 550 Verification failed for <email@example.com>
- Unrouteable address Sender verify failed
- Sender address rejected: User unknown in virtual mailbox table
- 452 4.5.2 Could not resolve sender domain
- 450 4.1.8 Sender address rejected: Domain not found
- 505 Your domain has no DNS/MX entries
- 550 550 Requested action not taken: mailbox unavailable invalid DNS MX or A/AAAA resource record
- 550 5.2.0 <firstname.lastname@example.org> From: Domain is invalid. Please provide a valid From: IB506 <http://x.co/srbounce>
- 550 550 5.7.1 Sender ID (PRA) Domain Does Not Exist
Now that we've seen the errors, We'll explore several ways to resolve this issue based on your current Mailgun sending domain.
Seeing This Issue With a Subdomain
When configuring any subdomain with Mailgun, while we don't require MX records to be used, as long as you don't already have incoming mail configured for the domain, we highly recommend pointing your MX records for the domain to Mailgun. Why? Doing so serves to proactively correct the Sender Verification Error issue before it begins - always good to be ahead of the curve!
As noted above, some pesky email servers check the subdomain in the envelope.mail-from field for MX records. If those records aren't found, then you're hit with a Sender Verification Error in your Mailgun logs. All is not lost, however - the fix is quite simple; just set the MX records for the subdomain to Mailgun values!
Once this is completed, the MX lookups of those email servers should be successful and the servers should accept your messages.
The two MX records for Mailgun that will need to be added to your subdomain are:
Once the records have been added, you may need to wait the 24-48 hours for them to fully propagate; following this, the error should disappear.
If for any reason you're still seeing that same error, you can also try adjusting the From field of the message to match the sending domain as well.
Seeing This Issue With a Root Domain
What if you're using a root domain? In this case, your root domain already has your ESP's (Email Service Provider) MX records in place. The best and safest way to quickly resolve this would be to add a subdomain for your Mailgun sending instead.
When the subdomain is added, along with Mailgun's MX records configured for it, the error should be resolved!
NOTE: Always make sure your MX records for a domain only point to one source. Otherwise, servers get confused, and bad things happen when servers get confused.
Still having issues? Not to worry; here are the alternate options for resolving the error. Make sure to note - it's highly recommended to review and implement the above suggestions before moving on to these:
- Turn off sender address verification (this is server-side)
- Add "x-mailgun-native-send: true" to the header of your message to turn off sender address rewriting
- Create a catch_all with the service where you receive email so that, when the recipient server checks, verification it will pass
If any questions arise, just reach out to our Support team via the Support tab in your Mailgun control panel!