KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q235329: XFOR: How to Change an MSMail Custom Recipient to SMTP

Article: Q235329
Product(s): Microsoft Exchange
Version(s): winnt:4.0,5.0,5.5
Operating System(s): 
Keyword(s): exc4 exc5 exc55 kbgraphxlinkcritical
Last Modified: 06-AUG-2002

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Exchange Server, versions 4.0, 5.0, 5.5 
-------------------------------------------------------------------------------

SUMMARY
=======

In some cases you may need to change many custom recipients of one type, for
example Microsoft Mail (MS Mail), to another type of custom recipient, like
Simple Mail Transfer Protocol (SMTP). This article outlines the steps to change
a group of MS Mail custom recipients to SMTP custom recipients.

MORE INFORMATION
================

For additional information about general bulk import and export procedures,
click the article number below to view the article in the Microsoft Knowledge
Base:

  Q155414 XADM: Bulk Import/Export FAQ

To change a group of MS Mail custom recipients to SMTP custom recipients:

1. Export the MS Mail custom recipients to a .csv file that contains all of the
  pertinent headers. You can find a copy of a .csv file that is designed to
  export custom recipients on the Microsoft Exchange Server version 4.0 CD in
  the Support\Samples\Csvs\Custom\Custom.csv folder.

2. Use Microsoft Excel to open the .csv file that you created in step 1.

3. Select the entire file, and sort it by the E-mail Address header.

4. If you only want to change a subset of these custom recipients, delete all of
  the rows except the rows that you want from this file.

5. Delete the E-mail Addresses column.

6. Under the E-mail Address column, delete all of the existing e-mail addresses.
  The addresses are in the following MS Mail format:

  MS:<network>/<postoffice>/<user>

7. Type the primary SMTP addresses in the E-mail Address column in the following
  format:

  SMTP:<alias>@<domain>.com

8. Delete the Imported-From, Obj-Container, and Obj-Dist-Name columns, if they
  exist.

9. Save this .csv file to a different name.

10. Start the Exchange Server Administrator program and on the Tools menu, click
  Directory Import to import the .csv file that you saved in step 9 to the
  target Recipients container.

If you do not have the Microsoft Exchange Server version 4.0 CD, the sample .csv
files are available in a file that you can download. The following file is
available for download from the Microsoft Download Center:

  DownloadDownload Csv.exe now
  (http://support.microsoft.com/download/support/mslfiles/Csv.exe)

Release Date: Sep-11-1998

For additional information about how to download Microsoft Support files, click
the following article number to view the article in the Microsoft Knowledge
Base:

  Q119591 How to Obtain Microsoft Support Files from Online Services

Microsoft scanned this file for viruses. Microsoft used the most current
virus-detection software that was available on the date that the file was
posted. The file is stored on secure servers that prevent any unauthorized
changes to the file.

Additional query words: ccmail gwise notes profs

======================================================================
Keywords          : exc4 exc5 exc55 kbgraphxlinkcritical 
Technology        : kbExchangeSearch kbExchange500 kbExchange550 kbExchange400 kbZNotKeyword2
Version           : winnt:4.0,5.0,5.5
Issue type        : kbhowto

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

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.