Products
Applications
Support
Company
How To Buy
Skip to main content (Press Enter).
Sign in
Skip auxiliary navigation (Press Enter).
Register
Skip main navigation (Press Enter).
Toggle navigation
Search Options
Home
My Communities
Communities
All Communities
Enterprise Software
Mainframe Software
Symantec Enterprise
Blogs
All Blogs
Enterprise Software
Mainframe Software
Symantec Enterprise
Events
All Events
Enterprise Software
Mainframe Software
Symantec Enterprise
VMware
Water Cooler
Groups
Enterprise Software
Mainframe Software
Symantec Enterprise
Members
Messaging Gateway
View Only
Community Home
Threads
Library
Events
Members
Back to discussions
Expand all
|
Collapse all
sort by most recent
sort by thread
421 4.4.0 [internal] no MXs for this domain could be reached at this time........
Jump to
Best Answer
Migration User
Mar 19, 2010 08:37 AM
I have the SBG version 8.0.3-11 running on VmWare ESX4. Getting lots of error of this kind "421 4.4.0 ...
Migration User
Mar 19, 2010 10:47 AM
Are these mails to legitimate domains? I am thinking may be these mails are NDRs (mail from MAILER-DAEMON) ...
SSE-JDavis
Mar 19, 2010 11:20 AM
Yeah, they are most likely NDRs we are trying to send to fake email addresses You should consider setting ...
Migration User
Mar 24, 2010 04:53 AM
No they are not the NDRs but they are the legitimate mails to legitimate domains. Domains like yahoo.com, ...
Migration User
Mar 24, 2010 10:44 AM
Best Answer
Hi Prashant, Please take a look at the following KB article for some suggestions: http://service1.symantec.com/SUPPORT/ent-gate.nsf/docid/2009032512563954 ...
1.
421 4.4.0 [internal] no MXs for this domain could be reached at this time........
0
Recommend
Migration User
Posted Mar 19, 2010 08:37 AM
Reply
Reply Privately
Options Dropdown
I have the SBG version 8.0.3-11 running on VmWare ESX4. Getting lots of error of this kind "421 4.4.0 [internal] no MXs for this domain could be reached at this time" and daily around 200-300 mails are stucking in the Delivery queue. Can anyone help me to resolve this issue...... Thanks in advace for the solution and efforts for this discussion..
2.
RE: 421 4.4.0 [internal] no MXs for this domain could be reached at this time........
0
Recommend
Migration User
Posted Mar 19, 2010 10:47 AM
Reply
Reply Privately
Options Dropdown
Are these mails to legitimate domains? I am thinking may be these mails are NDRs (mail from MAILER-DAEMON) going out to bogus domains.
Regards,
Adnan
3.
RE: 421 4.4.0 [internal] no MXs for this domain could be reached at this time........
0
Recommend
Broadcom Employee
SSE-JDavis
Posted Mar 19, 2010 11:20 AM
Reply
Reply Privately
Options Dropdown
Yeah, they are most likely NDRs we are trying to send to fake email addresses You should consider setting up an LDAP source so we will not accept messages for users that don't exist.
4.
RE: 421 4.4.0 [internal] no MXs for this domain could be reached at this time........
0
Recommend
Migration User
Posted Mar 24, 2010 04:53 AM
Reply
Reply Privately
Options Dropdown
No they are not the NDRs but they are the legitimate mails to legitimate domains.
Domains like yahoo.com, icicibank.com, etc....
5.
RE: 421 4.4.0 [internal] no MXs for this domain could be reached at this time........
Best Answer
0
Recommend
Migration User
Posted Mar 24, 2010 10:44 AM
Reply
Reply Privately
Options Dropdown
Hi Prashant,
Please take a look at the following KB article for some suggestions:
http://service1.symantec.com/SUPPORT/ent-gate.nsf/docid/2009032512563954
Regards,
Adnan
×
New Best Answer
This thread already has a best answer. Would you like to mark this message as the new best answer?
Copyright 2019. All rights reserved.
Powered by Higher Logic