XCLN: Macintosh Mail Migration Fails to Import SMTP PAB Entries

 Last reviewed: March 11, 1998
Article ID: Q181939
The information in this article applies to:
  • Microsoft Exchange Server, version 4.0

SYMPTOMS

When you use the Microsoft Mail Gateway Source Extractor to migrate Mac Mail 3.x users to Exchange Server 5.5, it may fail to generate SMTP PAB (personal address book) entries correctly. PAB e-mail address SMTP entries in the .PRI file may be of the following type: 

   USER:FIRSTNAME LASTNAME
with no indication as to what mail type the entries are. The only entries with any type before the e-mail address value may be the local users of the MacMail PO, for example, MSA:NetworkAdmin@Operations.

The X400 addresses may appear as the following: 

   USER:X400First
with no additional fields included in the addresses.

CAUSE

The problem occurs because PC Mail GW and Exchange Mail GW addresses do not conform exactly to the default address format; they have two additional fields. Therefore, these addresses are never recognized as SMTP addresses.

STATUS

Microsoft has confirmed this to be a problem in Exchange Server version 4.0. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information. 

Keywords          : XADM XCLN
Version           : Macintosh:4.0
Platform          : MACINTOSH
Issue type        : kbbug
Solution Type     : kbfix

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

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