Chapter 5
Migrating from Microsoft Mail for AppleTalk Networks
To migrate users from Microsoft Mail for AppleTalk Networks to Microsoft Exchange Server, use the MS Mail (AppleTalk) source extractor. The source extractor copies information from MS Mail (AppleTalk) version 3.0 or later to migration files. You then import these migration files to Microsoft Exchange Server by using the Migration Wizard. 
The MS Mail (AppleTalk) source extractor copies the following information to migration files: account information, messages, message attachments, personal address books (PABs), and Schedule+ appointments and notes. 
The source extractor cannot migrate gateway recipients. It also cannot migrate groups to distribution lists, though it can provide group membership information, which can be used to migrate groups.
To perform the migration, you will need to:
	Prepare for migration.
	Migrate custom forms.
	Migrate groups.
	Migrate mailboxes.
	Migrate MS-DOS clients.
	Import the migration files.

If you are performing a multiphase migration, you will also need to:
	Connect the MS Mail (AppleTalk) and Microsoft Exchange Server sites.
	Support the native gateway during migration.
	Convert gateway recipients.
	Synchronize directories between MS Mail (AppleTalk) and Microsoft Exchange Server.

Preparing for Migration
Preparing to migrate from MS Mail (AppleTalk) to Microsoft Exchange Server involves the following activities:
	Deciding whether to do a single-phase or multiphase migration.
	Updating client hardware if necessary to meet hardware requirements. 
	Asking users to move their folders to the server with the information to be migrated.
	Setting up your Microsoft Exchange Server site. For information, see the Microsoft Exchange Server Concepts & Planning Guide and the Microsoft Exchange Server Installation Guide.
	Replacing MAPI and HAPI applications. MS Mail API applications and HyperCard® stack applications made with the HyperCard SDK don’t function with Microsoft Exchange Server. You need to replace these applications.

Migrating Custom Forms
MS Mail (AppleTalk) custom forms are based on HyperCard and are not compatible with Microsoft Exchange Server custom forms. Messages created in custom forms are migrated as text so that no data is lost. 
If you have many messages that use a particular custom form, you could preserve that information as a form instead of as text. To do so, you must extract it before migration. Use the MS Mail SDK for HyperCard (on the Extras disk of MS Mail version 3.x) to create a HyperCard application for retrieving the information and storing it in a database.
If you are using Microsoft Exchange Server computers as a backbone between MS Mail sites, be aware that custom forms are converted to text when sent across the MS Mail Connector. This could impact coexistence during a multiphase migration. 
Migrating Groups
You should migrate groups before you migrate users. If directory synchronization is configured correctly, the distribution lists are automatically updated as mailboxes replace custom recipients. 
You can use the MS Mail (AppleTalk) Network Administrator program to create a list of groups, which you import to Microsoft Exchange Server and use to create Microsoft Exchange Server distribution lists.
	To migrate groups
	1.	Make sure that you have defined custom recipients for all users in Microsoft Exchange Server.
	2.	Use the MS Mail (AppleTalk) Network Administrator program to create a list of all global groups and their members.
Global group list for Dublin,
1/7/96  10:08,

All,Dublin :
Assembly Team,Dublin
Sales,Dublin

Assembly Team,Dublin :
Chris Bauknecht
Eva Corets
Joe Howard

Sales,Dublin :
Paul Canniff
Reed Koch
Roger Harui

	3.	Use the Directory Export command in the Microsoft Exchange Server Administrator program to export a list of custom recipients to a file with the following header:
Obj-Class,Directory Name,Target-Address

Obj-Class	Directory Name	Target-Address	
			
Remote	ChrisBauknecht	MSA:Chris Bauknecht@dublin	
Remote	EvaCorets	MSA:Eva Corets@dublin	
Remote	JoeHoward	MSA:Joe Howard@dublin	
Remote	PaulCanniff	MSA:Paul Canniff@dublin	
Remote	ReedKoch	MSA:Reed Koch@dublin	
Remote	RogerHarui	MSA:Roger Harui@dublin	

	4.	Modify the exported list so that the target addresses have the same format as the group list names. You can do this with a macro that removes the MSA and replaces the at sign (@) with a comma.

Obj-Class	Directory Name	Target-Address	
			
