## Chapter 8 Summary

UNIX and Windows NT share several messaging protocols and standards including SMTP, IMAP, and POP3.

Unlike other LAN-based e-mail systems that require an SMTP gateway, Microsoft Exchange Server has native support for SMTP and POP3. In addition to Internet e-mail protocols, Microsoft Exchange Server supports LDAP for directory services, and HTTP for access messaging features through a Web browser.

Microsoft supports a number of clients and protocols for downloading e-mail. Any client supporting POP3 or IMAP can be used with Microsoft Exchange Server.

Microsoft Outlook™, supports rules on the client side. These rules examine attributes of a message and perform tasks based on the message configuration. Microsoft Exchange Server also supports server-side scripting using Javasoft or VBScript.

The most difficult aspect of messaging integration is the use of attachments. Users need to be aware that when sending an attachment, a recipient using a different operating system or program may not be able to read the attachment. Microsoft Exchange Server supports a number of common encoding standards including MIME, uuencode, and BinHex. Microsoft Exchange Server also supports converting Rich Text Format (RTF) to Hypertext Transfer Protocol (HTML).

The following table summarizes messaging service compatibility between Windows NT and UNIX.

Role | Windows NT | UNIX
Messaging protocols | SMTP, X.400, POP3, IMAP, MAPI | SMTP,POP3, IMAP
Mail gateway | Microsoft Exchange Server IMS | Third party
Mail User Agent (MUA) | Microsoft Outlook Express, Eudora, Microsoft Outlook, Inbox, Netscape, Internet Explorer | UCB Mail, Zmail, Elm, Netscape, Pine, Mh
List server | Post.Office, NT Mail, Web Essentials ListCaster, Imail, LISTSERV, SVList | Majordomo, Listserv
Filters and processors | Client side uses "Rules" Server side JavaScript or VBScript | Mh, Procmail, Perl scripts

©1997 Microsoft Corporation. All rights reserved. Legal Notices.
Last Updated: December 1, 1997