The Sender Verification Error (or Sender Address Verification) occurs when the recipient server performs a MX lookup on the envelope.mail-from address and it fails to locate the MX records for the sending domain. The error can appear 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
We'll explore several ways to resolve this error based on your current Mailgun sending domain!
When configuring any subdomain with Mailgun, we don't require MX records to be used, but we do highly advocate that they are to proactively correct this issue before it begins! As noted above, some pesky email servers check the subdomain in the envelope.mail-from field for MX records and if those records aren't found, then BAM! You'll get hit with a Sender Verification Error in your Mailgun logs. Not to worry though - the fix is easy!
The fix is to simply add Mailgun's MX records to your subdomain! 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'll need to wait the 24-48 hours for them to fully propagate and the error should disappear!
One final tip - If you're still seeing it, please also try adjusting the From field of the message to match the sending domain as well.
On to the root domain approach! In this instance, 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 will be resolved!
These are the final options for resolving the error - It's highly recommended to review and implement the above suggestions before moving on to these! They are:
- 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