no MXs for this domain could be reached at this time, instead of undeliverable?
Updated: 21 May 2010 | 5 comments
This issue has been solved. See solution.
I had a user send emails to two bad email addresses.
He received delay messages for days after it. (he didnt report it to me until day 4)
421 4.4.0 [internal] no MXs for this domain could be reached at this time
When I did a lookup for the domains, they were non-exsistant.
So why didnt BrightMail just send an undeliverable back to him, instaed of retrying for several days?
discussion Filed Under:
Comments
A 400 series error is not
A 400 series error is not permanent / fatal error. So it will keep trying until the time out period has been reached. If a 500 series error was returned that would send a bounce/undeliverable back.
I only glanced at it but it doesnt appear RFC2821 specifys that a DNS failure as a fatal error. Also if a MX record or domain shows up for the domain in the devlivery retry window it would get delivered.
Here is the knowledgebase
Here is the knowledgebase document we have on this:
Title: 'Queue Message: 421 4.4.0 [internal] "no MXs for this domain could be reached at this time."'
Document ID: 2009032512563954
> Web URL: http://service1.symantec.com/SUPPORT/ent-gate.nsf/...
Delivery retry is
configured on the Scanner's Advance tab. Just because there isn't an MX now, doesn't mean that within the delivery retry time one won't appear, or that an A-Record won't become available. Change your delivery retry max if you want SBG to give it up sooner.
May I know where is the
May I know where is the Scanner's Advance tab location?
Hi, the Advanced SMTP
Hi,
the Advanced SMTP settings on the GUI are under Administration -> Hosts -> Configuration -> <hostname> ->SMTP (then go to the bottom of this page) -> click "Advanced Settings" button.
Regards,
Federico
Would you like to reply?
Login or Register to post your comment.