XFOR: Connector MTA Appears to Collect Mail It Shouldn't

Last reviewed: April 21, 1997
Article ID: Q133401

The information in this article applies to:

Microsoft Exchange Server, version 4.0

SYMPTOMS

Under certain circumstances, an MS Mail connector (PC) MTA on a Microsoft Exchange Server computer appears to collect messages that it shouldn't. An event entry similar to the following is logged:

   Category:  Moved In
   Description:
   Date: 05/03/95
   Time:  18:43
   Message ID: 00000032
   Size: 1235
   FROM:  NETWORK/PO1/USER03
   TO:    NETWORK/PO3/USER45

CAUSE

This is by product design.

MORE INFORMATION

The log entry above is generated when a message is sent from PO1 to PO3, indirectly through PO2. In the example, PO2 also happens to be the hub connecting other postoffices to Microsoft Exchange.

The sample message is in error since no mail was actually moved into the Microsoft Exchange server. A similar message will appear if the connector MTA polls a postoffice that has messages queued up, waiting to be moved by an additional instance of the MTA.

Additional query words: message transfer agent (MTA) External
Keywords : kbenv XFOR
Version : 4.0
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 21, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.