Microsoft KB Archive/292244

= XCON: Sending Mail to Alternate Recipient May Cause an NDR =

Article ID: 292244

Article Last Modified on 2/20/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-



This article was previously published under Q292244





SYMPTOMS
When a Microsoft Exchange Server 5.5 user in one site sends mail to a mail-enabled user in another site who has an alternate recipient in the same site that the sender is in, the message may generate the following non-delivery report (NDR):

-Original Message- From: System Administrator Sent: Wednesday, February 28, 2001 5:07 PM To: Jane A Subject: Undeliverable: test mail

Your message did not reach some or all of the intended recipients.

Subject: test mail Sent: 2/28/01 5:07 PM

The following recipient(s) could not be reached:

Jane A on 2/28/01 5:07 PM The recipient was detected looping within the message transfer service The MTS-ID of the original message is: c=US;a= ;p=EX;l=JET40SP6-010228220658Z-194 MSEXCH:MSExchangeMTA:A:JET40SP6. Here Site A is Exchange 5.5 site and Site B is Exchange 2000 site.

This problem also occurs when you &quot;backbone&quot; between Exchange Server 5.5 sites over Exchange 2000 sites, for example:

site A -- ADC -- site B -- ADC -- site C

In this scenario, sites A and C are Exchange Server 5.5 sites and site B is an Exchange 2000 site. If a user in site A sends an e-mail message to a user in site C who has an alternate recipient defined in site A, the alternate recipient receives the e-mail message, but the sender may also receive the NDR that is described in this section.



RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack

The English version of this fix should have the following file attributes or later:

Component: Transport Core



STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 1.

Keywords: kbbug kbexchange2000presp1fix kbfix kbqfe KB292244

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.