RE: IMCEAex Messages - NDR Failures

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Ok ... so runnign Winroute shows that their are 7 objects with the following:

"Routing Group: [Object not found in Active Directory]"

When viewing the objects, it shows these were decomissioned sites. So that
means that 7 of our 50+ sites were not decommissioned properly.

The real question is how to resolve this issue? I don't see any sites in the
Org .. I did find some remnants of these same sites F/B in the System
Hierarchy. I don't see these sites using ADSI.

Thanks for your assistance!

"Brian" wrote:

> Message was sent to Employee One from Employee Two. The message was sent
> between two users on the same mailbox cluster. The environment has been
> Exchange 2003 fully native for over a year. Previously, we had all Exchange
> 5.5 servers in the environment and used ADMT to migrate users to AD and
> placed an Exchange 2003 server in the same site as the corporate Site. Once
> we had SP1 installed, we migrated across sites to a centralized location.
>
> Every now and then I see emails that fail because for some reason it is
> converting the messages to the IMCEAex format. Notice how the site shows an
> old Exchange 5.5 site that was decom'd over a year ago. I see no references
> on the actual user account. Message tracking reveals that the message tried
> to convert the SMTP address to the old legacy DN.
>
> Can anyone shed some light as to why this occurs and what I can do to
> resolve the issue?
>
> I double checked to make sure Employee Two did not have an old contact in
> his mailbox. I've also confirmed this does not happen most of the time and
> does happen for different employees.
>
> Any help would be much appreciated!
>
>
>
> Reporting-MTA: dns;CDC01MSX01.contoso.com
>
> Final-Recipient:
> rfc822;IMCEAex-_O=Contoso_OU=NANYC01_CN=RECIPIENTS_CN=employee@xxxxxxxxxxx
> Status: 4.4.7
> Will-Retry-Until: Mon, 16 May 2005 18:46:33 -0500
> X-Display-Name: Employee One
>
> -----Original Message-----
> From: System Administrator
> Sent: Mon May 16 19:26:18 2005
> To: Employee Two
> Subject: Undeliverable:Email Limits
>
> Your message did not reach some or all of the intended recipients.
>
> Subject: Email Message
> Sent: Mon May 16 15:46:40 2005
>
> The following recipient(s) could not be reached:
> Employee One on Mon May 16 19:26:18 2005
.

Relevant Pages

  • RE: ADC Connector
    ... My environment is a Windows NT 4 enviroment running exchange 5.5. ... Servers in native mode at certain sites and migrated some of our user ...
    (microsoft.public.exchange.setup)
  • Free/Busy information not replicating
    ... I recently upgraded my Exchange environment from 5.5 to 2003. ... retired my Exchange 5.5 servers over 1 month ago and have been running ... not show up under the scheduling tab of the meeting request, ...
    (microsoft.public.exchange.admin)
  • Re: IMCEAex Messages - NDR Failures
    ... servers in your org, all at the same time...including the ... I'll plan to shutdown all exchange services and WMI during our maintenance ... > between two users on the same mailbox cluster. ... The environment has been ...
    (microsoft.public.exchange2000.transport)
  • IMCEAex Messages - NDR Failures
    ... Message was sent to Employee One from Employee Two. ... between two users on the same mailbox cluster. ... The environment has been ... Exchange 2003 fully native for over a year. ...
    (microsoft.public.exchange2000.transport)
  • Re: Changing User
    ... > The exchange service feeds it's users list from the AD and all other ... >>>> I have an employee who has moved on to bigger and beter ... >>>Microsoft Most Valuable Professional, Microsoft's Windows ... >> Server Systems ...
    (microsoft.public.backoffice.smallbiz2000)