ctsmequon
asked on
MSExchangeTransport NDR 3018 error on one user
Hello-
My Exchange server (SBS2003) seems to have developed a problem in the last few days. This server is servicing a small number of users (<10) and has been working properly for a few years. In the last 72 hours, the Exchange server is generating the "MSExchangeTransport NDR 3018" error for every email address that one user tries to send to. All other users are having no problems sending or receiving, and this user can receive messages with no problems. This user can also send and receive using an independent POP3 account that is setup on his instance of MS Outlook.
Here is the error message generated by the server everytime this user sends an email message through the server:
Event Type: Error
Event Source: MSExchangeTransport
Event Category: NDR
Event ID: 3018
Date: 7/8/2009
Time: 12:33:58 PM
User: N/A
Computer: SERVER
Description:
A non-delivery report with a status code of 5.4.0 was generated for recipient rfc822;mcs@eeee.com (Message-ID <FDDA08E3FDE24147AE765C69B
Causes: This message indicates a DNS problem or an IP address configuration problem
Solution: Check the DNS using nslookup or dnsq. Verify the IP address is in IPv4 literal format.
For more information, click http://www.microsoft.com/contentredirect.asp.
Data:
0000: ef 02 04 c0 ï..À
Here is the error message that the user receives in return:
From: System Administrator
Sent: Wednesday, July 08, 2009 12:42 PM
To: user
Subject: Undeliverable: test message
Your message did not reach some or all of the intended recipients.
Subject: test message
Sent: 7/8/2009 12:42 PM
The following recipient(s) could not be reached:
mcs@eeee.com on 7/8/2009 12:42 PM
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.
<domain.com #5.4.0>
I have tried rebooting the workstation and the server with no luck.
Please let me know what suggestions you may have.
Thanks,
CTSMKE
My Exchange server (SBS2003) seems to have developed a problem in the last few days. This server is servicing a small number of users (<10) and has been working properly for a few years. In the last 72 hours, the Exchange server is generating the "MSExchangeTransport NDR 3018" error for every email address that one user tries to send to. All other users are having no problems sending or receiving, and this user can receive messages with no problems. This user can also send and receive using an independent POP3 account that is setup on his instance of MS Outlook.
Here is the error message generated by the server everytime this user sends an email message through the server:
Event Type: Error
Event Source: MSExchangeTransport
Event Category: NDR
Event ID: 3018
Date: 7/8/2009
Time: 12:33:58 PM
User: N/A
Computer: SERVER
Description:
A non-delivery report with a status code of 5.4.0 was generated for recipient rfc822;mcs@eeee.com (Message-ID <FDDA08E3FDE24147AE765C69B
Causes: This message indicates a DNS problem or an IP address configuration problem
Solution: Check the DNS using nslookup or dnsq. Verify the IP address is in IPv4 literal format.
For more information, click http://www.microsoft.com/contentredirect.asp.
Data:
0000: ef 02 04 c0 ï..À
Here is the error message that the user receives in return:
From: System Administrator
Sent: Wednesday, July 08, 2009 12:42 PM
To: user
Subject: Undeliverable: test message
Your message did not reach some or all of the intended recipients.
Subject: test message
Sent: 7/8/2009 12:42 PM
The following recipient(s) could not be reached:
mcs@eeee.com on 7/8/2009 12:42 PM
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.
<domain.com #5.4.0>
I have tried rebooting the workstation and the server with no luck.
Please let me know what suggestions you may have.
Thanks,
CTSMKE
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks guys. The problem turned out to be different than advertised. On your suggestions I looked more closely at the DNS issue, and then discovered that it wasn't that no other users were having this problem, it was that no other users had had to send email outside the company for the last few days. It turns out no one could send email outside the company. My bad. There was a DNS configuration issue associated with a name service server that we were no longer using that had been decommissioned. After I reconfigured DNS, all worked properly. Thanks again for your help.
ASKER