7,925 questions
Create a send connector for just this domain and set the good mx record as the smarthost.
Exchange 2010 Fails to send if recipeint domain has any bad MX records
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(156.8, 3%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETM%3C/text%3E%3C/svg%3E)
Timothy M
1
Reputation point
Sometime in May of 2021 our Exchange Server 2010 started to 550 queue time out fail delivering EMail to any external domain that has any bad MX records regardless of pref setting in DNS.
For example if a recipient domain has:
valid pref 10
valid pref 20
invalid pref 999
listed in MX our Exchange server will return
550 4.4.7 QUEUE.Expired; message expired
Not sure what we can do on our end in Exchange or why this symptom started recently.
Exchange | Exchange Server | Management
{count} votes
-
Timothy M 1 Reputation point
2021-06-30T15:56:16.613+00:00 As soon as the invalid MX is removed for recipient domain the mail delivers without issue again
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 22%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKY%3C/text%3E%3C/svg%3E)
Kael Yao 37,746 Reputation points Moderator2021-07-06T08:07:25.863+00:00 Hi @Timothy M
I am writing here to confirm with you how thing going now?
If you have any questions or needed further help on this issue, please feel free to post back.Since Exchange 2010 is quite old and has already reached its end of support, please consider upgrading for better support.
Sign in to comment
2 answers
Sort by: Most helpful
-
Andy David - MVP 157.8K Reputation points MVP Volunteer Moderator2021-06-30T16:40:11.077+00:00 -
Timothy M 1 Reputation point
2021-06-30T16:58:49.453+00:00 While I could do that if/when that domain changes MX it will be an issue again.
Wondering what is causing the Exchange server to now balk over having a single bad MX specified even if the Pref is set low (high value ie 999). It is like the Exchange server recently began to verify each server listed in MX as valid prior to attempting to send the message to the high priority MX server ie pref 10. For years Exchange would try to send using MX in order of pref only trying the lower pref MX if the higher failed. -
Andy David - MVP 157.8K Reputation points MVP Volunteer Moderator
2021-06-30T17:31:29.307+00:00 I've seen this before and seem to recall this was fixed in some CU. Exchange 2010 may not have the fix.
Sign in to comment -
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 98%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
Amit Singh 5,306 Reputation points2021-07-07T10:16:23.207+00:00 You can try these solutions to fix this issue.
- The MX record for your domain might be missing or incorrect.
- Test your MX record and your organization's capacity to send mail using the Verify MX Record and Outbound Connector Test at Office 365 > Mail Flow Configuration in the Microsoft Remote Connectivity Analyzer.
- The SPF record for your domain might be incomplete and might not include all email sources for your domain.
- It might be that the PTR record is not set up or matching per your server's limit.
- DKIM check failed.