Remote	ChrisBauknecht	Chris Bauknecht,Dublin	
Remote	EvaCorets	Eva Corets,Dublin	
Remote	JoeHoward	Joe Howard,Dublin	
Remote	PaulCanniff	Paul Canniff,Dublin	
Remote	ReedKoch	Reed Koch,Dublin	
Remote	RogerHarui	Roger Harui,Dublin	

	5.	In the group list, replace all mailbox names with the directory or common names from the custom recipient export list.
All,Dublin :
Assembly Team,Dublin
Sales,Dublin

Assembly Team,Dublin :
ChrisBauknecht
EvaCorets
JoeHoward

Sales,Dublin :
PaulCanniff
ReedKoch
RogerHarui

	6.	Convert the group list to directory import format. You need to create unique directory names for each distribution list by following these steps:
	Add header line of #$#
	Replace all paragraphparagraph with ###
	Replace all space:paragraph with #,#
	Replace all paragraphs with %
	Replace all commas with a space
	Replace all ### with paragraphdl,,
	Between all ,, insert the common-name of the distribution list
	Replace #$# with obj-class,common-name,display-name,members

Obj-Class	Common-Name	Display-Name	Members	
				
dl	ZZAll	All Dublin	Assembly Team Dublin%Sales Dublin	
dl	zAssemTeam	Assembly Team Dublin	ChrisBauknecht%Eva Corets%JoeHoward	
dl	zSales	Sales Dublin	PaulCanniff%ReedKoch%RogerHarui	

	7.	(Optional) If you have groups that are members of other groups (nested groups), the display names for those nested groups are still in the members list. For the nested groups in the members field of all distribution lists, replace the display names with the directory names.
In this example, the All Dublin group has two nested groups. In the members field, the display names of these groups are replaced with the common names of the new distribution lists. 
Obj-Class	Common-Name	Display-Name	Members	
				
dl	ZZAll	All Dublin	zAssemTeam%zSales	
dl	zAssemTeam	Assembly Team Dublin	ChrisBauknecht%Eva Corets%JoeHoward	
dl	zSales	Sales Dublin	PaulCanniff%ReedKoch
%RogerHarui	

	8.	Sort the distribution lists by display name. You can remove the server name appended to each display name as long as the display name remains unique.
Obj-Class	Common-Name	Display-Name	Members	
				
dl	ZZZAll	All	zAssemTeam%zSales	
dl	zAssemTeam	Assembly 
Team	ChrisBauknecht%Eva Corets%JoeHoward	
dl	zSales	Sales	PaulCanniff%ReedKoch
%RogerHarui	

	9.	Use the Directory Import command in the Microsoft Exchange Server Administrator program to import the file.
	10.	Delete all groups in MS Mail after directory synchronization.

During migration, it may be necessary to update the groups as custom recipients are deleted and replaced with mailboxes. This depends on how you configure directory synchronization and how you use Recipients containers.
Migrating Mailboxes
Use the MS Mail (AppleTalk) source extractor to migrate mailboxes from MS Mail (AppleTalk). You can migrate the following:
	Mailboxes
	Messages, attachments, and private folders
	Schedule+ data
	Personal address book entries

As you migrate a mailbox, the extractor can list all MS Mail groups associated with the mailbox. During a multiphase migration, you can use this log for distribution list maintenance.
The source extractor has the following requirements:
	Macintosh System 6.0.2 or later
	1700K of RAM
	Microsoft Mail for AppleTalk Networks version 3.0 or later
	User must log on as the Network Manager.

Important
The source MS Mail (AppleTalk) server must not be used during extraction. Ask users to exit and log off the client program. You can search the Address Book for users connected to the server. If the Address Book reports that users are logged on when they are not, clear them by choosing Restart from the Special menu.

For best performance, the destination Microsoft Exchange Server computer should not be used while importing migration files. However, this is not required. If the Microsoft Exchange Server Administrator program is not installed on the computer to which you want to import the data, you can install it by running the Microsoft Exchange Server Setup program.

Note
For maximum performance, run the Migration Wizard on the destination server. 

Use one of the following options to extract mailbox data: 
	Specify options in a control file.
	Select default options on the user interface.

Use a control file if you’re migrating a significant portion, but not all, of a server’s mailboxes. Use the interface if you are migrating only a few, or all, of a server’s mailboxes. Control files handle all the user interface choices for you. In addition, they can be used as a permanent log of when and how the mailboxes were migrated. 
Specifying Options in a Control File
The source extractor control file follows standard formatting conventions. The following are valid fields in a control file.
Variables	Description	Default values	
			
