| Issues or Symptoms |
Article Title & Link |
Description or Resolution |
|
| |
|
|
|
| SMTP messages stay in the Outgoing
Messages Awaiting delivery queue until they receive a NDR for certain
domains |
SMTP Messages
Not Being Delivered
to Certain Domains |
The site which the message is destined for is
possibly using reverse zone lookups for security purposes. The Fully
Qualified Domain Name (FQDN) of the Exchange Server computer does not
match its InterNic-registered IP address; hence, the telnet session to
the destination mail server is refused. |
|
| How to test for relay |
SMTP relay behavior
in Windows 2000,
Windows XP, and
Exchange Server |
You can test your SMTP server to
determine if it is configured to relay e-mail messages. |
|
| Receiving 5.5.0
non-delivery reports only from specific domains |
Receiving 5.5.0
non-delivery reports
only from specific
domains in
Exchange2000
Server, in
Exchange 2003,
and in SBS 2003 |
This behavior occurs if the destination
server cannot resolve the domain that you are using as your return
address. For example, if your server's domain is "nonexistentdomain.com,"
and you are trying to deliver a message to a domain called "destinationdomain.com,"
and this domain has Reverse Lookup enabled on its SMTP server, mail
delivery will fail. This occurs because the destination server will
perform a reverse lookup on "nonexistentdomain.com," and then it will
stop the SMTP conversation. |
|
| "The destination server for
this recipient could not be found in Domain Name Service (DNS). Please
verify the email address and retry. If that fails, contact your
administrator. < Host.Domain.tld #5.4.0>" |
You receive an NDR
#5.4.0 when you
send an e-mail
message by using
the SMTP connector
in Exchange Server
2003 |
|
• |
The SMTP
connector is configured to forward e-mail messages to a smart host,
and the SMTP connector has the Queue mail
for remote triggered delivery option
turned on. |
|
• |
The bridgehead server
for the SMTP connector is moved to a different server. |
|
|
| A configuration error in
the e-mail system caused the message to bounce between two servers or to
be forwarded between two recipients. Contact your administrator. |
You Receive a
NDR
When Exchange
2000 Server
Attempts to
Send SMTP Mail |
This issue occurs when loop-back is
detected for DNS resolution. In the loop-back mode, the server is
configured to loop back on itself. |
|
| Some Domains Send NDRs to
an Exchange 2000 Server That Runs Watchguard Firebox Firewall |
Some Domains
Send NDRs to an
Exchange 2000
Server That Runs
Watchguard
Firebox Firewall |
To work around this behavior, disable
the Watchguard Firebox SMTP Proxy service. Watchguard also has a
software update to correct this behavior. To obtain the update, contact
Watchguard support. |
|
| "5.0.0" NDR Occurs When You
Send Push Notifications to an SMTP Carrier |
"5.0.0" NDR Occurs
When You Send
Push
Notifications to an
SMTP Carrier |
This issue can occur if the network
adapter that is located on the intranet is bound before the network
adapter on the Internet. In this case, the name resolution service fails
for the SMTP service as the service tries to resolve an Internet domain
name on the intranet DNS server. |
|
| This article explains how to configure
the SMTP connector. |
How to configure
the SMTP connector
in Exchange 200x |
Exchange 2000 and Exchange 2003 work differently than
Exchange Server 5.5. SMTP is an add-on to Exchange Server 5.5 through
Internet Mail Service. SMTP is native to Exchange 2000 and Exchange
2003. Everything is SMTP-based. The default SMTP virtual server (by
itself) can handle all Internet traffic (inbound and outbound). |
|
