asked on

MSExchangeTransport Event ID 3018 error

I recently increased SMTP logging (and other logging) to try to find the source of frequent login errors. Some of them are caused by people trying to use my server to relay spam, and those errors specify a relay failure and a source IP address.

I notice another type of error that I get a few times a day:

MSExchangeTransport Event ID 3018

A non-delivery report with a status code of 5.4.0 was generated for recipient rfc822;gary@internatiionalauthors.com (Message-ID <D814D4924F7341499C0276BCC31F5D14@dasilva.local>). 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.

My server's domain is DASILVA.LOCAL. My public domain name is www.internationalauthors.com. Many of these MSExchangeTransport errors have the same misspelling of my public domain name with an extra letter "i": "internatiionalauthors". I cannot tell from the Event log whether someone from the outside keeps trying to access my server with the misspelled domain name (which doesn't bother me so much) , or if I myself mistyped it in one of my configration files (which does bother me). I don't know where to start looking.

Can anyone suggest where to find the answer? I already checked my HOSTS file, which only has only one line: 127.0.0.1 localhost.

Many thanks.

ASKER CERTIFIED SOLUTION

Radweld

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Gary DaSilva

ASKER

Radweld knew what the likely cause was and explained what to look for. The only hard part (for me) was figuring out where the logs were and how to search them, since I had never done this before.

Gary DaSilva

ASKER

The culprit was a typo that I made when entering my own e-mail address in Symantec Mail Security for Exchange for it to send me notification of errors. Radweld was correct when he said the message originated internally,