Accounts	File name of the accounts file, which must be in the same directory as the control file.		
Mailbox	Extract mailbox creation information. 	TRUE	
Email	Extract private messages from the accounts.	TRUE	
PAB	Extract personal address book entries and distribution lists. 	TRUE	
Schedule	Extract schedule and appointment data.	TRUE	
EmailStart	Earliest date to retrieve messages. Migration file date/time format. To retrieve even the oldest mail, leave entry blank.		
EmailEnd	End date to retrieve messages. Migration file date/time format. EmailStart is smaller than EmailEnd. To restrict retrieving by age for recent messages, leave entry blank.		
SchedStart	Earliest date to retrieve appointments. Migration file date/time format. See Appendix B.		
SchedEnd	End date for retrieving appointments. Migration file date/time format. SchedStart is smaller than SchedEnd.		
FirstSpaceLast	Attempt to split the mailbox name by looking for a space.	FALSE	
LastCommaFirst	Attempt to split mailbox name by looking for a comma.	FALSE	
LastSpaceFirst	Attempt to split mailbox name by looking for a space.	FALSE	
LogGroups	List group memberships for each mailbox.	FALSE	

The fields FirstSpaceLast, LastCommaFirst, and LastSpaceFirst are mutually exclusive. You should only use one in the control file. You enable parsing of the mailbox name for surname and given name by setting one of these variables to TRUE, or you disable all mailbox name parsing by setting it to FALSE.
Each line of the control file has one variable, followed by a comma and the value for that variable. For example, the following “First Batch” control file creates mailboxes, and also migrates 32 days of mail (inclusive dates) and the next five years of calendar data for each mailbox. 
Accounts,First Batch
Mailbox,TRUE
PAB,TRUE
Schedule,TRUE
EmailStart,19951010000000
EmailEnd,19951110000000
SchedStart,19951010000000
SchedEnd,20001010000000
FirstLastNames,TRUE
LogGroups,FALSE

The account list is a text file with the name of each mailbox to be migrated. You can use the Network Administrator program to create a local list of all the mailboxes, and then edit the file as needed. Each name appears on a separate line:
Bill Lee
Fran Wilson
Ann Devon

	To specify options in a control file
	1.	Log on to MS Mail as Network Manager.
	2.	Start the Microsoft Source Extractor program from the MS Mail (AppleTalk) Migration Source Extractor disk.
	3.	From the Migrate menu, choose Control File to specify options with the control file.
	4.	Select the control file, and then choose OK.
	5.	Select the accounts file, and then choose OK.
	6.	In the Save Migration Folder As box, specify the name of the new folder in which to create the migration files, and then choose Save.

The source extractor creates the migration files and displays a summary of the results. You can save this information by choosing Save from the File menu.
If you select the Generate First and Last Names option, the extractor attempts to split the mailbox name into first and last names. It assumes that all userlist names are in the selected format and it searches backward from the end for separation characters. If a space is preceded by a comma, the space is skipped. The first and last names generated are logged to the log window for each mailbox. You can fix errors by changing the migration file using the Microsoft Exchange Server Administrator program or the Directory Import command.

Important
This algorithm does not correctly distinguish last names that contain spaces (for example, “Van Morrison”).

Selecting Default Options on the User Interface
	To select default options on the user interface
	1.	Log on to MS Mail as Network Manager.
	2.	Start the Microsoft Source Extractor program from the MS Mail (AppleTalk) Migration Source Extractor disk.
	3.	From the Migrate menu, choose Migrate Users to specify options.
	4.	Select the import options based on your needs, and then choose Continue.
Option	Description	
		
Mailbox Creation 
Information	Creates mailboxes for all users in the account list or users selected in the next screen.	
Generate First and 
Last Names	Parses the existing mailbox name to resolve first and last names. If not selected, fields are left empty. (You select the parsing option that best fits your display naming convention.)	
E-mail Messages	Copies messages and folders from the selected mailboxes. (You select all messages or set a date range.)	
Schedule+ Information	Copies calendar data to a special message in the selected user’s inbox. (You select all messages or set a date range.)	
Personal Address 
Books	Copies PAB entries to a special message in the selected user’s inbox.	

	5.	In the Available Accounts box, select the mailboxes you want to migrate. Choose Add, and then choose Continue. (Or choose Add All to select all mailboxes, and then choose Continue.)
	6.	In the Save Migration Folder As box, specify the name of the new folder in which to create migration files, and then choose Save.

