                                       '           Message Exchange User's Guide                  October, 1998       ?           This manual provides information for users of Message =           Exchange, electronic mail software for VMS systems.         A           Revision/Update Information:  This is a revised manual.   =           Operating System and Version: VAX/VMS V5.2 or later   =                                         OpenVMS Alpha V1.5 or -                                         later   =           Software Version:             Message Exchange V5.1     )           Matt Madison and Hunter Goatley            MadGoat Software         "           17_October_1998_________  ?           The information in this document is subject to change 9           without notice and should not be construed as a :           commitment by MadGoat Software. MadGoat Software;           assumes no responsibility for any errors that may "           appear in this document.  8           No part of this publication may be reproduced,9           transmitted, transcribed, stored in a retrieval =           system, or translated into any language or computer ;           language, in any form or by any means electronic, ?           mechanical, magnetic, optical, chemical, or otherwise 9           without the prior written permission of MadGoat            Software.   ;           Use of this software and documentation is subject >           to the terms and conditions set forth in the License           Agreement.  =           The Licensed Materials are provided with RESTRICTED 8           RIGHTS. Use, duplication, or disclosure by the<           Government is subject to restrictions as set forth?           in subparagraph (c)(1)(ii) of the Rights in Technical >           Data and Computer Software clause at DFARS 252.227-@           7013 or subparagraphs (c)(1) and (2) of the Commercial@           Computer Software-Restricted Rights at 48 CFR 52.227-           19, as applicable.  =           MadGoat, Message Exchange, and MX are trademarks of            MadGoat Software.   ;           The following are trademarks of Digital Equipment            Corporation:  7           DEC                DECnet              P.S.I. ;           ULTRIX             VAX                 VAXcluster ;           VMS                AXP                 VMScluster   @           Jnet is a registered trademark of Wingra Technologies,           Inc.  ;           MultiNet and TCPware are registered trademarks of '           Process Software Corporation.   6           LISTSERV is a registered trademark of L-Soft           International.  :           WIN/TCP and Pathway are registered trademarks of           Attachmate, Inc.             __________@           Copyright 1998 MadGoat Software. ALL RIGHTS RESERVED.                       A           _______________________________________________________              Contents  A                 _________________________________________________ A                 PREFACE                                         v   A           _______________________________________________________ A           CHAPTER 1  USING MESSAGE EXCHANGE WITH VMS MAIL     1-1   A                 _________________________________________________ A                 1.1   SPECIFYING AN ADDRESS                   1-1   /                 1.1.1     Displaying MX Address A                           Translations  __________________    1-2   A                 1.1.2     Multiple Recipients  ___________    1-3   A                 1.1.3     Quotation Marks  _______________    1-3   A                 _________________________________________________ A                 1.2   USING SET FORWARD WITH MX               1-3   A                 _________________________________________________ A                 1.3   PERSONAL NAME                           1-4   A                 _________________________________________________ A                 1.4   SIGNATURE FILES                         1-4   A                 1.4.1     Automatic Signature Inclusion  _    1-5   A                 _________________________________________________ A                 1.5   REDIRECTING REPLIES                     1-6   A                 _________________________________________________ 4                 1.6   DIRECTING DELIVERY TO VMS MAILA                       FOLDERS                                 1-6   1                 1.6.1     Folder Delivery Address A                           Format  ________________________    1-7   A                 1.6.2     Format of MX_FOLDERS.DAT  ______    1-7   A                 1.6.3     Example MX_FOLDERS.DAT  ________    1-8   A                                                               iii                     Contents          4                 1.6.4     Specifying Folders in FromA                           Addresses  _____________________    1-8   A                 _________________________________________________ A                 1.7   DELIVERY STATUS NOTIFICATIONS           1-9   A                 1.7.1     Notification Settings  _________    1-9   A                 1.7.2     Returned-Information Settings  _   1-10   A                 1.7.3     Combining the Settings  ________   1-11   A                 1.7.4     Limitations  ___________________   1-11   A                 _________________________________________________ A                 1.8   NETWORK DELIVERY DELAYS                1-11   5                 1.8.1     Displaying MX Informational A                           Messages  ______________________   1-12   A                 _________________________________________________ 7                 1.9   SENDING BINARY FILES TO OTHER VMS A                       USERS                                  1-12   A           _______________________________________________________ A           CHAPTER 2  THE MXALIAS UTILITY                      2-1   A                 _________________________________________________ A                 2.1   ADDING AN MX ALIAS                      2-2   A                 _________________________________________________ A                 2.2   USING AN MX ALIAS                       2-3   8                 2.2.1     Disabling System-Wide MX AliasA                           Lookups  _______________________    2-3   /                 2.2.2     Displaying MX Address A                           Translations  __________________    2-4   A                 _________________________________________________ A                 2.3   DISPLAYING ALIASES                      2-4              iv         A                                                          Contents           A                 _________________________________________________ A                 2.4   MODIFYING ALIASES                       2-5   A                 _________________________________________________ A                 2.5   REMOVING ALIASES                        2-5     A           _______________________________________________________ A           CHAPTER 3  ELECTRONIC MAILING LISTS                 3-1   A                 _________________________________________________ A                 3.1   INTERNET-STYLE LISTS                    3-1   A                 _________________________________________________ A                 3.2   BITNET-STYLE LISTS                      3-2     A           _______________________________________________________ A           CHAPTER 4  NETWORK FILE SERVERS                     4-1   A                 _________________________________________________ A                 4.1   GET HELP                                4-1   A                 _________________________________________________ A                 4.2   MX FILESERV COMMANDS                    4-2   A                 4.2.1     Packages  ______________________    4-3   A                 4.2.2     Binary Files  __________________    4-3   A           _______________________________________________________ A           APPENDIX A  MESSAGE HEADER FORMAT                   A-1   A                 _________________________________________________ A                 A.1   VMS MAIL HEADERS                        A-3   A                 A.1.1     From Header  ___________________    A-4   A                 A.1.2     To and CC Headers  _____________    A-4   A                 A.1.3     Subject Header  ________________    A-4   A                                                                 v                    A           _______________________________________________________              Preface   @           Message Exchange (MX) is software that provides store-=           and-forward routing and delivery of electronic mail =           messages. It can also provide mailing list and file @           distribution services. MX can be used to enhance local>           electronic mail (E-mail) support, and it can be used>           with several kinds of network protocols to provide a9           unified E-mail interface to different networks.   L           __________________________________________________________________             Intended Audience   ;           This manual is intended for any VMS MAIL user who :           uses MX, and users of MX's mailing list and file?           distribution services. The reader should already know ;           the basics of using VMS and the VMS MAIL utility.   L           __________________________________________________________________             Document Structure  @           This guide consists of four chapters and one appendix.  9           Chapter    Describes the MX/VMS MAIL interface.            1   3           Chapter    Describes the MXALIAS utility.            2   8           Chapter    Describes the mailing list handler.           3   /           Chapter    Describes the file server.            4   <           Appendix   Describes MX message formats in detail.           A   A                                                                 v                     Preface         L           __________________________________________________________________             Related Documents   >           You can find additional information in the following           documents:  >           o  Message Exchange Installation Guide describes the               installation of MX.  <           o  Message Exchange Management Guide describes the,              management and operation of MX.  <           o  Message Exchange Mailing List/File Server Guide=              describes the management and operation of the MX *              mailing list and file server.  ?           o  Message Exchange Release Notes contain information A              and updates not included in this manual. The release =              notes are part of the software distribution kit.   ;           o  VMS Mail Utility Manual describes the VMS MAIL               utility in detail.                                                vi                     A           _______________________________________________________   .    1      Using Message Exchange with VMS MAIL      ;           Message Exchange (MX) interfaces with VMS MAIL to @           provide the means for addressing outgoing mail through=           MX. It also ensures that mail that is delivered via ;           MX has an appropriate source address for replies, <           and provides support for signature files and user-'           specified reply-to addresses.   L           __________________________________________________________________      1.1    Specifying an Address   >           MX interfaces with VMS MAIL as a "foreign protocol".:           When using VMS MAIL, you address mail to be sent:           through MX by specifying an address of the form:  )                            MX%"user@host"   9           The leading MX% tells VMS MAIL to invoke the MX 8           protocol handler; the address, which should be>           surrounded by quotation marks to prevent the address<           from being converted to upper case and prevent the;           @-sign from being interpreted by VMS MAIL, is the @           network mail address of the user you wish to send mail
           to.   <           If the user is on the local host, you can omit the=           @host part of the address, and the quotation marks,            just specifying   &                            MX%username             for an address.   >           The MXALIAS utility can be used to define MX aliases:           for e-mail addresses; see Chapter 2, The MXALIAS:           Utility, for information about using MXALIAS. MX=           aliases are used just as if sending mail through MX            to a local user:  A                                                               1-1          .           Using Message Exchange with VMS MAIL          #                            MX%alias   =           Any MX% address given without the @host part of the ?           address is checked to see if it is an MX alias. If it @           is, the equated address is used; if not, the specified8           address is assumed to be that of a local user.  %           ___________________________   ,    1.1.1  Displaying MX Address Translations  =           If you want to see all address translations made by <           MX for MX% addresses passed from VMS Mail, you can=           define the logical MX_VMSMAIL_SHOW_ADDR as shown in             the following command:  =                            $ DEFINE MX_VMSMAIL_SHOW_ADDR TRUE   :           If the logical is defined, MX displays the final+           address used for a given address:   %                            MAIL> SEND N                            To:     MX%JOE, MX%"MX-List@WKUVX1.WKU.EDU", SYSTEML                              MX rewrote alias JOE as <SYSTEM@WKUVX1.WKU.EDU>Z                              MX rewrote MX-List@WKUVX1.WKU.EDU as <MX-List@WKUVX1.WKU.EDU>'                            Subj:   ....   9           Note that "SYSTEM" was not passed to MX because 8           it was not specified with the MX% prefix. Also:           note that JOE had been defined as an alias equal<           to SYSTEM@WKUVX1.WKU.EDU using the MXALIAS utility#           (described in Chapter 2).   =           Placing the MX_VMSMAIL_SHOW_ADDR logical definition @           in your LOGIN.COM will cause MX to always show you all           address translations.         
           1-2          A                              Using Message Exchange with VMS MAIL         %           ___________________________       1.1.2  Multiple Recipients   :           When sending messages to more than one recipient?           through MX, each recipient's address requires the MX% @           prefix (and quotation marks, if needed). For examples:  %                            MAIL> SEND O                            To: SMITH, MX%"jones@otherhost.edu",BROWN,MX%NAMES-L   ;           Note that you can mix plain, local usernames with 4           MX-directed addresses in the same message.  %           ___________________________       1.1.3  Quotation Marks   :           VMS MAIL cannot handle quotation marks within an?           address. MX works around this problem by substituting >           apostrophes instead. For example, if the destination           address is  3                            "node::user"@remote.host   5           you can specify this address in VMS MAIL as   8                            MX%"'node::user'@remote.host"  9           To enter an apostrophe in an address, quote the :           apostrophe with a backslash. For example, if the            destination address is  /                            o'reilly@remote.host              you would enter   5                            MX%"o\'reilly@remote.host"   L           __________________________________________________________________  #    1.2    Using SET FORWARD with MX   @           You can use the SET FORWARD command in VMS MAIL to set>           a forwarding address for your mail through MX. To do>           this, however, requires that you add extra quotes to?           the address. The forwarding address should be quoted, ;           and, since MX addresses must be quoted, the inner   A                                                               1-3          .           Using Message Exchange with VMS MAIL          ;           quotes must be doubled to comply with the command            parsing. For example:v  ?                            MAIL> SET FORWARD "MX%""user@host"""n  <           You should be sure to check the forwarding address?           with SHOW FORWARD and to send yourself a test messaget=           to ensure that you specified the address correctly.   L           __________________________________________________________________      1.3    Personal Name   <           The SET PERSONAL_NAME command in VMS MAIL lets you:           enter your real name, to be appended to your VMS>           username on outgoing mail. Messages sent via MX will>           also include your personal name if you have one set.  L           __________________________________________________________________      1.4    Signature Filest  8           The MX/VMS MAIL interface provides support for<           "signature" files. A signature file is a file that;           contains your name, E-mail address, and any othere=           information that you would like to have included ina;           your outgoing mail messages. It should be no moren;           than a few lines long and should probably contain ?           lines that do not exceed 80 characters in length. For            example:  .                            Peter Shandy, Ph.D.2                            Horticulture Department9                            Balaclava Agricultural Collegec6                            shandy@buster.balaclava.edu  @           Once you create a signature file, you inform MX of its>           existence by defining the logical name MX_SIGNATURE:  L                            $ DEFINE MX_SIGNATURE device:[directory]name.type  :           You can then have the signature included in your&           message by entering the line  %                            /SIGNATURE   
           1-4S w  -    A                              Using Message Exchange with VMS MAIL           <           in your message. To be recognized, there can be no<           other text on the line and no leading blanks. Case<           is not important, and you can abbreviate SIGNATURE=           to SIG. Your signature file will be inserted in the =           message at the point where you place the /SIGNATURE            line.   <           Note that the signature is included only in copies:           of the message that are sent via MX; if you also>           send your message to users not using the MX% prefix,=           they will just see the /SIGNATURE line and not youra           signature file.   =           To enable your signature file every time you login,a:           include the DEFINE command in your login command           procedure.  %           ___________________________R  '    1.4.1  Automatic Signature Inclusion_  >           Your signature file can be included automatically at>           the end of your message by defining the logical name           MX_AUTO_SIGNATURE:  :                            $ DEFINE MX_AUTO_SIGNATURE text  @           The text is not important; as long as the logical name=           is defined, the signature file you specify with MX_ >           SIGNATURE will will automatically be appended to the>           end of all subsequent MX messages. A /SIGNATURE line<           can be used to place the signature anywhere in the7           message (overriding the automatic appending)._  @           If you wish to prevent the automatic inclusion of your&           signature file, enter a line  '                            /NOSIGNATURE   =           in your message. The same formatting rules apply as            for /SIGNATURE.N  A                                                               1-5_ _  _    .           Using Message Exchange with VMS MAIL        L           __________________________________________________________________      1.5    Redirecting Replies   ?           Normally when you send a message via MX from your VMS <           account, the message will include information that=           will direct any replies to the message back to your_=           VMS account. If you would rather have replies go to >           a different account, or to an account on a different@           system, you can define the logical name MX_REPLY_TO to2           include this information in the message:  ;                            $ DEFINE MX_REPLY_TO "user@host"D  @           Note that you should not include the MX% prefix on the?           address, and you should not change quotation marks toS3           apostrophes when you specify the address.m  >           To have this reply address included in your messages=           every time you login, include the DEFINE command in            your LOGIN.COM file.  >           Some mailers, including MX, allow multiple addresses;           on the "From:" line for messages. You can include =           multiple addresses in the MX_REPLY_TO definition to <           allow replies to be returned to multiple addresses>           (assuming the remote mailer allows it). For example,;           if you want replies to your messages to go to two =           different accounts, you could define the logical as_           follows:  G                            $ DEFINE MX_REPLY_TO "user@host,user2@host2"   L           __________________________________________________________________  0    1.6    Directing Delivery to VMS MAIL Folders  @           MX normally delivers incoming messages to your NEWMAIL>           folder, just as VMS MAIL does for local messages. If<           you receive a large amount of e-mail, particularly<           from different mailing lists, MX's folder delivery8           option may help you to keep your e-mail better           organized.  
           1-6_ _  _    A                              Using Message Exchange with VMS MAIL         %           ____________________________  (    1.6.1  Folder Delivery Address Format  7           MX accepts local e-mail addresses of the form 8           username+foldername, and treats the characters>           appearing after the plus sign (+) as either the name@           of a folder or an alias for a folder name. You control=           the folder names into which MX can deliver messages_@           by creating a file called MX_FOLDERS.DAT in your login           directory.  :           When MX receives a message for you that contains8           a plus sign, it reads the contents of your MX_:           FOLDERS.DAT file. If it finds the folder name in=           the file, it delivers the message into that folder. ;           Otherwise, it simply delivers the message to your            NEWMAIL folder._  %           ___________________________   "    1.6.2  Format of MX_FOLDERS.DAT  ;           The file MX_FOLDERS DAT must reside in your login_>           directory (SYS$LOGIN:) and should be an ordinary VMS?           text file. Blank lines in the file are ignored. Other_4           lines should contain one of the following:  @           o  A folder name (may be specified with or without the               leading plus sign).  :           o  A folder alias specification of the form (the,              leading plus sign is required):  8                               +alias  actual-folder-name  9           o  A comment, which is a line beginning with an #              exclamation point (!)._  =           Leading and trailing blanks (and tabs) are ignored.R=           Blanks and/or tabs separate alias names from actual_           folder names._  A                                                               1-7          .           Using Message Exchange with VMS MAIL          >           Since the folder specifications allowed in addresses>           are limited to only ASCII alphanumeric (A through Z,?           0 through 9) characters, underscores (_), and hyphens_>           (-), you can use folder aliases to allow delivery to@           folders that contain other characters that are allowed;           by VMS MAIL (such as dots and international 8-bit_           characters).  %           ___________________________L       1.6.3  Example MX_FOLDERS.DAT  ?           The following is an example of an MX_FOLDERS.DAT file-;           for the user SAMPLE. It resides in SAMPLE's login_           directory.  B                            !  MX-LIST for the MX-List mailing list#                            +mx-list D                            !  INFO-VAX for the Info-VAX mailing list$                            +info-vaxH                            !  MAD.GOAT for the Info-MadGoat mailing list2                            +info-madgoat  mad.goat  %           ___________________________   .    1.6.4  Specifying Folders in From Addresses  ;           You can specify a folder name to be added to yourl:           e-mail address in outgoing messages by using the;           following directive on the first line of the texto           of the message:e  ,                            /FROM=+foldername  ;           This only applies to ordinary (non-/FOREIGN) text_:           messages sent by VMS MAIL or DECwindows Mail. If=           present, MX's VMS MAIL interface will automaticallyM>           remove the line from the text of the message and the@           address in the From: header to be username+foldername.9           Note that this folder name must contain only 7-_=           bit ASCII alphanumeric characters, underscores, and            hyphens.  
           1-8     s    A                              Using Message Exchange with VMS MAIL           9           If you use this directive when subscribing to ah?           mailing list, and specify the folder name in your MX_ ?           FOLDERS.DAT file, then all messages from that mailing >           list will be delivered to the folder, rather to your!           default NEWMAIL folder.   L           __________________________________________________________________  '    1.7    Delivery Status Notifications   <           MX supports the Internet standard form of delivery8           status notifications (DSNs), which can provide?           information on the status of a message that you send.n=           When a system supporting the DSN standards deliversc<           a message, it examines the DSN control information?           you defined for the message and determines whether itr=           should notify you about the status of the delivery.   >           To enable these notices, you must define the logical?           name MX_VMSMAIL_DSN_CONTROL. This logical name can be 3           defined with up to two separate settings:e  >           o  a setting to specify when you want to be notified8              about the status of message deliveries, and  @           o  a setting to specify how much of the message should8              be returned along with the delivery notice.  %           ___________________________       1.7.1  Notification Settings   ;           The notification setting is specified as follows:_  N                            $ DEFINE MX_VMSMAIL_DSN_CONTROL "NOTIFY=type[,...]"  <           where type can be one of these notification types:  >           NEVER              Specifies that you do not want to>                              be notified about the delivery of;                              the message, even if it fails.   A                                                               1-9  c  e    .           Using Message Exchange with VMS MAIL            :           SUCCESS            Specifies that you want to be?                              notified about successful deliverye>                              of the message, or if it has been<                              successfully relayed to another?                              system that does not support DSNs.   :           FAILURE            Specifies that you want to be@                              notified if delivery of the message#                              fails.a  :           DELAY              Specifies that you want to be@                              notified if delivery of the message8                              is delayed for some reason.  =           If you specify NOTIFY=NEVER, you cannot specify anya>           other notification type. Other types may be combined6           by separating the type keywords with commas.  ;           Note that for SUCCESS notifications, notificatione<           of the successful delivery of the message may only>           be notification of a "relay" to another system. This>           happens if a remote system does not support DSNs, or@           the message is sent to a remote system using a protcol;           that is not capable of transmitting DSN requests.   %           ___________________________   '    1.7.2  Returned-Information Settings   9           The setting for returned information is either:   K                            $ DEFINE MX_VMSMAIL_DSN_CONTROL "RETURN=HEADERS"   ?           which specifies that you only want the RFC822 messageq@           headers included in the returned notification message,
           or:t  H                            $ DEFINE MX_VMSMAIL_DSN_CONTROL "RETURN=FULL"  :           which specifies that you want the entire message8           included in the returned notification message.             1-10 r  V    A                              Using Message Exchange with VMS MAILs          <           If you do not specify a RETURN setting, the system9           that issues the delivery status notification isg?           allowed to choose whether it should return the entirer&           message or just the headers.  %           ___________________________        1.7.3  Combining the Settings  9           You may specify both notification and returned-t=           information settings by separating the two settings /           with one or more blanks. For example:t  b                            $ DEFINE MX_VMSMAIL_DSN_CONTROL "NOTIFY=SUCCESS,FAILURE RETURN=HEADERS"  <           This DSN control string specifies that you want to>           be notified if the message is delivered successfully?           or if it fails, and you want only the message headersi)           included with the notification.   %           ___________________________D      1.7.4  Limitations   @           Because DSN settings are controlled by a logical name,?           they apply to all recipients of all messages you send ?           while the logical name is defined. You cannot specify >           per-message or per-recipient settings while using MX.           through VMS MAIL or DECwindows Mail.  L           __________________________________________________________________  !    1.8    Network Delivery Delays(  >           Messages sent over any network can be delayed due to<           network outages, system loading, or other reasons.=           Once a message leaves the local system, there is noa<           way to determine where the message may be held up.>           However, messages still on the local system awaiting>           network transfer can be displayed with the MAILQUEUE           utility:  1                            $ RUN MX_EXE:MAILQUEUEu  A                                                              1-11e p       .           Using Message Exchange with VMS MAIL          =           MAILQUEUE lists any messages you have sent that are @           waiting for network transfer. All messages that cannot;           be sent are tried periodically, based on settings >           established by your system manager. If the number of@           attempts exceeds the established limit, the message is>           returned to sender with a message explaining why the!           transfer did not occur.M  %           ____________________________  .    1.8.1  Displaying MX Informational Messages  8           If you want MX to display information messages8           indicating that your VMS Mail message has been:           successfully delivered to MX, you can define the@           logical MX_VMSMAIL_SHOW_INFO as shown in the following           command:  =                            $ DEFINE MX_VMSMAIL_SHOW_INFO TRUEn  @           If the logical is defined, MX displays a line like the;           following when the message has been queued to MX:   c                            %MX-I-MAIDLVR, message (entry number 22643) successfully delivered to MXw  @           An informational message will also be displayed when a,           message is sent with SEND/FOREIGN:  Q                            %MX-I-BASE64, encoding MX foreign message using BASE64S  =           Placing the MX_VMSMAIL_SHOW_INFO logical definitions?           in your LOGIN.COM will cause MX to always display the_!           informational messages._  L           __________________________________________________________________  1    1.9    Sending binary files to other VMS users   ;           The VMS Mail command SEND accepts an undocumentedo>           qualifier, /FOREIGN. SEND/FOREIGN allows you to mail<           any VMS file to another user on the same system or;           over DECnet. The file retains all of the VMS file ?           attributes. When the recipient tries to read the mailc@           message containing the file, the following information           is displayed:              1-12 e  -    A                              Using Message Exchange with VMS MAIL           E               #2          14-APR-1993 15:28:02.11             NEWMAILn           From:   GOATHUNTER           To:     GOATHUNTER
           CC:i           Subj:   RESET.EXEr  5           You cannot read this foreign format message Q                   Use the EXTRACT command to copy the message to an external filee             MAIL>   =           The EXTRACT command copies the message to the named <           external file with all VMS file attributes intact.  ;           The SEND/FOREIGN command can also be used to sendd<           VMS binary files through MX, if the target user is>           on a system running MX V3.3 or higher, MultiNet V3.3>           or higher, or PMDF V4.1 or higher. When SEND/FOREIGN<           is used, MX encodes the message using an algorithm8           called BASE64, which is defined in RFC 1341, a>           document describing MIME (Multipurpose Internet Mail>           Extensions). The BASE64-encoded file is wrapped in a>           MIME-compliant message and mailed to the recipients.>           When the message is received on a system running the?           appropriate versions of either MX, MultiNet, or PMDF, :           the encoded binary file is automatically decoded=           and mailed to the local user as a foreign file. They@           recipient will receive two messages-one containing the?           headers for the message, and the other containing thei&           foreign file as shown above.  2           The MIME "Content-Type:" for the file is@           "APPLICATION/VMS-RMS". MX will automatically recognize>           and decode incoming "VMS-RMS" files that are encoded:           using BASE64, as well as QUOTED-PRINTABLE files.  ?           Note: The encoding done by MX is only compatible witha>           the VMS mailers specified above. SEND/FOREIGN cannot@           be used to send binary files to non-VMS MIME-compliant           mailers.  A                                                              1-13t         .           Using Message Exchange with VMS MAIL          =           The following example demonstrates sending a binaryi           file through MX:  !                            $ mailb  @                            MAIL> send/noedit/foreign program.exe5                            To:     MX%"gene@KISS.COM"eJ                            Subj:   Here is that program I promised to send  C                            Encoding MX foreign message using BASE64 T                            Message (entry number 22244) successfully delivered to MX                               MAIL>  ?           Note: Non-VMS recipients or VMS recipients on systems =           not running the appropriate software will receive a <           single message containing the BASE64-encoded file.@           This message will most likely be meaningless for those           recipients.w  >           From the DCL prompt, the command MAIL/FOREIGN can be?           used to send a binary file to one or more recipients:n  ^                            $ mail/foreign/subj="My LOGIN.COM" login.com "mx%""user@node.edu"""                                           1-14 n  n                A           _______________________________________________________       2      The MXALIAS Utility       ?           MXALIAS is a simple database manager for user-definedo=           MX aliases. An alias is a name that is equated withi?           a mail address that can be used to address electronicm=           mail. For example, the address "BOB" can be equated >           with "smithjb@node1.school.edu"; it can then be used?           in VMS Mail by specifying MX%BOB at the "To:" prompt:   %                            MAIL> SEND )                            To:     MX%BOBe'                            Subj:   ....   =           MX aliases are stored, by default, in a file calledh7           MX_ALIAS_DATABASE.DAT in your login directoryb<           (SYS$LOGIN:). You can define the MX_ALIAS_DATABASE<           logical in your LOGIN.COM to relocate the database           file:g  P                            $ DEFINE MX_ALIAS_DATABASE dev:[user.MAIL]ALIASES.DAT  8           MXALIAS will automatically create the MX alias>           database the first time you add an alias definition.  @           MXALIAS can be executed by setting up a foreign symbol           in your LOGIN.COM:  <                            $ mxalias :== $mx_exe:mxalias.exe  =           Your system manager may have already defined it fors>           you in the system login procedure. You can also just0           use RUN MX_EXE:MXALIAS to run MXALIAS.  ?           When MXALIAS is invoked without any parameters on thee=           DCL command, your are put into an interactive mode. #           The prompt is "MXalias>":E  $                            $ mxalias#                            MXalias>1  A                                                               2-1m    r               The MXALIAS Utilitya          <           At the MXALIAS prompt, you can ADD aliases, MODIFY>           them, REMOVE them, and list them using the DIRECTORY<           command. There is on-line help available by typing&           HELP at the MXalias> prompt.  L           __________________________________________________________________      2.1    Adding an MX Alias  <           The MXALIAS command ADD is used to add an alias to=           the database. ADD takes three parameters: the alias <           to define, the equivalent address, and an optional@           description for the alias. The following example shows           a typical definition:   ^                            MXalias> add joe "smith@somewhere.com" "Joe Smith, Somewhere, Inc."?                            Added alias JOE to MX alias database #                            MXalias>o  >           The alias, JOE in the example above, can be a string<           of up to 20 alphanumeric characters (plus $, -, _,?           and .) that is equated with the given e-mail address.t@           The alias is the address given to MX from the VMS Mail>           "To:" line using a format like MX%alias. All aliases%           are converted to uppercase.   ?           The given address must be a valid address in the formc<           "user@host". If the domain is omitted, it defaults:           to the local host (as defined by the MX_VMSMAIL_?           LOCALHOST logical). The maximum length of the addressl=           is 255 characters. If you want to preserve the case ;           of an address, or if the address contains the "!" <           character, you must enclose the address in double-=           quotes. If the address includes quotes, the addresss:           should be quoted, with the inside quotes doubled$           ("""node::user""@domain").  ;           The description is any quoted string of up to 255l9           characters. The description is displayed by then;           DIRECTORY command; it is not included in the mail *           headers of the outgoing message.  
           2-2.         A                                               The MXALIAS Utility         L           __________________________________________________________________      2.2    Using an MX AliasL  9           Once an MX alias has been added to the MX alias =           database, it can be used on the VMS Mail "To:" line >           by simply prefixing the alias name with MX%. MX will;           check every address that does not include the "@" @           character to see if it is an MX alias. For example, if>           JOE is defined as an alias, the following "To:" line           would be specified:_  %                            MAIL> SENDm)                            To:     MX%JOEo'                            Subj:   ....   <           Sending to MX%"JOE@localhost" will prevent MX from?           performing the alias translation, in case you want tom-           send mail to a local user name JOE.o  %           ___________________________o  0    2.2.1  Disabling System-Wide MX Alias Lookups  ;           MX supports both a personal MX alias database and :           a system-wide (global) alias database created by:           your system manager. If an alias is not found in=           your personal database, MX will see if it's definede=           in the global database and, if so, it will use thatI:           definition. If your system manager has defined a9           global database and you wish to prevent MX from <           accessing it, you can do so by using the following           command:  A                            $ define mx_global_alias_database _nl:h  <           That command causes MX to attempt to open the null:           device as the global database, which effectively0           disables a system-wide alias database.    A                                                               2-3_ _  _               The MXALIAS Utilityi        %           ___________________________o  ,    2.2.2  Displaying MX Address Translations  ?           To see the resulting addresses used by MX for all MX%o?           addresses, define the logical MX_VMSMAIL_SHOW_ADDR asn           TRUE:i  =                            $ define mx_vmsmail_show_addr truet!                            $ mail   %                            MAIL> SENDnN                            To:     MX%JOE, MX%"MX-List@WKUVX1.WKU.EDU", SYSTEML                              MX rewrote alias JOE as <SYSTEM@WKUVX1.WKU.EDU>Z                              MX rewrote MX-List@WKUVX1.WKU.EDU as <MX-List@WKUVX1.WKU.EDU>'                            Subj:   ....t  >           The MX_VMSMAIL_SHOW_ADDR works regardless of whether=           or not MX aliases are specified. If you always wantc@           to see MX address translations, you can put the DEFINE$           command in your LOGIN.COM.  L           __________________________________________________________________      2.3    Displaying Aliases  :           The MXALIAS command DIRECTORY is used to display?           your defined aliases. By default, the brief directoryn@           listing shows only the alias and the comment, if there           is one:o  '                            MXalias> dir   <                            MX Alias              Description<                            ------------          -----------K                            JOE                   Joe Smith, Somewhere, Inc.g  #                            MXalias>   @           Wildcards can be given to limit the display to aliases@           matching the given pattern. The DIRECTORY/FULL command>           can be used to show the equivalent e-mail addresses.  =           The /OUTPUT=file qualifier can be used to write the +           directory listing to a text file.S  
           2-4  L       A                                               The MXALIAS Utilityn        L           __________________________________________________________________      2.4    Modifying Aliasesa  @           The MODIFY command is used to modify an existing alias>           definition. It accepts the alias name as a parameter;           and the qualifiers /ADDRESS and /DESCRIPTION. For            example:  Q                            MXalias> MODIFY JOE/DESCRIPTION="Local system manager" -                            Modified alias JOEa#                            MXalias>t  L           __________________________________________________________________      2.5    Removing Aliases  7           The REMOVE command is used to remove an aliasd<           definition from the MX alias database. By default,>           it prompts the user for confirmation before removing           the specified alias:  .                            MXalias> remove joeD                            Remove JOE <SYSTEM@WKUVX1.WKU.EDU> [N]? y,                            Removed alias JOE#                            MXalias>L  =           You can supply the qualifier /NOCONFIRM to overridet"           the confirmation prompt.                        A                                                               2-5     D                A           _______________________________________________________n  "    3      Electronic Mailing Lists      >           When talking about electronic mail, the term mailing>           list is generally used to describe an E-mail address?           that forwards messages to more than one user. Mailing <           lists abound on the Internet and BITNET, on a wide8           variety of technical and non-technical topics.  6           Unfortunately, there are no standards on the<           implementation of mailing lists, so their use will<           vary depending on the systems on which the mailing>           lists are set up. For the most part however, mailing8           lists can be broken down into two basic types:           Internet and BITNET.  L           __________________________________________________________________      3.1    Internet-Style Lists  7           For an Internet-style mailing list, there ares;           generally two addresses: one for the mailing list ;           itself, and one for "administrivia" (subscriptionh@           requests, etc.). The administrative address is usually:           the mailing list name with "-request" added. For:           example, the mailing list for discussing Message:           Exchange is MX-List@WKUVX1.WKU.EDU. Subscription<           requests, removals, or comments about the list are1           sent to MX-List-request@WKUVX1.WKU.EDU.   7           Most Internet-style mailing lists are managed_:           manually, so mail sent to -request addresses can:           usually be free-form. However, a few systems, MX<           included, have mailing list handlers which process=           some types of requests automatically, without humana;           intervention. The syntax of the commands you sendt>           to these automated handlers will vary from system to<           system. For example, the MX mailing list processor)           accepts the following commands:   A                                                               3-1U         "           Electronic Mailing Lists            :           SUBSCRIBE          for getting added to the list  >           SIGNOFF            for getting removed from the list  6           REVIEW             for getting a list of the(                              subscribers  7           HELP               for getting a help message   ;           QUERY              for getting the status of your -                              subscriber entrys  =           SET [NO]CONCEAL    for concealing or revealing youry;                              e-mail address in REVIEW lists_  ?           SET [NO]DIGEST     for switching between reception ofg>                              regular list traffic and periodic@                              digests (only applies to lists that8                              have corresponding digests)  ;           SET [NO]MAIL       for enabling/disabling receipt =                              of list messages while remainingL3                              subscribed to the liste  >           SET [NO]REPRO      for enabling/disabling receipt of3                              your own list postings   <           QUIT               for preventing the parsing of a+                              mail signatures  <           Commands must generally be placed in the body of a8           mail message, rather than on the Subject line.  L           __________________________________________________________________      3.2    BITNET-Style Lists  <           Most mailing lists on BITNET hosts are implemented>           using LISTSERV, a package developed specifically for>           automated handling of mailing lists. One LISTSERV on=           a system, at address LISTSERV@hostname, manages all @           the mailing lists offered on that system, and provides4           automatic administrative request handling.  
           3-2t    r    A                                          Electronic Mailing Listst          >           LISTSERV will usually handle the following commands:  :           SUBSCRIBE list-    for getting added to the list           name  >           SIGNOFF list-name  for getting removed from the list  6           REVIEW list-name   for getting a list of the(                              subscribers  ;           QUERY list-name    for getting the status of your -                              subscriber entry   7           HELP               for getting a help messages  <           LIST               for getting a list of available*                              mailing lists  6           Along with several more. The MX mailing list;           processor, MXSERVER, also provides LISTSERV-stylel:           command handling, but supports only the commands9           listed above plus a QUIT command to prevent thes4           unintentional parsing of a mail signature.                                  A                                                               3-3F I                   A           _______________________________________________________6      4      Network File Servers      8           The term file server, for the purposes of this?           document, refers to a network entity that maintains a @           library of files and delivers them to users on demand.  @           As with mailing lists, there are no standards for file@           servers. There are several file server implementations8           in existence: LISTSERV, VMSSERV, MAILSERV, and@           several others. MX also includes a file server module,?           generally referred to as FileServ. Some of these file @           servers accept commands via BITNET immediate messages,=           some only by E-mail messages. Some take commands on-@           the subject line of a message, and some in the body of@           a message. The way files are distributed can also vary            from server to server.  L           __________________________________________________________________      4.1    Get HELP  =           If you want to obtain files from a file server, andE=           you are unsure of the commands you need to use, youI>           should begin by requesting help information from the>           server. The best way to do this is to send an E-mail<           message to the file server's address with the word<           HELP on the subject line and on the first and only<           line of the body of the message. Most servers will;           mail you back a message listing the commands they ?           accept and the format the commands should take, along )           with other helpful information.   ;           If you cannot get assistance from the file serveri6           itself, you may be able to get some from the1           postmaster on the file server's system.   A                                                               4-1i n  o               Network File Servers        L           __________________________________________________________________      4.2    MX FileServ Commands  >           The MX file server, usually called FileServ, accepts;           commands, one command per line, in the body of anc6           E-mail message. The commands it accepts are:  <           ADDRESS valid-     provides a valid e-mail address           addressu  8           LIST [pattern]     lists all packages matching&                              "pattern"  )           DIRECTORY          same as LIST_           [pattern]_  ;           SENDME             sends an entire package or the +           package[.part]     specified partr  1           HELP               sends a help message   <           QUIT               causes any lines following this2                              command to be ignored  @           FileServ commands may be abbreviated to their shortest           unique string.  ?           ADDRESS provides the user with the ability to specify:>           a valid RFC822-compliant e-mail address to which any<           FileServ output is to be sent. Normally, any files@           requested from FileServ are sent to the address in the>           "Reply-To:" or "From:" lines in the message headers.@           However, addresses are sometimes corrupted by gateways;           through which the message passes, resulting in ana?           invalid return address. File server users can use theI=           ADDRESS command to provide a valid alternate to thel           "From:" address.  >           Note: When an ADDRESS command is processed, the file>           server transaction log includes the original "From:"?           address. Any user receiving unasked-for files can use 5           it to determine from whom the request came.s  
           4-2  e  r    A                                              Network File Serversc        %           ___________________________t      4.2.1  Packages  9           A package is a collection of related files that :           are grouped together for distribution. FileServ,=           along with other file servers, distributes files in ;           packages. These packages are usually in a special >           format for distribution over the network via E-mail;9           once you collect all of the parts in a package, <           the parts are combined together and fed through an;           unpacking program (sometimes contained within the @           package itself) to recreate the original collection of           files.  %           ____________________________      4.2.2  Binary Files  :           Because E-mail systems generally do not properly>           handle binary data, binary files (such as executable;           images or compressed files) are generally encoded 9           before being packaged and distributed by a file =           server. Once unloaded from the package, the encodeds@           file must then be decoded to recreate the binary file.?           The type of encoding will vary from system to system."  ;           In addition, large files may be compressed befores8           being encoded and packaged, to cut down on the:           network bandwidth required when transmitting the=           package. Restoring the original files then requiresn.           an additional decompression program.                  A                                                               4-3: i  u                A           _______________________________________________________       A      Message Header Format       ;           Most network mail systems require or include morei>           information about messages than VMS MAIL can handle.>           MX, for example, follows the Internet message format>           standard, usually called RFC 822 after the number of1           the document that describes the format.f  =           When you receive a message via MX, the FROM addressl@           identified in the VMS MAIL headers will begin with the?           MX% prefix, which allows you to REPLY to the message.s<           In addition to the VMS MAIL headers, you will also>           see the RFC 822 header information, which is usually?           displayed as the first part of the message text (this :           is under the control of the system manager). For           example:  `                                #1          29-FEB-1992 10:36:22.11                       NEWMAILB                            From:   MX%"naive@myhost.mycompany.com"*                            To:     MANAGER                            CC:+                            Subj:   Questiona                            A                                                               A-1n h  l               Message Header Format           D                            Return-Path: <naive@myhost.mycompany.com>a                            Received: from myhost.mycompany.com by mgrsta.mycompany.com (MX V3.0);eB                                      Thu, 29 Feb 1992 10:35:10 ESTa                            Received: by myhost.mycompany.com (MX V3.0) id 31437; Thu, 29 Feb 1992 1                                      10:35:05 EST E                            Resent-Date: Thu, 29 Feb 1992 10:35:01 EST C                            Resent-From: system@myhost.mycompany.com_B                            Resent-To: manager@mgrsta.mycompany.com?                            Sender: <naive@myhost.mycompany.com> >                            Date: Thu, 29 Feb 1992 10:34:55 ESTH                            From: Naive User <naive@myhost.mycompany.com>?                            Reply-To: naive@myhost.mycompany.comgU                            Message-ID: <00933068.08a17f00.31437@myhost.mycompany.com>g:                            To: system@myhost.mycompany.com,                            Subject: Question  0                            How do I send E-mail?  ?           The first five lines of this message are the VMS MAILl;           headers. The message text starts with the RFC 822 @           headers, followed by the message itself. The following>           sections explain the meaning of the RFC 822 headers.  ;           Return-Path. The return address as appears on the_>           envelope of the message. This usually identifies the>           route the message took in getting to you, and can be=           used to identify forged messages in some cases. The @           return path is used as the VMS MAIL From address if no%           other address is available.   ;           Received. There may be several of these lines for ;           a message. They usually indicate how and when theS=           message was transferred from one system to another.U<           They are provided for informational purposes only.  @           Resent- lines. If the message is forwarded (usually by;           an automatic mechanism such as SET FORWARD in VMS :           MAIL), some messaging systems (MX included) will=           include information about when it was forwarded andt:           who it was forwarded to. One set of Resent lines2           usually appears for each forwarding hop.  
           A-2n n  u    A                                             Message Header Format_          @           Sender. This line indicates the sender of the message,?           which could be different from the address in the Fromi           line.   9           Date. This line indicates the date and time thea9           message was entered into the mail system by the <           sender. It will usually include the local time for<           the sender, which may be in a different time zone.  <           From. This line indicates who the message is from.9           If the message was sent by someone on behalf of @           another person or group, the message will also include;           a Sender line to identify the person or agent whoe$           actually sent the message.  =           Reply-To. If the sender wants to receive replies at @           an address different from the From address, a Reply-To8           line will be included to redirect the replies.  @           Message-ID. The message identifier uniquely identifies?           a message. Message-ID's are used by some mail systems_,           for tracking messages and replies.  9           To. Identifies the target user or users for thei=           message. Also included can be CC and BCC lines thats:           identify users to whom a carbon copy and "blind"-           carbon copy of the message is sent.   <           Subject. A brief description of the subject of the           message.  <           Other headers are also possible, some of which are?           extensions to the RFC 822 message standard. Also, the_@           order in which the headers appear may vary from system           to system.  L           __________________________________________________________________      A.1    VMS MAIL Headers  @           MX automatically translates some of the RFC 822 header,           information into VMS MAIL headers.  A                                                               A-3V W  E               Message Header Format         %           ___________________________M      A.1.1  From Header   @           There are several RFC 822 headers used for identifying@           the originator of a message. VMS MAIL, however, allows@           only one. To allow the REPLY command to work properly,<           therefore, MX fills in the VMS MAIL From line with9           the address that should be used in generating a ;           reply. This reply address is selected from one of =           the following header lines, listed here in order of            preference:g             1  Reply-To              2  Fromi             3  Sendern             4  Return-Path  @           MX will only use the address from one of these headers?           if it is syntactically valid. Since most mail systemsa=           provide a valid address in the Reply-To and/or Fromi0           headers, this should not be a problem.  %           ___________________________e      A.1.2  To and CC Headers   ;           The VMS MAIL To and CC headers will list only theT=           users on the local system receiving the message. To_@           see the actual list of recipients, examine the To, CC,/           and BCC lines in the RFC 822 headers.   %           ___________________________r      A.1.3  Subject Header  @           The VMS MAIL Subject header should be identical to the0           RFC 822 Subject header, if one exists.  
           A-4a