Microsoft mail to AT&T mail Gateway

Introduction

The Microsoft mail to AT&T mail gateway provides automated conversion between the two mail systems, with the preservation of document structure and attachments. The gateway performs these conversions in tandem with the Microsoft mail to SMTP gateway. The conversion to and from SMTP allows the MSMAIL to AT&T mail gateway to reside anywhere on an SMTP network, as long as routing of the messages is properly configured.

MSMAIL does not have direct support for AT&T mail addresses, and so users access AT&T mail using the SMTP address type. A special address format is used to route the mail items to the gateway. Once the correct address format is entered, the conversion between AT&T mail and MSMAIL is automatic. Attached documents are converted between the native file formats and can be accessed normally, for example double-click to open.


Author

The Microsoft mail to AT&T mail Gateway and this documentation were written by:

Gordon Rowell
Gormand Pty Ltd (ACN 067 684 548)
Post: P.O. Box 239, St Pauls, NSW 2031, Australia

About this documentation

This document is aimed at Microsoft mail users of the gateway. There are also documents for:

User's Guide

The use of the Microsoft mail to AT&T mail gateway is relatively simple. Conversion between the mail systems is automatic. The only aspect that needs to be remembered is the addressing required to send mail to AT&T mail and the addressing required to receive mail from AT&T.

A modification to the AT&T mail address is required to ensure that it can be routed across SMTP networks. The AT&T format addresses, without modification, are unlikely to be routable across general SMTP networks, and the Microsoft mail to SMTP gateway requires a modification to the address to ensure it is passed to SMTP for delivery. The modification to the address is simple and regular. The gateway automatically modifies incoming AT&T mail addresses so that they can be replied to without further modification.


Sending to AT&T mail

All that is required is to create an SMTP address of the form ATTaddress@attmail.uucp. That is, add the fixed string @attmail.uucp to the end of the address given to you by a user on AT&T mail. Initial strings of attmail! or just ! should be deleted. Some examples are:

AT&T mail Address SMTP Address
fredfrog fredfrog@attmail.uucp
attmail!fredfrog fredfrog@attmail.uucp
!fredfrog fredfrog@attmail.uucp
somesite!johndoe somesite!johndoe@attmail.uucp
attmail!somesite!johndoe somesite!johndoe@attmail.uucp
!somesite!johndoe somesite!johndoe@attmail.uucp

Creating AT&T addresses


Microsoft mail aliases

Microsoft mail allows users to create address books, and each entry in the address book contains an Address, which is the SMTP or AT&T mail address, and an Alias, which is the usually used to hold the name that goes with the address. Microsoft mail allows the user to put any string of characters in the Alias field, some of which are unsupported by AT&T mail. For example, if the user John Doe entered:
	Alias: Frog, Frederick (AT&T)
	Address: fredfrog@attmail.uucp
and then used this entry to send mail to AT&T, Microsoft mail would send this from the SMTP gateway in the following format:
	From: "Doe, John" <JDoe@nibuxyz.ms-mail.telstra.com.au>
	To: "Frog, Frederick (AT&T)" <fredfrog@attmail.uucp>
Although this is a legal address format under SMTP, the use of parentheses and commas is not supported under AT&T mail. The gateway performs a conversion on quoted strings in the From:, To:, and Cc: headers to:
	From: John Doe <JDoe@nibuxyz.ms-mail.telstra.com.au>
	To: Frederick Frog <fredfrog@attmail.uucp>
This format is acceptable to Microsoft mail, SMTP and AT&T mail.

Receiving from AT&T mail

The conversion from AT&T mail to Microsoft mail is automatic. All that is required is for the user on AT&T mail to use the proper address to ensure that the mail passes through the conversion gateway. It is also possible to send mail via SMTP from AT&T over the Internet, but this avoids the conversion process. Binary data in the attachments may be stripped, resulting in data which cannot be easily converted.

In order for conversion to occur, the AT&T mail user must ensure that the mail passes through the gateway by the direct link from AT&T mail. The addressing used is simply a modification of your normal SMTP address into a format suitable for use by AT&T mail.

It is vital that messages with attachments are sent via the gateway. Messages with attachments sent over the Internet will appear in the MSMAIL inbox as MSG000.BIN, and will not be readable without external conversion.

To receive from AT&T mail, all that you need to know are the Microsoft mail POSTOFFICE that you connect to and your Microsoft mail USER name. You then perform a simple replacement of these two items into the address below:


	telstra!POSTOFFICE.ms-mail.telstra.com.au!USER

Some examples are:

Microsoft mail Address AT&T mail Address
NCAGEPPI/JUser telstra!ncageppi.ms-mail.telstra.com.au!JUser
NIBUGCD/JBloggs telstra!nibugcd.ms-mail.telstra.com.au!JBloggs
QNPBQRS/FThing telstra!qnpbqrs.ms-mail.telstra.com.au!FThing
VITGXYZ/ABod telstra!vitgxyz.ms-mail.telstra.com.au!ABod

The simplest way to let someone know your AT&T mail address is to send them some mail using the addressing rules shown in Sending to AT&T mail. The correct address will be automatically inserted into your mail, and they can simply reply to your mail.

Due to the change of company name from Telecom to Telstra, the SMTP address can be any of the valid SMTP addresses:

All of these are valid, and deliverable SMTP addresses for MSMAIL postoffices, although the Telstra addresses are preferred, and the gateway will automatically use the USER@POSTOFFICE.ms-mail.telstra.com.au address on mail going to AT&T. The old OTC MSMAIL/SMTP address USER@POSTOFFICE.ccdn.otc.com.au has been retired. Please use the USER@POSTOFFICE.ms-mail.telstra.com.au address instead.


Non-Delivery Notices

Failures in AT&T mail result in Non-Delivery notices. Unfortunately, AT&T mail sends these messages from the user uucp, without a Subject:, and with the reason for the failure in the Not-Delivered-To: header. The original mail message is returned in full to the sender.

Most SMTP mail readers hide non-standard headers from view unless specifically requested to display them. Microsoft mail users have no way to display extra SMTP headers, such as the Not-Delivered-To: header. They receive a message from uucp, with no Subject: containing their original mail. The gateway detects these failures, and generates a special mail, which contains the following elements:

Here is the full text of a converted non-delivery notice. The message body is automatically supressed by the gateway. This is first part of a converted Non-Delivery notice as shown in Microsoft mail.


Known Limitations


Attachments displayed at the top of the message

Attachments appear at the top of the received message, rather than in the place in the text where they were originally attached. In the following message, the attachments were included on the lines that now say:
[[ hello.doc : 2842 in hello.doc ]]
and
[[ hello.xls : 2841 in hello.xls ]]

This is a limitation of the MSMAIL/SMTP gateway, which can be demonstrated by sending mail with attachments on a round-trip through the MSMAIL/SMTP gateway.


Attachment date and time

AT&T mail does not store the date and time of the attachment, while Microsoft mail expects to have this information. The gateway chooses the date and time of conversion for these fields. The original date and time of the attachment cannot be determined. The use of the conversion date and time has a side-effect in that the same message will have different dates and times for the attachments if sent through the gateway more than once.

Zero-length attachments

Microsoft mail supports zero-length attachments, while AT&T mail does not. Zero-length attachments will be silently removed in AT&T mail.