The source extractor creates the migration files and displays a summary of the results. You can save this information by selecting Save from the File menu.

Tip
If you need to modify the directory section of the migration files, run the extractor twice. The first time, extract mailbox creation information to a small, easy-to-edit file. The second time, extract everything else.

Migrating MS-DOS Clients
To migrate mailboxes accessed with the MS-DOS client, you need not be concerned about locally stored mail or custom form messages. There are only two primary issues: 
	Protocol replacement
	Extended characters

Protocol Replacement
The AppleTalk or EtherTalk® protocol is not necessary to connect to Microsoft Exchange Server. When you finish using the MS-DOS client for MS Mail (AppleTalk), you can remove the protocol. You need to install TCP/IP, IPX/SPX or other supported protocols for the Microsoft Exchange Server MS-DOS client.
Extended Characters
Localized versions of the MS-DOS client for MS Mail (AppleTalk) send mail in the appropriate code-page, which allows for extended characters. Localized versions of the Apple Macintosh client use the Geneva character set. Since data is stored in the format in which it was sent, you can migrate mail and preserve this information. 
If all the MS-DOS clients use English, you can migrate these mailboxes with the Apple Macintosh client mailboxes. If the MS-DOS clients use other languages, migrate MS-DOS clients separately from Apple Macintosh client mailboxes. In the packing list file of the MS-DOS client mailbox, change the code-page value to the appropriate code-page. Then import the migration files.
Importing the Migration Files
To import the migration files to Microsoft Exchange Server, you use the Migration Wizard. For information about using the Migration Wizard, see Chapter 2, “Using the Migration Wizard.”
Schedule+ Information
The source extractor exports Schedule+ 1.0 appointments and notes to the migration files. The Migration Wizard imports the calendar information to the user’s inbox as a special message with an attachment. The user imports the data by opening the message and double-clicking on the imbedded schedule file. The message is in the same language used in the Migration Wizard dialog boxes. If this language is not the same as the user’s, send the user a message with the translated instructions before migration.
Performing a Multiphase Migration
If you are performing a multiphase migration, you will also need to:
	Connect the MS Mail (AppleTalk) and Microsoft Exchange Server sites.
	Support the native gateway during migration.
	Convert gateway recipients to Microsoft Exchange Server custom recipients.
	Synchronize directories between MS Mail (AppleTalk) and Microsoft Exchange Server. 

For information about synchronizing directories, see the Microsoft Exchange Server Administrator’s Guide.
Connecting Sites
You can connect MS Mail (AppleTalk) servers with Microsoft Exchange Server computers using the MS Mail Connector. This connection allows you to:
	Transfer mail and attachments from one system to the other.
	Let MS Mail users take advantage of some Microsoft Exchange Server gateways.
	Synchronize address information between MS Mail sites and Microsoft Exchange Server sites using the Microsoft Exchange Connection directory exchange requestor.

To decide how to connect MS Mail (AppleTalk) sites to Microsoft Exchange Server sites, consider the following issues:
	Single vs. multiple links.
It is easiest to use only one link per MS Mail (AppleTalk) site, but more links are possible.
	Directory synchronization.
If you have more than one MS Mail (AppleTalk) site or more than one link, plan how addresses will be imported and exported. This decision can be related to your plans to convert custom recipients to mailboxes. 
	Server statistics in the MS Mail (AppleTalk) Administrator program. 
Consider these statistics when determining which MS Mail (AppleTalk) servers are least used, and select one to be the gateway server. The gateway server can experience high volumes of mail during the early and middle phases of migration.

The following table summarizes the various options for connecting MS Mail (AppleTalk) and Microsoft Exchange Server computers.
Network configuration	Connection options	
		
MS Mail servers on same network as Microsoft Exchange Server.	Install a Microsoft Exchange Server MS Mail Connector.	
MS Mail servers on network isolated from Microsoft Exchange Server.	Connect a Microsoft Exchange Server computer in the MS Mail (AppleTalk) location to the main Microsoft Exchange Server computer through SMTP, RAS, X.25, or public X.400 connections.
 – or – 
