MAILbus 400 SMTP Gateway ____________________________________________________________________ Release Notes for Digital UNIX Revision/Update Information: Version 2.1 Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. © Digital Equipment Corporation 1996. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: DEC, DECnet, MAILbus, MAILbus 400, VAX DOCUMENT, ULTRIX, and the DIGITAL logo. Internet is a registered trademark of Internet, Inc. Microsoft Exchange is a trademark of Microsoft Corporation. OSF/1 is a registered trademark of Open Software Foundation, Inc. OSI is a registered trademark of CA Management, Inc. UNIX is a registered trademark in the United States and other countries, licensed exclusively by X/Open Company, Ltd. This document was prepared using VAX DOCUMENT, Version 2.1. ________________________________________________________________ Contents 1 Introduction.................................... 1 2 Documentation Provided With This Release........ 1 3 New Features for this Release .................. 2 3.1 Support for the Multipurpose Internet Mail Extensions Defined in RFC 1522................ 2 3.2 Support for Parts of MIXER ................... 2 3.3 New Summary Event - Gateway Status .......... 3 3.4 Support for Remote MTA ....................... 3 4 Changes Since Version 2.0....................... 3 4.1 Interworking with Other MIME Products ........ 3 4.2 New X-Author Header .......................... 3 4.3 More Precise sendmail Rules .................. 4 4.4 Changes in O/R Address Translation ........... 4 4.5 Running the Setup Procedure to Reinstate Rewrite Rules................................. 4 5 Changes Since Version 1.*....................... 4 5.1 Support for RFC 1327, RFC 1494 and RFC 1495 .. 5 5.2 Untranslated Internet Message Headers Now Added to the End of X.400 Messages............ 5 5.3 Changes to the Way the SMTP Gateway Uses the MAILbus 400 MTA .............................. 5 5.4 Use Setup Procedure Instead of Editing the Startup NCL Script............................ 6 5.5 Additional Characteristic Attributes for Modifying Message Exchange.................... 6 5.6 Changes to the add_map and remove_map Tools .. 7 5.7 Changes to the Settings of the Address Lookup Attributes.................................... 8 6 Restrictions in this Version of the SMTP Gateway......................................... 9 6.1 Quotation marks Must be Omitted in Address Test Tool Input............................... 9 iii 6.2 Syntactical Errors in O/R Addresses .......... 9 7 Restrictions in Other Products that Can Affect the SMTP Gateway ............................... 11 7.1 Sendmail Truncates Addresses Longer than 200 Characters.................................... 11 7.2 Sendmail Removes Blind Carbon Copy Headers from Messages................................. 11 7.3 MTA Version 1.* Changes Teletex Value of Organisational Unit Attribute in Returned Content to Printable String .................. 12 iv 1 Introduction The MAILbus 400[TM] SMTP Gateway enables users of X.400- based and SMTP-based messaging systems (such as the Internet[R]) to exchange messages. The MAILbus 400 SMTP Gateway translates X.400 messages into the format used within the Internet (as defined in RFC 822), and translates Internet messages into X.400 format. These release notes are provided with Version 2.1 of the MAILbus 400 SMTP Gateway for Digital[TM] UNIX[R] (formerly DEC[TM] OSF/1[R]). They describe: o The documentation provided with this release (see Section 2). o The new features provided in this release (see Section 3). o Changes from Version 2.0 of the MAILbus 400 SMTP Gateway (see Section 4). o Changes from Version 1.* of the MAILbus 400 SMTP Gateway (see Section 5). o The restrictions in Version 2.1 of the MAILbus 400 SMTP Gateway (see Section 6). o The restrictions in other products that can affect the MAILbus 400 SMTP Gateway (see Section 7). Note that if you have already upgraded to a Version 2.0 SMTP Gateway, there is no need to read Section 5. 2 Documentation Provided With This Release The following documentation is provided with Version 2.1 of the MAILbus 400 SMTP Gateway: o MAILbus 400 SMTP Gateway Managing, Version 2.1 o MAILbus 400 SMTP Gateway Installing on a Digital UNIX System, Version 2.1 o MAILbus 400 SMTP Gateway Software Product Description o MAILbus 400 SMTP Gateway Release Notes for Digital UNIX, Version 2.1 (this document) 1 Online help is provided in the SMTP-Gateway Module Online Help, which can be accessed through the NCL help. 3 New Features for this Release The following sections describe the new features that have been introduced in Version 2.1 of the SMTP Gateway. If upgrading, you mustread the relevant chapter of MAILbus 400 SMTP Gateway Managing. 3.1 Support for the Multipurpose Internet Mail Extensions Defined in RFC 1522 The SMTP Gateway conforms to the Multipurpose Internet Mail Extensions (MIME) defined in RFC 1522. MIME is a standardized way of encoding headers and bodyparts that have always been difficult to transfer in RFC 822-based Internet systems, such as headers that use non-ASCII characters. To manage the new RFC 1522 encodings, there is a new attribute of the SMTP-Gateway entity, Header Encoding. By default, however, the setting of the Header Encoding attribute makes the SMTP Gateway generate non-MIME headers. Further details of the Header Encoding attribute are in both MAILbus 400 SMTP Gateway Managing and the SMTP Gateway Module Online Help. More information about the SMTP Gateway's conformance to relevant RFCs is provided in Appendix E of MAILbus 400 SMTP Gateway Managing. RFC 1522 is provided with the SMTP Gateway and is located at /var/smtpgw/doc/rfc1522.txt. 3.2 Support for Parts of MIXER MIXER is an Internet draft that defines the MIME X.400 Enhanced Relay. MIXER was, when Version 2.1 of the SMTP Gateway was released, still evolving. Version 2.1 of the SMTP Gateway implements the parts of MIXER that were comparatively stable. MAILbus 400 SMTP Gateway Managing gives details of which parts of MIXER are implemented. 2 3.3 New Summary Event - Gateway Status There is now a summary event, Gateway Status, that gives the overall status of the SMTP Gateway and points to any error event that stops the SMTP Gateway from running normally. For further details of this event see MAILbus 400 SMTP Gateway Managing or the SMTP Gateway Module Online Help. 3.4 Support for Remote MTA This release can support an MTA running on a different node from the SMTP Gateway. See MAILbus 400 SMTP Gateway Managing for details. 4 Changes Since Version 2.0 This section lists some significant changes since Version 2.0 of the SMTP Gateway. For further details of all these changes, see MAILbus 400 SMTP Gateway Managing. 4.1 Interworking with Other MIME Products In Version 2.0 of the SMTP Gateway, the transfer of binary bodyparts between Microsoft Exchange[TM] and the SMTP Gateway caused problems. This was as a result of the different ways of identifying bodyparts used by Microsoft Exchange and the SMTP Gateway. 4.2 New X-Author Header When sending a message from X.400 to the Internet, if the originator address consisted only of a free form name, previous versions of the SMTP Gateway constructed an invalid From: field. When a free form name is the only indication of where a message came from, Version 2.1 of the SMTP Gateway no longer produces a From: field, but instead produces a new header, X-Author. 3 4.3 More Precise sendmail Rules In previous versions, the SMTP Gateway used imprecise sendmail rules. Version 2.1 has changed the rules in several major ways: o The rules now use only the Gateway's RFC 822 domain name. o The rules are easier to edit than in previous versions. See Appendix F of MAILbus 400 SMTP Gateway Managing for details of the new rewrite rules. 4.4 Changes in O/R Address Translation The method the SMTP Gateway uses for translating from X.400 O/R addresses to SMTP addresses, is different now from the method used in previous versions. Previous versions of the SMTP Gateway used an Internet address supplied in the RFC-822 DDA only if the remainder of the O/R address matched the gateway's own address or was in the directory. Now, if an RFC-822 DDA supplies an Internet address, the SMTP Gateway uses that address irrespective of any other O/R address terms. This is in accordance with MIXER. 4.5 Running the Setup Procedure to Reinstate Rewrite Rules This version of the SMTP Gateway adds rewrite rules to sendmail.cf when the setup procedure runs. Previous versions added rewrite rules when the SMTP Gateway was installed, and used a script to reinstate them. This script is no longer a part of the SMTP Gateway kit; to reinstate rewrite rules you simply run the setup script. 5 Changes Since Version 1.* Changes noted in this section are additional to the ones noted in Section 4, and apply only if you are upgrading from a Version 1.* SMTP Gateway. If you are upgrading from a Version 2.0 SMTP Gateway you can omit this section. 4 5.1 Support for RFC 1327, RFC 1494 and RFC 1495 Since Version 2.0, the SMTP Gateway has conformed to RFC 1327, which defines how Gateways should translate the headers on Internet messages and messages based on the 1988 X.400 recommendations. RFC 1327 also defines how to translate between the bodies of Internet and X.400 messages, though these definitions have been superseded by RFC 1494 and RFC 1495. Version 2.1 of the SMTP Gateway continues to conform to both RFC 1494 and 1495 as described in Appendix E of MAILbus 400 SMTP Gateway Managing. RFC 1327, 1494 and 1495 are provided with the SMTP Gateway and are located at: /var/smtpgw/doc/rfc1327.txt /var/smtpgw/doc/rfc1494.txt /var/smtpgw/doc/rfc1495.txt 5.2 Untranslated Internet Message Headers Now Added to the End of X.400 Messages When the SMTP Gateway generates an X.400 message from an Internet message, it writes those Internet message headers that it could not translate into a text bodypart and places the bodypart at the end of the X.400 message. In Version 1.*, the SMTP Gateway added the untranslated Internet message headers in a bodypart at the beginning of the X.400 message. Note that the SMTP Gateway translates more Internet headers into X.400 headers than Version 1.*. This reduces the likelihood of a bodypart with untranslated Internet message headers being added to the end of the X.400 message. 5.3 Changes to the Way the SMTP Gateway Uses the MAILbus 400 MTA Since Version 2.0, the SMTP Gateway has not used the Shared File 1984 interface when connecting to the MAILbus 400 MTA; it uses the XAPI interface instead. 5 Also, the SMTP Gateway no longer accesses the DEC X.500 Directory Service directly; instead, it uses services provided by the MAILbus 400 MTA. As a result of these changes, two password attributes were added to the SMTP-Gateway entity: PW-Agent and PW-Domain. The PW-Agent attribute contains the password that provides the required authorization when the SMTP Gateway connects to the MTA. The PW-Domain attribute contains the password that provides the required authorization for the SMTP Gateway when it passes a request for directory information to the MTA. How to upgrade from a previous version of the SMTP Gateway is described in detail in MAILbus 400 SMTP Gateway Managing. 5.4 Use Setup Procedure Instead of Editing the Startup NCL Script The SMTP Gateway accesses and modifies information in the SMTP Gateway's startup NCL script each time you run the setup procedure. If you modify the SMTP Gateway's startup NCL script manually it is possible that the setup procedure subsequently fails to access or modify the information in the startup NCL script. Therefore we recommend that you always make changes to the SMTP Gateway's startup NCL script by running the setup procedure. 5.5 Additional Characteristic Attributes for Modifying Message Exchange A number of new characteristic attributes have been provided since Version 2.0 of the SMTP Gateway. With the exception of the Trace Logging attribute, these new attributes allow you to specify how the SMTP Gateway translates between X.400 and Internet messages. The new attributes are: Text Encoder Binary Encoder Character Set 6 Character Translation Address Comments Trace Logging The SMTP Gateway is installed with values for these at- tributes that should be appropriate for most requirements. If you need to modify the settings of these attributes, run the SMTP setup procedure in the advanced mode. The new attributes and the setup procedure in the advanced mode are described in detail in Chapter 10 of MAILbus 400 SMTP Gateway Managing. 5.6 Changes to the add_map and remove_map Tools Changes have been made to the usage of the add_map and remove_map tools. You no longer need to use the -bothways parameter with the add_map tool in order to set up two address entries (that is, an O/R address entry and a foreign address entry) for the same user or group of users. In Version 2.0 of the SMTP Gateway, the following new parameters were introduced: o The -oneway parameter. Use this parameter to add different address entries to the directory, depending on whether an address translation is to be used in an originator or a recipient address. o The -x400user parameter. Use this parameter to add address entries to the directory for X.400 users. With this parameter only the Internet translation is added to a user's O/R address entry; no content information and routing instruction is added. o The -i parameter. This parameter replaces the -r parameter. Use the -i parameter to indicate an Internet address in an add_map or remove_map command. For example, the following command sets up two address entries for the same user, that is, an O/R address entry and a foreign address entry: % /var/smtpgw/scripts/add_map -o "c=nz;a=nz-ptt;p=veg;ou1=gisborne;ou2=domestic;s=nimble" -i nimble@domestic.veggies.com 7 Always enter add_map and remove_map commands on one line; the commands in this section are printed on several lines for clarity. In the following example one address entry is set up, indicated by the -oneway parameter: % /var/smtpgw/scripts/add_map -o "c=nz;a=nz-ptt;p=veg;ou1=gisborne;ou2=export;s=jameson" -i jameson@export.veggies.com -oneway Note also that the manpages for the add_map and remove_ map tools are no longer available. Instead, you can obtain online help on the add_map and remove_map tools by typing: % /var/smtpgw/scripts/add_map (for help on the add_map tool) % /var/smtpgw/scripts/remove_map (for help on the remove_map tool) More information on the add_map and remove_map tools is provided in Chapter 7 of MAILbus 400 SMTP Gateway Managing. 5.7 Changes to the Settings of the Address Lookup Attributes The SMTP Gateway has the following attributes, which specify how the SMTP Gateway is to translate addresses on messages: Lookup Internet Users Lookup X400 Users In Version 1.* of the SMTP Gateway these attributes had three settings: Off, Optional and Mandatory. Since Version 2.0, the SMTP Gateway has had only two settings for these attributes: Optional and Mandatory. The functionality of the Off setting has been included in the Optional setting. Therefore, if you have used the Off setting before, accept the value Optional when setting up the SMTP Gateway during the upgrade to Version 2.1. 8 6 Restrictions in this Version of the SMTP Gateway This section describes restrictions in Version 2.1 of the SMTP Gateway. 6.1 Quotation Marks Must be Omitted in Address Test Tool Input When entering an Internet address in the address test tool, you must not enclose encoded X.400 attributes in quotation marks. For example, when sending a message to the gateway you might use an address of the form To: "/OU=Finance/OU=Napier/PRMD=VEG/ADMD=NZ-PTT/C=NZ"@node8.x400 When entering the same address to the address test tool, however, you must omit the quotation marks: > /OU=Finance/OU=Napier/PRMD=VEG/ADMD=NZ-PTT/C=NZ@node8.x400 6.2 Syntactical Errors in O/R Addresses The SMTP Gateway always raises a Directory Configuration Error when a syntactically incorrect O/R address is constructed from a Foreign Address directory entry and data provided by the originator of an Internet message. The Problem Attribute in the Directory Configuration Error event is the full address received from Internet that would result in a syntactically incorrect O/R address. The gateway manager must examine this value and the corresponding Foreign Address entries in the directory to determine the origin of the error. A syntactical error might be either in one of these directory entries, or in the address supplied by the originator. The Constraint Error field indicates what sort of syntax error has occurred. This field has these possible values: o Too Many Characters Supplied An O/R term was too long, or contains non-printable characters. o Not Enough Characters Supplied An O/R name contains some Teletex attributes that would make up a Personal Name, but no Teletex Surname. 9 o No Error There is no error in the Foreign Address entry, but a constructed address would contain an incomplete set of Organisation Units, for example /OU1 and /OU3 but no /OU2. 7 Restrictions in Other Products that Can Affect the SMTP Gateway This section lists restrictions in other products that can affect SMTP Gateway operation. 7.1 Sendmail Truncates Addresses Longer than 200 Characters It is possible for Internet addresses longer than approximately 200 characters to be truncated by some sendmail implementations. If a recipient's address is truncated by sendmail, the message cannot be delivered to the recipient, and a non-delivery report is returned to the originator. Internet addresses themselves do not tend to exceed the 200 character limit; however, if your Internet users need to include long O/R addresses in Internet addresses in order to address X.400 users, this problem could occur. Therefore, if your O/R addresses tend to be very long, you should consider setting up partial address translations for these O/R addresses. Then, Internet users no longer need to include the long O/R addresses in Internet addresses. Part II of MAILbus 400 SMTP Gateway Managing describes in detail how to set up address translations. 7.2 Sendmail Removes Blind Carbon Copy Headers from Messages When translating between Internet and X.400 messages, one of the message headers that the SMTP Gateway translates is the Blind Carbon Copy (BCC) header. However, some sendmail implementations remove BCC headers from all Internet messages they process. 10 When the SMTP Gateway exchanges messages with such a sendmail implementation, no BCC headers will be present on the messages exchanged between Internet and X.400 users. This is because sendmail removes the BCC headers on Internet messages before they reach the SMTP Gateway and also removes the BCC headers on the Internet messages that the SMTP Gateway generates from X.400 messages. 7.3 MTA Version 1.* Changes Teletex Value of Organisational Unit Attribute in Returned Content to Printable String If your MTA is Version 2.0 or later, this restriction does not affect the SMTP Gateway. There was a restriction when working with a Version 1.* MTA. When the SMTP Gateway generates a non-delivery report for an X.400 message, it includes the content of the original X.400 message (called "returned content") in the non-delivery report, if this is requested by the message originator. Sometimes, if the MTA is an earlier version than Version 2.0, a non-delivery report does not reflect O/R addresses in the returned content correctly. More precisely, Organisational Unit attributes with Teletex values in these addresses sometimes are represented by PrintableString values. This occurs if both a PrintableString value and a Teletex value of the Organisational Unit attribute were present on the original message. In this situation, when the MAILbus 400 MTA receives the report, it replaces the Teletex value with the PrintableString value. This problem does not occur if only a Teletex value was present on the original message. 11