XADM: Generated SMTP Addresses for Duplicate Mailboxes

Last reviewed: April 21, 1997
Article ID: Q146455
The Information in this article applies to:
  • Microsoft Exchange Server, version 4.0

SYMPTOMS

When you have multiple users with the same surname and given name, only the first generated SMTP address uses the complete surname and given name combination. All subsequently generated SMTP addresses use their alias and an iteration number.

MORE INFORMATION

The first time that a unique SMTP address is generated for a recipient, the template information from the Configuration container, Site Addressing object, and Site Addressing property page is used to generate the SMTP address. For example, if you set up the SMTP site address to be %s.%g@company.com, the SMTP address will be surname.givenname@company.com.

If you have two or more people with the same surname and given name, every subsequent duplicate name uses the alias for that person and an appended iteration number. For example, the next person with the same name ends up with an SMTP address of:

   gsurname2@company.com

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0. This problem was corrected in the latest Microsoft Exchange Server U.S. Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K


Additional query words:
Keywords : kbbug4.00 kbfix4.00.sp2 kbusage XADM
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.