IMCEAex Messages - NDR Failures

IMCEAex Messages - NDR Failures

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@contoso.com
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

date: Tue, 17 May 2005 06:45:24 -0700 author: Brian

Re: IMCEAex Messages - NDR Failures

What you're seeing are replies using Outlook to old (client cached) entries of some of your employees, replies to some of the pre-migration messages, and updates or responses to pre-migration meeting requests.

What you can do to mitigate this is to add the old legacyDN of the migrated users as X.500 proxy addresses of address to the new objects in AD. Messages sent matching any of the criteria suggested above will be matched to an existing user, and delivered accordingly.

Typically, without the mitigation steps the message should result in a immediate NDR of a 5.1.0, 5.1.1 or a 5.1.2 (all user not found diagnostic codes) depending on certain things.

The reason you're not seeing an NDR, and most likely seeing it in two days or your configured timeout period, is because somewhere in your LinkState packet, the old 5.5 site is still referenced in the winroute as a "Deleted_RG_not_found_in_Active_Directory" or actually still an existing site/Routing Group in your winroute. You can verify this by running winroute.exe. This article http://support.microsoft.com/default.aspx?scid=kb;en-us;832281 is a good read, and has a link to a download of winroute.exe.

Hope that helps.

-Ade

"Brian" wrote in message news:FC285011-EB16-44DD-8B19-661B996F0EDA@microsoft.com...
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@contoso.com
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

date: Tue, 17 May 2005 11:54:04 -0400 author: Ade Famoti [MSFT]

RE: IMCEAex Messages - NDR Failures

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@contoso.com
> 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

date: Tue, 17 May 2005 11:41:05 -0700 author: Brian

RE: IMCEAex Messages - NDR Failures

I think I found the resolution for resolving stale link state information. 
I'll plan to shutdown all exchange services and WMI during our maintenance 
window and bring the master up first.

Does this sound right?

"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@contoso.com
> 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

date: Tue, 17 May 2005 13:59:38 -0700 author: Brian

Re: IMCEAex Messages - NDR Failures

Yes, that sounds right. You have to shutdown all servers in your org , all at the same time...including the RGmaster.

If that option is not feasible, you can call PSS and they can send you a tool called remonitor.exe and assist you in running it in "injection" mode, which will help this issue also.



"Brian"  wrote in message news:A3F19F10-F512-455D-AAEC-50064865B8E4@microsoft.com...
  I think I found the resolution for resolving stale link state information. 
  I'll plan to shutdown all exchange services and WMI during our maintenance 
  window and bring the master up first.

  Does this sound right?

  "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@contoso.com
  > 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

date: Wed, 18 May 2005 12:04:22 -0400 author: Ade Famoti [MSFT]