Use an MS Mail (AppleTalk) 3.1d server in the Microsoft Exchange Server location as its own site, and connect the two MS Mail (AppleTalk) sites with AppleTalk Remote Access.
 – or –
Use an MS Mail for PC Network postoffice in the MS Mail (AppleTalk) site, and use X.25 or asynchronous connections between the postoffice and the Microsoft Exchange Server connector postoffice. Connect the MS Mail (AppleTalk) server to the MS Mail (PC) postoffice with the Mail Connection Gateway, version 3.2.	
MS Mail servers connected to an MS Mail (PC) postoffice with Mail Connection Gateway, version 3.2.	Connect Microsoft Exchange Server to the MS Mail (PC) postoffices and backbone to MS Mail (AppleTalk) servers.
 – or –
Remove the existing connection gateway and reinstall it to connect to the connector postoffice. Set the registry entry “SetResponsibleBit” to a value of 0 for the MSExchangeMSMI service after the gateway is installed.	

For more information about the MS Mail Connector, see the Microsoft Exchange Server Administrator’s Guide.

Note
If your users connect to MS Mail (PC) gateways with the MS Mail Connection Gateway version 3.2, they can continue to send and receive mail through these gateways after migrating.

Supporting the Native Gateway During Migration
MS Mail (AppleTalk) gateways are not compatible with Microsoft Exchange Server. If you want to maintain connectivity with these foreign systems, you need to do one of the following:
	Install an equivalent gateway or connector on a Microsoft Exchange Server computer or MS Mail (PC) postoffice in your organization.
	Use a type of gateway address that matches a type supported by the MS Mail Connection gateway: X400, SMTP, SNADS, PROFS, FAX, ATT, MCI, 3COM, or MHS.
	Install the gateway access component on the Microsoft Exchange Server connector postoffice for MS Mail (PC) gateways.

If inbound messages route through Microsoft Exchange Server, you also need to do the following:
	Create a custom recipient in the Microsoft Exchange Server global address list for every MS Mail mailbox. You can create custom recipients with directory synchronization, as described in the Microsoft Exchange Server Administrator’s Guide.
	Maintain the external addresses of custom recipients for the gateway address type. (If not the same, users must notify those with whom they exchange mail of their new address after the gateway is reestablished as a Microsoft Exchange Server gateway or connector.)
	Redirect incoming mail from the foreign system to the appropriate gateway or connector in Microsoft Exchange Server.

Redirecting Mail Sent to the Native Gateway
After the native gateway is reestablished as a Microsoft Exchange Server gateway or connector, you can start migrating mailboxes. The following table summarizes the options. To minimize disruptions in mail delivery, the first option is the best.
Configuration	Result	
		
Mail to native gateway is redirected, and addresses of migrated users and custom recipients are updated.	All users receive mail sent to both new and old addresses.	
Mail to native gateway is redirected, and only addresses of migrated users are updated.	Migrated mailboxes receive mail sent to both new and old addresses. Non-migrated mailboxes only receive mail sent to the new addresses; the mail sent to old addresses is returned to sender as non-deliverable.	
Mail to native gateway is redirected, and no addresses are updated.	Users receive mail sent to their new addresses, but mail sent to old addresses is returned to the sender as non-deliverable.	
Mail to native gateway is not redirected.	Migrated mailboxes must periodically connect to the MS Mail (AppleTalk) server to check for mail. Or you can use the Out of Office Server (server version) to periodically forward all mail from migrated mailboxes to the corresponding MS Mail (AppleTalk) custom recipient for the Microsoft Exchange Server mailbox. You then respond to the sender with the user’s new address. The Out of Office Server is available only in MS Mail (AppleTalk), version 3.1d.	

Note
When you redirect inbound mail to an MS Mail (PC) gateway, address mapping depends on the MS Mail (AppleTalk) server’s postoffice address and gateway features.

