XADM: Latency Reading Alternate Recipient Information

Last reviewed: January 20, 1998
Article ID: Q176647

The information in this article applies to:

Microsoft Exchange Server versions 4.0, 5.0, and 5.5

When you configure a mailbox with alternate recipients, or you change alternate recipient information, the change in data may not be reflected immediately. This occurs because the Message Transfer Agent (MTA) caches the data with a ten-minute latency; this is by design. The processing overhead required to automatically detect these changes is too great to justify the benefit. This process is never guaranteed to be 100 percent accurate in any case, because the data can take some time to replicate to all directory databases in the site.

Keywords          : XADM
Version           : WINDOWS:4.0,5.0,5.5
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbworkaround

================================================================================

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: January 20, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.