Re: Exchange Non-Delivery Error

Tech-Archive recommends: Fix windows errors by optimizing your registry



Hi Jeff,

Default the Exchange MTA service is set to disabled and thus not running. Do
you have a user with the email address john@xxxxxxxxxx?

--
Regards,

Marina Roos
Microsoft SBS-MVP
One of the Magical M&M's
www.smallbizserver.net
Take part in SBS forum:
http://www.smallbizserver.net/Default.aspx?tabid=53

"Jeff Teel" <jdteel@xxxxxxxxxxxx> schreef in bericht
news:OuOW7NAeFHA.3376@xxxxxxxxxxxxxxxxxxxxxxx
> I was e-mailed a non-delivery report with the following message in it:
>
> The following recipient(s) could not be reached:
>
> Joe Doe on 6/23/2005 8:31 AM
> The message cannot be delivered due to a configuration error
on
> the server. Please contact your Administrator.
> <mydomain.com #5.3.0 smtp;553 5.3.0 <joe@xxxxxxxxxx>... No
such
> user here>
>
> The event log had more about error which I have pasted below:
>
> Event Type: Error
> Event Source: MSExchangeTransport
> Event Category: NDR
> Event ID: 3015
> Date: 6/23/2005
> Time: 8:30:59 AM
> User: N/A
> Computer: MYSERVERNAME
> Description:
> A non-delivery report with a status code of 5.3.0 was generated for
> recipient rfc822;xxx@xxxxxxxxxx (Message-ID
> <210AC4F571360B48BE2091F1A1B7B023037F6D@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>).
> Causes: Exchange mistakenly attempted mail delivery to an incorrect MTA
> route.
> For more information, click http://www.microsoft.com/contentredirect.asp.
> Solution: Check your route and topology; use the winroute tool to ensure
the
> routes are properly replicated between servers and routing groups.
>
> A search of Microsoft TechNet had this to say about error 5.3.0:
> Exchange 2003 can operate without the message transfer agent (MTA). If
mail
> was mistakenly sent to the MTA, Exchange returns this DSN to the sender.
> This condition is enforced only if you have disabled the MTA service and
> used specific registry settings to disable the MTA/StoreDriver. A default
> configuration strands the misrouted mail on the MTA queues.
>
> I checked to see if the MTA service is running and it is.Exchange is also
> running with a default configuration. Could the same error be generated
> because of a misspelled address? I noticed that the report that I was
> e-mailed about the message not being delivered says "No such user here".
>
> Thanks
> Jeff
>
>


.



Relevant Pages

  • Re: Exchange Non-Delivery Error
    ... I may be mistaking that service ... > Default the Exchange MTA service is set to disabled and thus not running. ...
    (microsoft.public.windows.server.sbs)
  • Re: Major Problem with MTA?
    ... In an environment with one Exchange 2000 server the MTA is not being used ... unless you have one of the following connectors installed (X.400, ... Exchange 2000 use SMTP as it's native transport and does not use the MTA ...
    (microsoft.public.exchange.misc)
  • Re: Event ID: 2000 - MTA service
    ... I was just surprised to get the warning message since other SBS ... the C: drive there the MTA folder is and the MDB folder is on the D: drive. ... Microsoft Exchange MTA service provides Microsoft Exchange ...
    (microsoft.public.windows.server.sbs)
  • Is MTA Running by Defalut?
    ... Exchange server shows "Critical: Service not running". ... I noticed that the MTA ... Solution: Check your route and ...
    (microsoft.public.windows.server.sbs)
  • Re: Repost on Startup Errors
    ... but this is my first Exchange 2003 install. ... old 5.5 server was improperly removed. ... The MTA is running recovery on the internal message database because the MTA ... Unable to initialize the Microsoft Exchange Information Store service. ...
    (microsoft.public.exchange.setup)