Maintaining External Addresses During Migration
When you migrate mailboxes to Microsoft Exchange Server, users can use Microsoft Exchange Server and MS Mail (PC) gateways. You can modify mailbox addresses to match old external addresses. To maintain external addresses, you must replace or supplement the default gateway address of the Microsoft Exchange Server custom recipient or mailbox. You will probably want to maintain the Internet (SMTP) addresses. 
The following are sample configurations for maintaining addresses during coexistence and migration. In each configuration, MS Mail (AppleTalk) connects to MS Mail (PC) with the MS Mail Connector version 3.2 and receives mail addressed to hex@proxypo.proxynet.<domain>. 
Sample Configuration No. 1
Microsoft Exchange Server connects to MS Mail (PC) and sees MS Mail (AppleTalk) mailbox addresses as MS Mail addresses. The directory synchronization server is either a Microsoft Exchange Server computer or a postoffice.
	To implement this configuration
	1.	Generate the list from directory synchronization information. Export custom recipients to a file that looks like this:
Obj-class,common-name,target-address,when-created
	2.	Sort the list on target-address. Copy all MS:<proxynet>/<proxypo> recipients to a new file (if not segregated).
	3.	Edit the target-address field:
	Parse proxynet, proxypo, and hex.
	Put them in the proper order: hex@proxynet.proxypo
	Append the domain information: hex@proxynet.proxypo.org.com
	4.	Change the header on the file:
	Delete when-created.
	Replace target-address with secondary-proxy-address.
	Add a mode field.
obj-class,mode,common-name,secondary-proxy-address
	5.	Set the mode field to modify.
	6.	Import the file.

Follow this procedure every week. Sort first on when-created, and delete all the old entries.
Sample Configuration No. 2
The Microsoft Exchange Server computer connects directly to MS Mail (AppleTalk) and MS Mail (PC) and is the directory synchronization server, importing MSA addresses from MS Mail (AppleTalk) and exporting MS or MSA addresses to MS Mail (PC).
	To implement this configuration
	1.	Use the Connection Gateway CNU program to create a full directory synchronization mail message and send it to a user’s mailbox (not the $SYSTEM address). This should have all the PCM:proxynet/proxypo/hex values. 
	2.	Export custom recipients to a file that looks like this:
Obj-class,common-name,target-address,when-created,display-name
	3.	Sort the list on target-address. Copy all MSA: to a new file. Sort the list on display-name.
	4.	Import the directory synchronization message to Microsoft Excel or another spreadsheet program or to a database. The file is space delimited. Break it into three columns: junk, e-mail address, and display name. Sort on display name. 
	5.	Combine the two files into one new file with a macro that matches display names and copies the e-mail address into the target-address field.
	6.	Edit the target-address field:
	Parse proxynet, proxypo, and hex
	Put them in the proper order: hex@proxynet.proxypo
	Append on the domain information: hex@proxynet.proxypo.org.com
	7.	Change the header on the file:
	Delete the display-name and when-created fields.
	Add a mode field.
	Change target-address to secondary-proxy-address.
obj-class,mode,common-name,secondary-proxy-address
	8.	Set the mode field to modify.
	9.	Import the file.

Follow this procedure every week. Sort first on when-created, and delete all the old entries.
Sample Configuration No. 3
The Microsoft Exchange Server computer connects directly to MS Mail (AppleTalk) and MS Mail (PC) and is a requestor to an MS Mail (PC) postoffice directory synchronization server. Microsoft Exchange Server and MS Mail (PC) have MS addresses for MS Mail (AppleTalk) mailboxes.
	To implement this configuration
	1.	Export custom recipients to a file that looks like this:
Obj-class,common-name,target-address,when-created
	2.	Edit the target-address field:
	Parse proxynet, proxypo, and hex
	Put them in the proper order: hex@proxynet.proxypo
	Append on the domain information: hex@proxynet.proxypo.org.com
	3.	Change the header on the file:
	Delete the when-created field.
	Add a mode field.
	Change target-address to secondary-proxy-address.
obj-class,mode,common-name,secondary-proxy-address
	4.	Set the mode field to modify.
	5.	Import the file.

Follow this procedure every week. Sort first on when-created, and delete all the old entries.
Converting Gateway Recipients
You should convert gateway recipients in MS Mail (AppleTalk) servers to Microsoft Exchange Server custom recipients. To do this, you use the MS Mail Administrator program to create a list of gateway recipients, and you put this list into directory import format. Import the list to Microsoft Exchange Server using the Administrator program. 
For more information about custom recipients, see the Microsoft Exchange Server Administrator’s Guide.

Note
There must be a corresponding gateway in the organization for which their addresses are valid. You cannot send mail from Microsoft Exchange Server through an MS Mail (AppleTalk) gateway.