smtp communication problem

Case Study - SMTP communication problem and NDR

Situation: When the client attempt to send a message to a recipient and he receive the non-delivery report (NDR) like these:

1. From: System Administrator > Sent: Thursday, May 24, 2001 6:41 PM > To: blin@chicagotech.net > Subject: Undeliverable: Delivery Status Notification (Failure)

Your message did not reach some or all of the intended recipients.

Subject: Sent: 5/24/01 6:41 PM The following recipient(s) could not be reached: > > blin@chicagotech.net on 5/24/01 6:41 PM > Your mail system could not find a way to successfully > communicate with the destination system. Please notify your > administrator. <mail.ms-mvps.com> #5.5.0 >

2. You may also receive an error code of #5.5.4 Transaction failed.

Additionally, the Windows Event viewer may contain an event 4000 or 4001 that is similar to the following: Event Type: Warning Event Source: MSExchangeTransport >Event ID: 4000 >Description: Message delivery to the remote domain ' FQDN Domain Name ' failed for the following reason: >SMTP protocol error

3. Or SMTP communication problem with the recipient's email server with other error codes: 554 Relay access denied, 553 mail rejected due to excessive spam, 554 Validating Sender,

Troubleshooting: When we tried to access the system remotely, we could not. That told us the problem is that they are using the dynamic IP. Many companies don't like dynamic IP's and will think you might be a spammer.

Conclusion: If your Network that is connected to the Internet is using a dynamic IP address, you may have to configure Exchange Server to route mail for the nonexistentdomain.com domain through an SMTP connector to a smart host.

Post your questions, comments, feedbacks and suggestions

Contact a consultant