                                       +           Message Exchange Management Guide                  October, 1998       <           This manual describes the management and operation?           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                                        ix   A           _______________________________________________________ 1           CHAPTER 1  OVERVIEW OF MESSAGE EXCHANGE A                      OPERATION                                1-1   A                 _________________________________________________ A                 1.1   WHAT IS A MESSAGE?                      1-1   A                 _________________________________________________ A                 1.2   WHAT IS AN ADDRESS?                     1-2   A                 _________________________________________________ A                 1.3   MX COMPONENTS                           1-3   A                 1.3.1     The Message Queue  _____________    1-4   A                 1.3.2     Message Entry Agents  __________    1-4   A                 1.3.3     The Router  ____________________    1-5   A                 1.3.4     Delivery Agents  _______________    1-6   A                 1.3.5     MLF Agent  _____________________    1-7   A           _______________________________________________________ A           CHAPTER 2  CONFIGURING MX WITH MXCONFIG             2-1   A                 _________________________________________________ A                 2.1   WHY USE MXCONFIG?                       2-1   A                 _________________________________________________ A                 2.2   USING MXCONFIG                          2-1         A                                                               iii                     Contents          A           _______________________________________________________ A           CHAPTER 3  MANAGING THE ROUTER                      3-1   A                 _________________________________________________ A                 3.1   REWRITE RULES                           3-1   A                 _________________________________________________ A                 3.2   DEFINING DELIVERY PATHS                 3-2   A                 3.2.1     DOMAIN.NAMES Paths  ____________    3-3   A                 _________________________________________________ A                 3.3   ALIAS TRANSLATION                       3-4   A                 _________________________________________________ A                 3.4   CONTROLLING THE ROUTER PROCESS          3-5   A                 _________________________________________________ A                 3.5   LOGGING ROUTER EVENTS                   3-5   A           _______________________________________________________ A           CHAPTER 4  MANAGING THE DELIVERY AGENTS             4-1   A                 _________________________________________________ A                 4.1   LOCAL DELIVERY OPTIONS                  4-1   A                 _________________________________________________ 5                 4.2   SMTP, DECNET_SMTP, AND X25_SMTP A                       DELIVERY OPTIONS                        4-1   3                 4.2.1     Internet "Mail Exchanger" A                           Support  _______________________    4-2   A                 4.2.2     Default SMTP Router  ___________    4-2   A                 _________________________________________________ A                 4.3   THE JNET INTERFACE                      4-3   A                 4.3.1     Jnet Address Conversion  _______    4-3   A                 4.3.2     Gateway Policy  ________________    4-4              iv         A                                                          Contents           A                 4.3.3     Jnet Node Name  ________________    4-4   A                 4.3.4     Mailer Username  _______________    4-4   6                 4.3.5     XMAILER.NAMES, DOMAIN.NAMES,A                           and BITEARN.NODES Files  _______    4-5 >                 4.3.5.1     BITEARN.NODES and MXBITNET.MAILERS&                             Files, 4-63                 4.3.5.2     XMAILER.NAMES File, 4-8 2                 4.3.5.3     DOMAIN.NAMES File, 4-8  A                 _________________________________________________ A                 4.4   UUCP DELIVERY OPTIONS                   4-9   A                 _________________________________________________ A                 4.5   SITE DELIVERY OPTIONS                  4-10   A                 _________________________________________________ A                 4.6   THE LISTSERV INTERFACE                 4-10   A                 _________________________________________________ A                 4.7   SHUTDOWNS AND RESETS                   4-10   A                 _________________________________________________ A                 4.8   LOGGING DELIVERY AGENT EVENTS          4-11   A           _______________________________________________________ A           CHAPTER 5  MANAGING MESSAGE ENTRY AGENTS            5-1   A                 _________________________________________________ A                 5.1   LOCAL MESSAGE ENTRY                     5-1   4                 5.1.1     System-wide MX Aliases forA                           Outgoing Addresses  ____________    5-2   A                 5.1.2     VMS MAIL Protocol Prefix  ______    5-2   A                 5.1.3     Default Host Names  ____________    5-3   -                 5.1.4     Disabling Automatic A                           Quoted-Printable Encoding  _____    5-4   A                                                                 v                     Contents          A                 _________________________________________________ A                 5.2   SMTP_SERVER                             5-4   A                 _________________________________________________ A                 5.3   DECNET_SMTP NETWORK OBJECT              5-5   A                 _________________________________________________ A                 5.4   X25_SMTP NETWORK OBJECT                 5-6   A                 _________________________________________________ A                 5.5   MESSAGE ENTRY AGENT SHUTDOWNS           5-8     A           _______________________________________________________ A           CHAPTER 6  MANAGING THE MESSAGE QUEUE               6-1   A                 _________________________________________________ A                 6.1   ESTABLISHING THE QUEUE SIZE             6-1   A                 _________________________________________________ A                 6.2   RUNNING THE MX FLQ MANAGER              6-1   A                 _________________________________________________ A                 6.3   QUEUE CLEANUP LOGICALS                  6-2   A                 _________________________________________________ 9                 6.4   AUTOMATIC PURGING OF FINISHED QUEUE A                       ENTRIES                                 6-3   A                 _________________________________________________ A                 6.5   THE MCP QUEUE COMMANDS                  6-4   5                 6.5.1     Interpreting MCP QUEUE SHOW A                           Output  ________________________    6-4   0                 6.5.2     Interpreting MCP QUEUEA                           STATISTICS Output  _____________    6-6                  vi         A                                                          Contents           A           _______________________________________________________ 1           CHAPTER 7  CONFIGURING MX FOR PART-TIME A                      INTERNET CONNECTIONS                     7-1   A                 _________________________________________________ /                 7.1   ENVIRONMENT FOR PART-TIME A                       CONNECTIONS                             7-1   A                 _________________________________________________ 3                 7.2   CONFIGURING MX AS A PART-TIME A                       CLIENT                                  7-1   A                 _________________________________________________ 4                 7.3   CONFIGURING MX AS A SERVER FORA                       PART-TIME CLIENTS                       7-2   A                 _________________________________________________ A                 7.4   ETRN SUPPORT                            7-3   A                 _________________________________________________ A                 7.5   EXAMPLE CONFIGURATION                   7-5     A           _______________________________________________________ 3           CHAPTER 8  REDUCING OR ELIMINATING "JUNK" A                      E-MAIL                                   8-1   A                 _________________________________________________ A                 8.1   WHAT IS "JUNK" E-MAIL?                  8-1   A                 _________________________________________________ A                 8.2   MX FILTERING FEATURES                   8-2   A                 _________________________________________________ A                 8.3   SENDER VALIDATION                       8-2   A                 _________________________________________________ A                 8.4   DISABLING THE SMTP RELAY FUNCTION       8-3     A                                                               vii                     Contents          9                 8.4.1     Identifying Inside Networks and A                           Hosts  _________________________    8-5   A                 _________________________________________________ A                 8.5   REALTIME BLACKHOLE LIST                 8-6   A                 8.5.1     Other RBL Providers  ___________    8-7   A                 _________________________________________________ 5                 8.6   ESTABLISHING REJECTION CRITERIA A                       WITH REJMAN                             8-7   A                 8.6.1     Address-Based Rejections  ______    8-8   A                 8.6.2     Header-based Rejections  _______    8-9   A                 8.6.3     Tracking Rejections  ___________   8-11   A                 8.6.4     Purging Old Rules  _____________   8-11   A                 _________________________________________________ A                 8.7   HEURISTIC FILTERS                      8-12   A                 8.7.1     Confidence Levels  _____________   8-13   A                 8.7.2     Rejection Actions  _____________   8-18   A                 8.7.3     Junk Mail Warnings  ____________   8-18   A                 _________________________________________________ A                 8.8   LOGGING SMTP SERVER REJECTIONS         8-19   A                 _________________________________________________ 3                 8.9   DEBUGGING REJECTION RULES AND A                       HEURISTIC FILTERS                      8-19   A           _______________________________________________________ A           CHAPTER 9  OTHER MISCELLANEOUS UTILITIES            9-1   A                 _________________________________________________ A                 9.1   THE MLFAKE UTILITY                      9-1   A                 _________________________________________________ A                 9.2   THE MAILQUEUE UTILITY                   9-2              viii         A                                                          Contents           A                 _________________________________________________ A                 9.3   THE MX_DECODE UTILITY                   9-3     A           _______________________________________________________ A           CHAPTER 10  TROUBLESHOOTING MX                     10-1   A                 _________________________________________________ A                 10.1  QUEUE FILES USED BY MX COMPONENTS      10-1   A                 10.1.1    File Types  ____________________   10-2   A                 _________________________________________________ A                 10.2  PROCESS NAMES                          10-3   A                 _________________________________________________ A                 10.3  DEBUG/TRACE OUTPUT                     10-4   A           _______________________________________________________ A           CHAPTER 11  THE MX STARTUP PROCESS                 11-1   A                 _________________________________________________ A                 11.1  STARTUP COMMAND PROCEDURES             11-1   A                 _________________________________________________ A                 11.2  STARTUP DATA FILES                     11-2     A           _______________________________________________________               MCP COMMAND DICTIONARY:                 MCP                                  MCP-3:                 @ (REDIRECT COMMAND INPUT)           MCP-5:                 ATTACH                               MCP-6:                 DEFINE/KEY                           MCP-8:                 DEFINE ALIAS                         MCP-9:                 DEFINE FILE_SERVER                  MCP-10:                 DEFINE INSIDE_NETWORK_ADDRESS       MCP-14:                 DEFINE LIST                         MCP-16  A                                                                ix                     Contents          :                 DEFINE LOCAL_DOMAIN                 MCP-27:                 DEFINE PATH                         MCP-29:                 DEFINE REWRITE_RULE                 MCP-31:                 DEFINE SYSTEM_USERS                 MCP-33:                 EXIT                                MCP-35:                 HELP                                MCP-36:                 MODIFY                              MCP-37:                 QUEUE CANCEL                        MCP-38:                 QUEUE COMPRESS                      MCP-39:                 QUEUE CREATE                        MCP-41:                 QUEUE EXTEND                        MCP-42:                 QUEUE PURGE                         MCP-43:                 QUEUE READY                         MCP-44:                 QUEUE SHOW                          MCP-45:                 QUEUE STATISTICS                    MCP-49:                 QUEUE SYNCHRONIZE                   MCP-50:                 QUIT                                MCP-51:                 REMOVE                              MCP-52:                 RESET                               MCP-53:                 REVIEW                              MCP-55:                 SAVE                                MCP-56:                 SET DECNET_SMTP                     MCP-57:                 SET JNET                            MCP-59:                 SET LOCAL                           MCP-62:                 SET MLF                             MCP-66:                 SET ROUTER                          MCP-68:                 SET SITE                            MCP-70:                 SET SMTP                            MCP-71:                 SET X25_SMTP                        MCP-75:                 SHOW                                MCP-77:                 SHUTDOWN                            MCP-79:                 SPAWN                               MCP-81:                 STATUS                              MCP-82                         x  t       A                                                          Contents           A           _______________________________________________________m  #           REJMAN COMMAND DICTIONARY-;                 REJMAN                             REJMAN-3r;                 COMMAND INPUT REDIRECTION          REJMAN-5 ;                 ADD EXCLUSION                      REJMAN-6M;                 ADD REJECTION                      REJMAN-7 <                 ATTACH                             REJMAN-11<                 CHECK                              REJMAN-13<                 DEFINE/KEY                         REJMAN-15<                 DELETE EXCLUSION                   REJMAN-16<                 DELETE REJECTION                   REJMAN-18<                 DISABLE HEURISTIC                  REJMAN-19<                 ENABLE HEURISTIC                   REJMAN-20<                 EXIT                               REJMAN-22<                 HELP                               REJMAN-23<                 QUIT                               REJMAN-24<                 PURGE                              REJMAN-25<                 SAVE                               REJMAN-26<                 SET HEURISTICS                     REJMAN-27<                 SHOW                               REJMAN-30<                 SPAWN                              REJMAN-32    A           _______________________________________________________            INDEX_    A           _______________________________________________________            FIGURES   A                 1-1       Message parts  _________________    1-2                 A                                                                xi  .                  Contents          A           ________________________________________________________           TABLES  4                 5-1       Address Formatting LogicalA                           Names  _________________________    5-3_  ,                 6-1       FLQ Manager/RouterA                           queue-related logicals  ________    6-2g  A                 8-1       Heuristic Filters  _____________   8-14n  A                 10-1      Debug/Trace logical names  _____   10-5r  6                 11-1      Component names for use withA                           MX_STARTUP.COM  ________________   11-1   1                 MCP-1     Mailing list protection A                           classes  _______________________ MCP-21   A                 MCP-2     Mailing list protection codes  _ MCP-21   A                 MCP-3     Typical protection codes  ______ MCP-22   A                 MCP-4     Header name keywords  __________ MCP-63   A                 MCP-5     MCP STATUS Descriptions  _______ MCP-83                             
           xii                    A           _______________________________________________________              Preface   >           This guide describes the management and operation of            Message Exchange (MX).  L           __________________________________________________________________             Intended Audience_  ?           This manual is intended for use by the system manager :           or any individual responsible for installing and8           maintaining MX. The reader should be generally<           familiar with VMS system concepts, electronic mail-           systems and networking terminology.   L           __________________________________________________________________             Document Structure  @           This guide consists of two parts. Part I contains nine>           chapters which contain information on management and<           operation of the various components of MX. Part II>           is the command dictionary for the MX Control Program           (MCP).  ;           Chapter    Contains information about how Message_'           1          Exchange operates.E  A           Chapter    Describes how to use the MXCONFIG procedure.            2_  7           Chapter    Describes how to manage the Router            3          functions.   A           Chapter    Describes how to manage the message delivery_           4          agents.  >           Chapter    Describes how to manage the message entry           5          agents.  ?           Chapter    Describes how to manage the message queue.            6   ?           Chapter    Describes some miscellaneous MX utilities.            7e  A                                                                ix_ _  _               Preface_            6           Chapter    Describes the tools available for(           8          troubleshooting MX.  6           Chapter    Describes the MX startup process.           9   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 User's Guide describes MX features(              available to general users.  >           o  Message Exchange Programmer's Guide describes the0              programmable customization features  <           o  Message Exchange Mailing List/File Server Guide7              describes the MX Mailing List/File Server._  ?           o  Message Exchange Release Notes contain informationVA              and updates not included in this manual. The release_=              notes are part of the software distribution kit.E  A           o  RFC 821: Simple Mail Transfer Protocol describes the_              SMTP protocol._  >           o  RFC 822: Standard for the Format of ARPA Internet>              Text Messages describes the format of headers and.              addresses used by Internet hosts.  8           o  RFC 1123: Requirements for Internet Hosts -8              Application and Support provides additional<              information on SMTP support for Internet hosts.             x_ _  _                A           _______________________________________________________N  0    1      Overview of Message Exchange Operation      9           This chapter briefly describes how MX operates.   L           __________________________________________________________________      1.1    What is a Message?  >           Electronic mail messages are usually divided up into           three parts:  A           o  The envelope. Much like an envelope used for mail ineA              the real world, an electronic mail envelope includes A              a return address and destination information. Unlikec>              real mail, however, one message can have multipleA              destinations. In addition, addresses on the envelope :              can be changed as they pass through a system.  =           o  The headers. Message headers include information :              about the message that the recipient will see?              when he or she reads the message. This informationB@              includes the date the message was sent, the subjectA              of the message, who sent it and who will receive it,O@              and which systems the message passed through on its"              way to the recipient.  :           o  The body. This is the message text itself, as>              entered by the person (or other entity) that sent              the message.   <           There are several standards for the format of each@           part of a message. MX uses the Internet RFC 822 format<           for message headers and body, and Internet RFC 821@           format for envelope information. When sending messages<           to non-Internet sites, MX will convert the message@           format as needed to comply with the standards required@           by the destination system. Figure 1-1 is an example of/           a message broken down into its parts._  A                                                               1-1N F  N    0           Overview of Message Exchange Operation        #           Figure 1-1  Message parts A           _______________________________________________________              Envelope:M  4               <user1@host1.org>       Return address2               <user2@host2.org>       Recipient #12               <user3@host3.org>       Recipient #2             Headers:  W               Received: from host1.org by host2.org with SMTP; 01 Oct 1990 12:32:01 EDT 1               Date: Mon, 01 Oct 1990 11:19:47 EDT #               From: user1@host1.orgC!               To: user2@host2.org_!               Cc: user3@host3.org_"               Subject: Hello there             Body:   :               Just a quick note to let you know I'm alive.               Have a nice day.  A           _______________________________________________________   L           __________________________________________________________________      1.2    What is an Address?   6           Much like the address on a real envelope, an;           electronic mail address indicates where a message =           should be delivered, or where it came from. MX uses <           the Internet RFC 822 format for addresses. RFC 822>           specifies a very rich syntax for addresses, but most           are of the form:  G                                                       local-part@domain_  =           Where domain usually identifies a system and local- 2           part identifies the user on that system.  
           1-2_ _  _    A                            Overview of Message Exchange Operation                      Envelope Addresses  @           Envelope addresses are kept by MX in a special format,:           the route-address, which adheres to Internet RFC>           821. Users cannot generally use route-addresses when=           addressing mail; they are used internally by MX and =           other mail systems for tracking the route a message =           has taken to get from source to destination, or for ?           forcing a particular route to be taken for a message.   &           A route-address has the form  H                                                      <local-part@domain>?                                                              or_R                                           <@domain[,@domain...]:local-part@domain>  7           This form of addressing is discouraged on the ;           Internet, but is used when messages are gatewayed )           between multiple mail networks.e  L           __________________________________________________________________      1.3    MX Components_  5           Message Exchange consists of several parts:   ;           o  A message queue, where all messages are stored %              during processing by MX.   >           o  Message entry agents. These programs or processes@              take messages in from users or from other networked:              hosts and enter them in the message queue for              processing.  @           o  The Router. This is the "hub" of MX processing. All>              incoming messages have their envelope informationA              processed by the Router to determine how they should               be delivered.  A           o  Message delivery agents. These programs or processes_A              take messages that have been processed by the router.?              and deliver them either to local users or to other               networked hosts._  A                                                               1-3_ _  _    0           Overview of Message Exchange Operation          ;           o  The Mailing List/File Server (MLF) agent. This_>              special process handles all mailing list and file              server requests.   %           ____________________________      1.3.1  The Message Queue   >           All MX messages are stored in a directory called the?           message queue (sometimes called the file queue). This_=           is the directory pointed to by the logical name MX_ <           FLQ_DIR. Besides the files comprising the messages>           themselves, the queue directory also contains a file?           called MX_SYSTEM_QUEUE.FLQ_CTL. This file, called the @           queue control file, is a sequential file that contains=           information about the state of each message, who is ;           processing it, etc. All MX processes access their 2           queue entries through this control file.  ;           The size of the queue control file determines the_?           maximum number of entries that can be in the queue at ?           any given time. The larger the file, the more entries_#           that can be in the queue.   >           Because the message queue is shareable cluster-wide,>           a user on any node in a VMScluster can send messages<           over a network, even if there is no direct network:           connection (via TCP/IP, X.25, UUCP, etc.) on the3           particular node to the target network.[1]_  %           ___________________________2      1.3.2  Message Entry Agents  =           Messages are entered into MX by users from VMS Mail_@           through the MX% protocol prefix. This invokes routines:           in image MX_EXE:MX_MAILSHR.EXE, which create the=           necessary files in the message queue for processingT           by the Router.             ________________8         [1]  When following the MX clustering guidelines  =             described in Message Exchange Installation Guide.   
           1-4_ _  _    A                            Overview of Message Exchange OperationF          <           Messages coming in from other hosts are handled by  @           o  an SMTP server, for messages coming in over TCP/IP;  =           o  a DECnet-SMTP server, for messages coming in via               SMTP-over-DECnet;  <           o  an X.25-SMTP server, for messages coming in via              SMTP-over-X.25;  A           o  the Jnet Mail/File dispatcher and interface process,E.              for messages coming in over Jnet;  @           o  the RMAIL program, for messages coming in via UUCP;              orR  @           o  the MX_SITE_IN program, for messages coming in from1              a locally-created network interface.   9           Messages are also entered into the queue by then@           Mailing List/File Server (MLF) agent, in response to a.           mailing list or file server request.  %           ___________________________E      1.3.3  The Router  ;           The Router is responsible for taking the envelope >           information from a message and determining where the>           message should be sent based on the addresses listed           in the envelope.  @           Each recipient address in the envelope is processed in           two or three phases:  A           1  In the rewrite phase, the address is checked against @              a list of rewriting rules. If it matches one of the@              rules, the rule is applied and the original address              is replaced.-  ;           2  In the path identification phase, the next hop @              domain of the address is identified and that domain=              is checked against the domain-path mapping list. <              This identifies the delivery agent that will be?              called on to deliver the message to the recipient.E  A                                                               1-5          0           Overview of Message Exchange Operation          =           3  If the recipient is on the local system, a third @              phase is entered, which checks to see if the local-A              part of the address is an alias for another address,96              a mailing list name, or file server name.  <           The Router is also responsible for maintaining the=           message queue. It cleans out completed or cancelled            entries.  %           ___________________________       1.3.4  Delivery Agents   ?           The Local delivery agent delivers mail to local users ?           or to other hosts over DECnet using VMS Mail. It also =           identifies local users who have used SET FORWARD to =           direct their mail elsewhere and resends messages to-%           their forwarding addresses.   ?           Other delivery agents send messages to other hosts or )           other mail-processing software.   =           o  The SMTP delivery agent sends messages using the_7              Simple Mail Transfer Protocol over TCP/IP.D  @           o  The DECNET_SMTP delivery agent sends messages using;              the Simple Mail Transfer Protocol over DECnet.J  A           o  The X25_SMTP delivery agent sends messages using the ?              Simple Mail Transfer Protocol over X.25 (using VAX               P.S.I.).   @           o  The Jnet delivery agent sends messages either using>              the Batch SMTP protocol or as regular BITNET note              files.-  @           o  The UUCP delivery agent passes messages to the UUCP$              package for processing.  9           o  The SITE delivery agent passes messages to a 7              locally-created network interface package.   
           1-6J -       A                            Overview of Message Exchange Operation           ;           o  The LISTSERV delivery agent passes messages toT9              L-Soft International's LISTSERV mailing listU              processor.   ;           Each delivery agent is responsible for converting =           MX-format messages into the format required for the :           particular network or network interface package.  %           ___________________________       1.3.5  MLF Agent   ?           The Mailing List/File Server (MLF) agent is a special_>           form of delivery agent that handles mailing list and;           file server requests. It doesn't actually deliver @           messages to a network directly. What it does is create;           new messages based on the list or server requests ;           and sends the new messages back to the Router for +           processing and eventual delivery._                                          A                                                               1-7                      A           _______________________________________________________   &    2      Configuring MX with MXCONFIG      <           This chapter describes the MXCONFIG procedure, MX_           DIR:MXCONFIG.COM._  L           __________________________________________________________________      2.1    Why Use MXCONFIG?   9           Configuring MX by hand can be a complicated andA;           error-prone process, due to the number of options ;           available. Based on a question-and-answer script, =           MXCONFIG creates the MX startup information for itsa:           logical names and agent invocation, as well as a=           command file that will generate an MX configuration ?           database. Configurations created with MXCONFIG should >           be adequate for most Internet and BITNET/EARN sites;<           it can also be used as a base that can be tailored8           using the MX Control Program (MCP), if needed.  L           __________________________________________________________________      2.2    Using MXCONFIG  :           When you execute MXCONFIG, it displays a menu of            configuration options:  U                                              Message Exchange Configuration Proceduree  $                            Main Menu  K                                1. Configure MX message queue logical names.lO                                2. Configure MX host and timezone logical names. ?                                3. Configure MX agent processes._F                                4. Create an MX configuration database.;                                5. Exit from this procedure.s  (                            Enter choice:  A                                                               2-1e r  s    &           Configuring MX with MXCONFIG          >           To completely reconfigure MX, start with menu option;           1, then select each of the other options in order =           as you complete each section. Each section displaysr7           information about the items being configured, :           then asks you to answer some questions. Read the2           explanations carefully before answering.  @           When you are finished with your configuration changes,=           select option 5 from the main menu to exit from them@           configuration procedure. You will be asked whether you=           would like to save the configuration changes before            the procedure exits.                                                        
           2-2                      A           _______________________________________________________       3      Managing the Routero      9           This chapter describes the MCP commands used to +           configure and control the Router.c  L           __________________________________________________________________      3.1    Rewrite Rules   >           Address-rewriting rules, or rewrite rules for short,?           are checked by the Router for every recipient addressa@           on every envelope of every message that passes through8           MX. A rewrite rule consists of a pattern and a=           result. If an address matches the pattern, the rule.=           is applied and the address rewritten per the rule'st=           result. The purpose of this is to provide a general =           means of altering envelope addresses, primarily for >           handling multi-gateway cases where DEFINE PATH/ROUTE           is insufficient.  9           Be careful, since the rule processor treats the 9           addresses as ordinary text strings and does notf=           understand the syntax of RFC 821 addresses. Becausee@           they were designed mainly for handling domain aliases,:           rewrite patterns are matched from right to left.  9           The rewrite rule list is searched only once perh<           address, until a matching pattern is found. Once a;           match is found, no additional rules are searched. ;           If no rule matches an address, further processing ,           continues on the original address.  ;           An example of an application for rewrite rules is_;           the mapping of an artificial domain name, such as =           host.dnet, into an address for delivery through VMSc           MAIL over DECnet:M  L                            MCP> DEFINE REWRITE_RULE "<{user}@{host}.dnet>" -Z                            _MCP>                    "<""{host}::{user}""@local.host.name>"  A                                                               3-1p M                  Managing the Router           :           The pattern matching routine treats the variable6           references in the first string as wildcards;;           everything between the left angle bracket and thev9           at sign is copied into the {user} variable, ande>           everything between the at sign and the string .dnet>@           is copied into the {host} variable. The variable names>           have no special significance to the pattern matching           routine.  L           __________________________________________________________________  !    3.2    Defining Delivery Pathsb  :           The first step the Router takes in determining a?           delivery path is to identify the next hop the messageo<           should take. The next hop is determined by looking>           at the address and selecting either the first domain?           in the route path at the beginning of the address, orm<           if there is no route path, the destination domain.:           The second step is to search the list of defined>           domain/path mappings to determine the delivery path,6           and possibly a routing host for that domain.  9           The MCP DEFINE PATH command is used to create a =           domain/path mapping. A mapping consists of a domainw?           pattern (possibly containing VMS wildcard characters)F=           and the name of the delivery path to be used if theo=           next hop matches the domain pattern. Possible paths =           are DECNET_SMTP, JNET, LOCAL, SITE, SMTP, UUCP, andx           X25_SMTP.   ?           For example, a typical path list for an Internet host_-           might be created with the commands:   H                            MCP> DEFINE PATH myhost.mycompany.ORG   LOCALX                            MCP> DEFINE PATH myhost                 LOCAL  ! abbreviation[                            MCP> DEFINE PATH [1.2.3.4]              LOCAL  ! numeric addressSG                            MCP> DEFINE PATH *                      SMTP9  >           When setting up a path for X25_SMTP traffic, the DTE<           logicals defined in the PSI$DTE_TABLE logical name=           table should be specified as the /ROUTE values. For ?           example, assume two nodes wish to exchange mail usinga  
           3-2     _    A                                               Managing the Router_          :           X25_SMTP. Node A's domain name is node_a.foobar_=           org.whatever, and Node B's name is node_b.whocares_n=           org.whatever. The MCP command to define the path one           node A would be:  P                            MCP> DEFINE PATH "*.whocares_org.whatever" X25_SMTP ->                            _MCP> /ROUTE="WHOCARES_DTE_LOGICAL"  .           On Node B, the MCP command would be:  N                            MCP> DEFINE PATH "*.foobar_org.whatever" X25_SMTP -<                            _MCP> /ROUTE="FOOBAR_DTE_LOGICAL"  >           where the *_DTE_LOGICALs are the logicals defined in           PSI$DTE_TABLE.  >           The path list is searched sequentially until a match;           is made. The first three rules catch any locally-e8           addressed messages. The next two rules provide<           transparent routing of addresses in the BITNET and?           UUCP "fake domains" through their respective Internetr>           gateways. The last rule, which would match any other;           domain name, routes all other messages off-systema>           via SMTP. Notice that abbreviations or nicknames for?           the local host must have LOCAL path definitions to be            recognized by MX.   %           ___________________________       3.2.1  DOMAIN.NAMES Paths  @           If no paths from the configuration file match a domain;           name, the Router will automatically examine paths.;           built from a BITNET/EARN DOMAIN.NAMES file, whichd:           describes the appropriate BITNET/EARN routes for<           Internet domain-style addresses. See Section 4.3.5@           for further information about obtaining a DOMAIN.NAMES           file.     A                                                               3-3v l  r               Managing the Routere        L           __________________________________________________________________      3.3    Alias Translationp  =           The third phase of Router address processing is the :           identification and translation of local aliases.=           The system manager or postmaster can define aliasesT<           on the local system that translate to any local or;           remote address with the MCP DEFINE ALIAS command. <           If an address, after passing through the first two>           Router phases, is identified as a local address, the>           Router searches the alias list. If the local part of>           the original address matches one of the aliases, the=           original address is discarded and the alias addresss?           is substituted in its place and is passed through the *           other address processing phases.  >           Note that alias processing is totally transparent to>           the sender as well as the recipient of a message. No?           message headers are changed or added to indicate that >           the message is being forwarded via an alias address.=           In addition, aliases are kept in a simple list that @           is searched sequentially, rather than a more efficient=           structure. For these two reasons, it is recommendedl<           that aliases be used sparingly. Mail forwarding is<           better done with the VMS MAIL SET FORWARD command.  7           Also performed during this phase is "percent-s@           dehacking" of addresses. MX supports the "percent-sign;           hack" that allows users to route messages throughe?           the local system by specifying an address of the forms>           "user%host1@host2". If the local part of the address>           is found to contain a percent sign, the percent sign=           is converted to an at sign, the original address ise>           discarded, and the new address is substituted as for>           aliases. While this form of routed addressing is not>           recommended, it is sometimes required when the local?           host is acting as a gateway between two networks. Youa=           can disable the percent-dehacking function with thei0           MCP command SET ROUTER/NOPERCENT_HACK.  
           3-4  t  t    A                                               Managing the Router2        L           __________________________________________________________________  (    3.4    Controlling the Router Process  ?           The Router process will respond to shutdown and reset >           signals sent by the MCP SHUTDOWN and RESET commands,<           respectively. Using these commands is the only way;           that the Router can be shut down or reset withoutd#           possibly losing messages.s  ?           You can control Router functions, such as creation of =           an accounting log, with the MCP SET ROUTER command.F  L           __________________________________________________________________      3.5    Logging Router Eventse  >           Major events in the Router process, such as startup,?           shutdown, and configuration resets, are automatically <           logged to the Router's log file, MX_ROUTER_DIR:MX_:           ROUTER_nodename.LOG_process-id. These events may?           also be logged to an operator console by defining theg+           logical name MX_EVENT_OPER_CLASS:r  N                            $ DEFINE/SYSTEM/EXEC MX_EVENT_OPER_CLASS class-name  ?           where class-name can be any recognized OPCOM operatore!           class, such as NETWORK.   @           This logical name must be defined before MX is started=           in order to have any effect. Its definition affectsl#           all MX processing agents.                   A                                                               3-5i e  n                A           _______________________________________________________g  &    4      Managing the Delivery Agents      >           This chapter describes some of the MCP commands used:           to configure and control the various MX delivery           agents.r  L           __________________________________________________________________       4.1    Local Delivery Options  =           The local delivery agent can be configured to placep=           message header lines at either the beginning of the =           message text, the end of the message text, or both, 3           when delivering locally through VMS Mail.   9           In addition, you can control whether accountingn@           information is generated, the delivery retry interval,?           and the maximum retry count. By default, unsuccessfule>           deliveries into VMS Mail are retried every half hour?           up to 96 times total (giving a two-day period) beforee#           being returned to sender.   ?           The MCP SET LOCAL command can be used to alter any ofn>           these settings; refer to the command description for           further information.  L           __________________________________________________________________  :    4.2    SMTP, DECNET_SMTP, and X25_SMTP Delivery Options  9           As with the local delivery agent, you can alter 9           the accounting setting, the retry interval, and 8           the maximum retry count for SMTP, DECNET_SMTP,:           and X25_SMTP deliveries. However, the SMTP agent9           differentiates between failed deliveries due toi?           domain name lookup failures and other kinds of failede?           deliveries, and you can set a different maximum retryr>           count for DNS lookup failures. The MCP SET SMTP, SET<           DECNET_SMTP, and SET X25_SMTP commands are used to;           alter the settings for the three delivery agents.n  A                                                               4-1          &           Managing the Delivery Agents          <           The defaults are 30 minutes for retry interval, 12>           DNS failures maximum (for SMTP only), and 96 general           failures maximum.a  7           Refer to the command descriptions for furtherS           information.  %           ___________________________h  +    4.2.1  Internet "Mail Exchanger" Supporto  >           Some of the supported TCP/IP packages include domain?           name resolvers that provide access only to host name-c:           to-address mapping information. However, not all:           Internet domain names map directly to addresses.?           Domain names are also used to identify hosts on other @           networks to which electronic mail can be sent via some>           other Internet-connected gateway host, called a mail           exchanger.  =           Mail exchangers are recorded in the Internet Domain 9           Name System (DNS) using mail exchanger resource =           records (MXRRs). The initial list of DNS servers to <           be asked for MXRR information is controlled by the@           NETLIB software. Refer to the NETLIB documentation for           further information.  %           ___________________________       4.2.2  Default SMTP Routere  ;           When the local system uses host tables instead ofa:           Domain Name Service, you may want to establish a=           default router for SMTP messages. The SMTP deliveryt@           agent will automatically forward to the default router>           all messages addressed to users on hosts whose names>           are not found either in the Domain Name System or in?           the local host table provided by your TCP/IP package.   =           A default router is established in MCP with the SET_&           SMTP/DEFAULT_ROUTER command.  
           4-2     h    A                                      Managing the Delivery AgentsG          <           Before you use a default router, you should ensure           that:   <           o  The host name for the system you are using as a<              default router is known to your system's TCP/IP5              (i.e., is in your system's host tables).o  =           o  The default router you select "knows" more aboutM@              the Internet than your host, or in turn can forward@              to another host that has access to more domain name              information.   <           o  You have the consent of the people managing the?              system you intend to use as a default router. This >              is especially important if you expect the traffic=              between your system and the default router to be               heavy._  L           __________________________________________________________________      4.3    The Jnet Interface  9           The MX/Jnet interface module runs as a detached =           process. For incoming messages, it will convert CMSf=           NOTEs and PROFS notes into mostly-RFC 822-compliant =           messages. Also supported is BSMTP for both incomingg;           and outgoing mail to BITNET nodes with registeredh           mailers.  %           ___________________________   !    4.3.1  Jnet Address Conversion   7           The Jnet interface will automatically convertn>           addresses on outgoing mail such that local addresses>           use the RSCS node name and all non-BITNET, non-local@           addresses are "percent-hacked" to provide a route back?           through the local system for hosts that are connected            only to BITNET.X  ;           BITNET-style addresses are automatically percent-o8           hacked on incoming messages and de-hacked when=           outgoing, to guarantee a return path for mail beingt:           forwarded to other networks. If Jnet is the only  A                                                               4-3r .       &           Managing the Delivery Agents          ;           network transport you are using for mail, you canx?           disable this feature with the MCP SET JNET/NOPERCENT_d=           HACK command. This is done automatically for you ifa=           you use the MXCONFIG.COM procedure to configure MX.   :           You can also use the SET JNET command to control9           whether accounting information is generated and_?           whether BSMTP replies are generated. See the SET JNET 6           command description for further information.  %           ___________________________t      4.3.2  Gateway Policy  =           BITNET/EARN rules prohibit Internet/BITNET gateways1;           from gatewaying mail to or from BITNET hosts thate;           do not have a BSMTP-compliant mailer. MX enforceso=           these rules unless you use the MCP SET JNET/LENIENTy           command.  %           ___________________________n      4.3.3  Jnet Node Name  @           MX will use the Jnet cluster node name on all outgoing?           mail, if you have enabled Jnet clustering. Otherwise, @           MX will use the local Jnet node name. You can override>           this selection by defining the logical name MX_JNET_           NODE:t  @                            $ DEFINE/SYSTEM MX_JNET_NODE nodename  <           No validity checking is performed on the specified           node name.  %           ___________________________       4.3.4  Mailer Username8  =           BITNET mail protocols require the use of a reserveda<           "mailer" username, through which most incoming and?           outgoing mail messages will be sent. This username ise?           registered in the BITNET/EARN node tables and is usedf<           by other mailers on the network to determine which=           mail protocols can be used to communicate with yourp  
           4-4     t    A                                      Managing the Delivery Agentsn          @           system. The recommended mailer username is MAILER. You8           should not use SYSTEM as your mailer username.  =           You can implement a mailer username either with the ;           /USERNAME qualifier on the SET JNET command or by >           running the MX/Jnet interface under a mailer account?           you create specifically for use with MX, as described 1           in Message Exchange Installation Guide.   %           ___________________________   >    4.3.5  XMAILER.NAMES, DOMAIN.NAMES, and BITEARN.NODES Files  ?           In order to communicate with other mailers on BITNET,n>           you must register your node's mailer username in the>           BITNET/EARN node table. Information on how to update@           your BITNET node entry can be obtained from your local           LISTSERV@BITNIC:  E                            $ SEND LISTSERV@BITNIC GET UPDATE PROCEDUR   =           The person performing the update must be the BITNET_<           contact person for the node being updated, or some"           other authorized entity.  ?           The following example shows a typical command used tot/           update your BITNET node entry for MX:T  +                            MODIFY NODE node K                            :servers1.mailer@node(MAIL,ND PU,M,BSMTP,P_user)p  @           This command can be sent to UPDATE@BITNIC to establish;           your mailer account (substituting the appropriate ?           username and node, of course). Jnet can received mailt>           files in either NETDATA or PUNCH format; the "ND PU"?           in the command above will inform other BITNET mailerss?           that your node can accept both (and prefers NETDATA).i>           NETDATA is the preferred format, because there is no=           line length limitation as there is for PUNCH files.   :           In order for MX to determine the capabilities of>           mailers on other systems on BITNET, you must provide8           either BITEARN.NODES file or XMAILER.NAMES. If<           you're not directly connected to the Internet, you  A                                                               4-5M    I    &           Managing the Delivery Agents          ?           should also provide DOMAIN.NAMES. All three files arev           described below.  @           If BITEARN.NODES is available, then MX can send either>           files via Jnet as either NETDATA or PUNCH, depending=           on the preference established for the target nodes. @           If XMAILER.NAMES is used instead, only PUNCH files can@           be sent, because preferred mail format information for1           nodes is not supplied in XMAILER.NAMES.h&                  _____________________<                  4.3.5.1  BITEARN.NODES and MXBITNET.MAILERS                           Files =           The file BITEARN.NODES contains descriptions of all ?           the systems on the BITNET/EARN networks. Every BITNET <           node is fully described in BITEARN.NODES; the file>           XMAILER.NAMES is created from this file. In order to<           provide support for sending NETDATA files, MX uses=           BITEARN.NODES to create its own mailer file, called            MXBITNET.MAILERS.              BITEARN.NODES   ?           Because all BITNET nodes are listed in BITEARN.NODES, ?           the file can be pretty big (several thousand blocks). =           You can arrange to have monthly updates sent to youT?           from a NETSERV site near you. By applying the monthlyl9           updates, your mailer information stays current.y  @           You can obtain a copy of BITEARN.NODES from your local*           NETSERV, or from NETSERV@BITNIC:  B                            $ SEND NETSERV@BITNIC GET BITEARN NODES  ;           The file may also be available from a neighboringm<           site; because of the file's size, you might try to=           acquire a copy from a neighbor before requesting itr           from NETSERV.   =           If you have a NETSERV access password, you can have >           the monthly updates distributed to you automatically@           with the NETSERV AFD command. Send the command HELP to>           your local NETSERV for further information. Software=           for applying the updates can be obtained by sendingN  
           4-6e h  d    A                                      Managing the Delivery Agents           >           the following commands in the body of a mail message           to FILESERV@WKU.EDU:  (                            SEND UPDNODES.                            SEND FILESERV_TOOLS             MXBITNET.MAILERS  8           If the file BITEARN.NODES is found in MX_JNET_<           DIR:, the MX Jnet interface will scan the file for9           mailer information for all the nodes, producingd;           the MX-private file MX_JNET_DIR:MXBITNET.MAILERS.a<           This file contains the mailer names for all BITNET>           sites, as well as the sites' preferred mail formats.=           This file is then read during the MX Jnet interfaceE@           initialization; when mail is sent to a BITNET site, MX?           consults the data from this file to determine whethera<           the message should be sent as a PUNCH file or as a>           NETDATA file. Lines are wrapped at 80 characters for1           PUNCH files, but not for NETDATA files.c  >           You can avoid the need for maintaining BITEARN.NODES8           if you get it from the VMS Store, a repository4           of VMS utilities maintained by Eric Thomas>           (ERIC@SEARN.BITNET). You can get the current version>           of MXBITNET.MAILERS by sending the following command#           to LISTSERV@SEARN.BITNET.   M                            $ SEND LISTSERV@SEARN GET <BITNET>MXBITNET.MAILERSi  :           You can also have MXBITNET.MAILERS automatically;           distributed to you each month using the following.           command.  Q                            $ SEND LISTSERV@SEARN AFD ADD <BITNET>MXBITNET.MAILERS           A                                                               4-7o r  m    &           Managing the Delivery Agents        &                  _____________________,                  4.3.5.2  XMAILER.NAMES File6           If you elect not to use BITEARN.NODES and/or5           MXBITNET.MAILERS, then you should obtain ant<           XMAILER.NAMES file for your RSCS network and place?           it in the directory MX_ROOT:[JNET]. For BITNET hosts,t@           you should be able to obtain this file from your local*           NETSERV, or from NETSERV@BITNIC:  B                            $ SEND NETSERV@BITNIC GET XMAILER NAMES  =           If you cannot contact a NETSERV server, the contact <           person for a host that is upstream from you should#           have a copy of this file.   7           If you do not have a copy of this file in MX_E=           ROOT:[JNET], MX will not be able to contact mailers =           at other sites on the networks, nor will it be able_;           to use the BSMTP protocol, which is required when_3           communicating with the INTERBIT gateways. &                  _____________________+                  4.3.5.3  DOMAIN.NAMES Fileb>           If you do not have a direct Internet connection, you=           should also obtain a copy of DOMAIN.NAMES and place =           it in MX_ROOT:[JNET]. The Router will use this filee?           to route non-BITNET messages to appropriate gateways.r6           DOMAIN.NAMES is also available from NETSERV:  A                            $ SEND NETSERV@BITNIC GET DOMAIN NAMES_  =           If you cannot contact a NETSERV server, the contact <           person for a host that is upstream from you should#           have a copy of this file.t  @           These files are updated monthly. If you have a NETSERV;           access password, you can have the monthly updatess?           distributed to you automatically with the NETSERV AFDo>           command. Send the command HELP to your local NETSERV"           for further information.    
           4-8  E  T    A                                      Managing the Delivery Agentsz          =           If you cannot obtain an XMAILER.NAMES file for yourl<           RSCS network, you can create one for your own use.=           You need one line in the file for each node in yourl=           network. Each line in the file must be of the form:   O                            :nick.HOSTNAME :alias.ALIAS :net. :mailer. :netsoft._  >           where "HOSTNAME" is the name of the host, "ALIAS" is@           either the host name repeated or an alias for the host>           name, ":net." is followed by the name of the network9           the node resides on (optional for use with MX), >           ":mailer." is followed either by a blank (indicating9           no mailer) or by a mailer username designation, =           and ":netsoft." is followed by the name of the RSCSs<           software in use on the node (optional for MX use).  =           You should only specify a mailer username for othern?           nodes running MX or running some other mailer packagey?           that can handle BSMTP. Be sure that the other mailersr@           on your network are also aware of your system's mailer;           username in order to take full advantage of BSMTP :           message transfers. Until your mailer username is>           registered, you should omit any reference to mailers%           in your XMAILER.NAMES file.E  L           __________________________________________________________________      4.4    UUCP Delivery Options   ;           The MX_RMAIL program (part of the UUCP interface)_<           can be configured to use DECUS UUCP's MAIL_REWRITE<           rules to translate addresses on messages coming in?           from UUCP. To use this feature, execute the followingg8           logical name definition to your system startup'           procedure before starting MX:   ?                            $ DEFINE/SYSTEM MX_UUCP_REWRITE TRUEf  9           The MX_RMAIL program will automatically use then@           rewrite rules in the file UUCP_CFG:MAIL_REWRITE.RULES.<           If you would rather define your own INBOUND_TO and?           INBOUND_FROM rules for use by MX_RMAIL, place them inN?           the file MX_UUCP_DIR:UUCP_MAIL_REWRITE.RULES. If thath  A                                                               4-9          &           Managing the Delivery Agents          >           file is present, MX_RMAIL will use it instead of the           file in UUCP_CFG.n  L           __________________________________________________________________      4.5    SITE Delivery Options   <           The SITE delivery agent includes support for retry;           on error. The MCP SET SITE command can be used to1;           alter the retry interval and maximum retry count. ?           Refer to the SET SITE command description for furthers           information.  L           __________________________________________________________________       4.6    The LISTSERV Interface  =           The MX/LISTSERV interface module runs as a detachedn=           process. If L-Soft International's LISTSERV producti=           is installed on the system, MX Router automaticallyw<           detects messages destined for LISTSERV and mailing?           lists and passes them on to the LISTSERV software forS           processing.e  6           There are no MCP commands to control MX LSV.  L           __________________________________________________________________      4.7    Shutdowns and Resets  >           Each of the delivery agents will respond to shutdown;           and reset signals as sent by the MCP SHUTDOWN ande<           RESET commands, respectively. Using these commands=           is the only guaranteed way of cleanly shutting downn<           and resetting the delivery agents, without loss of           messages in progress.n  <           There may be times when it is necessary to prevent>           local users from using VMS Mail to send mail via MX.<           To do so, define the executive-mode system logical           name MX_SHUTDOWN:   @                            $ DEFINE/SYSTEM/EXEC MX_SHUTDOWN TRUE             4-10 _       A                                      Managing the Delivery Agents           <           If a user tries to send mail to an MX% address and<           MX_SHUTDOWN is defined, VMS Mail (MX_MAILSHR) will;           display an error message stating that MX has beene5           temporarily disabled by the system manager.o  L           __________________________________________________________________  '    4.8    Logging Delivery Agent Eventse  ?           Major events in the delivery agents, such as startup, ?           shutdown, and configuration resets, are automaticallye;           logged to each agent's log file. These events may ?           also be logged to an operator console by defining the +           logical name MX_EVENT_OPER_CLASS:.  N                            $ DEFINE/SYSTEM/EXEC MX_EVENT_OPER_CLASS class-name  ?           where class-name can be any recognized OPCOM operatorh!           class, such as NETWORK._  @           This logical name must be defined before MX is started=           in order to have any effect. Its definition affectss#           all MX processing agents.i                                  A                                                              4-11                      A           _______________________________________________________i  '    5      Managing Message Entry Agents       ?           This chapter describes the options available with theA"           MX message entry agents.  L           __________________________________________________________________      5.1    Local Message Entry   ?           The VMS MAIL interface (MX_MAILSHR) is used for local @           message entry. It is controlled through the definition'           of system-wide logical names.r  9           Use of MX through VMS Mail can be restricted bys?           defining the executive-mode logical MX_RESTRICT_USAGEn+           in the system logical name table:   F                            $ DEFINE/SYSTEM/EXEC MX_RESTRICT_USAGE TRUE  ?           If the logical is defined, the user must hold the MX_ @           MAIL_ACCESS process rights identifier in order to send=           mail using MX. The VMS utility AUTHORIZE is used tor'           create and grant identifiers:   4                            $ set default sys$system:*                            $ run authorize=                            UAF> ADD/IDENTIFIER MX_MAIL_ACCESSe`                            Identifier MX_MAIL_ACCESS value: %X8001000D added to rights data baseJ                            UAF> GRANT/IDENTIFIER MX_MAIL_ACCESS GOATHUNTERJ                            Identifier MX_MAIL_ACCESS granted to GOATHUNTER                            UAF>_  =           Users not holding the identifier and trying to send @           mail through MX will see an error message stating that8           they are not authorized to send mail using MX.  A                                                               5-1  e  n    '           Managing Message Entry Agents         %           ____________________________  7    5.1.1  System-wide MX Aliases for Outgoing Addresses   ?           MX supports the use of personal and system-wide aliash<           databases for defining aliases for frequently-used;           addresses for outgoing mail. The MXALIAS utility,s<           described in the Message Exchange User's Guide, is-           used to maintain the database file.M  =           To create a system-wide alias database, you can user@           the USE command in MXALIAS to open a centrally-located?           database file that can then be populated with the ADDN@           command. To make the file accessible to users, set the>           protection to allow WORLD:READ access and define the@           MX_GLOBAL_ALIAS_DATABASE logical to point to the file:  J                            $ set file/prot=w:re mx_dir:mx_global_alias.datc                            $ define/system/exec mx_global_alias_database mx_dir:mx_global_alias.dat   >           You will also need to add the DEFINE command to your           system startup.   %           ___________________________   "    5.1.2  VMS MAIL Protocol Prefix  <           MX by default uses the foreign protocol prefix MX%8           when interfacing with VMS Mail. You can define:           alternate foreign protocol prefixes for use with>           MX, to provide a migration path for users from other:           mail systems to MX. MX will correctly handle the>           following prefixes: SMTP%, WINS%, IN%, JNET%, IHMF%,?           VN%, ST%, INET%, and UUCP%.[1] To set up one of theseI<           alternate prefixes in VMS Mail, define the logical$           name MAIL$PROTOCOL_prefix:             ________________>         [1] You should not re-direct the UUCP% prefix to MX if=             you are using MX with UUCP. Doing so will prevente@             messages from being delivered to UUCP from MX, sinceA             MX uses the UUCP_MAILSHR interface (the same as UUCP%E               does).  
           5-2     a    A                                     Managing Message Entry Agentsa          O                            $ DEFINE/SYSTEM/EXEC MAIL$PROTOCOL_prefix MX_MAILSHR   >           where prefix is one of the above-mentioned prefixes,,           without the trailing percent sign.  >           Note that incoming mail from MX will always bear the;           MX% prefix. If you wish to use another prefix fort<           incoming mail, you can define the logical name MX_           PROTOCOL_PREFIX:  J                            $ DEFINE/SYSTEM/EXEC MX_PROTOCOL_PREFIX prefix%  >           where prefix is one of the above-mentioned prefixes,@           with the trailing percent sign. The default prefix MX%$           is the recommended prefix.  %           ___________________________p      5.1.3  Default Host Names  ;           By default, MX uses the logical name MX_NODE_NAMEl;           as the host name to be appended when converting ae>           username into a full network mail address. For sites:           that require more control over how addresses are=           formatted, additional logical names may be defined.u  ;           These logical names are not automatically defined =           by MX; you must define them yourself (e.g., in your ;           system startup procedure). The must be defined ini=           executive mode, but may reside in the process, job,D@           group, or system logical name table. The logical names2           and their descriptions are in Table 5-1.  A           Table_5-1__Address_Formatting_Logical_Names____________L  A           Logical_name___Description_____________________________c  =           MX_ENVELOPE_   Host name to be used when formattingt>           FROM_HOST      envelope return addresses (equivalent2                          to the RFC821 MAIL FROM).  =           MX_FROM_HOST   Host name to be used when formattingi*                          the From: header.  A                                                               5-3          '           Managing Message Entry Agentsh          A           Table_5-1_(Cont.)__Address_Formatting_Logical_Names____   A           Logical_name___Description_____________________________E  >           MX_TO_HOST     Host name to be used when on a To: orA           _______________Cc:_address.____________________________I  >           You can also affect address formatting by installing<           a SITE address conversion callout. See the Message=           Exchange Programmer's Guide for more information onT&           address conversion callouts.  %           ___________________________r  7    5.1.4  Disabling Automatic Quoted-Printable Encodingf  ;           MX_MAILSHR automatically detects the inclusion ofE<           8-bit characters in outgoing messages, causing the:           messages to be re-encoded using the MIME quoted-?           printable content transfer encoding. In some locales,e?           this automatic encoding may not interoperate properlyr8           with other systems, and this feature should be<           disabled. To do this, define the following logical           name:e  K                            $ DEFINE/SYSTEM/EXEC MX_MAILSHR_IGNORE_8BIT TRUEd  =           The value of the equivalence string is unimportant;f=           the existence of this logical name will cause 8-bitb#           characters to be ignored.   8           If Kanji support is enabled, automatic quoted-.           printable encoding is also disabled.  L           __________________________________________________________________      5.2    SMTP_SERVER   @           The SMTP server is a detached, multi-threaded process.<           You can specify how many threads the server should;           handle simultaneously by defining a logical name:   H                            $ DEFINE/SYSTEM/EXEC MX_SMTP_SERVER_THREADS n  
           5-4     p    A                                     Managing Message Entry Agentss          ?           The value of n should range from 1 to 16. The defaulte:           is 4. The SMTP server may require larger process>           quotas/limits if more than four threads are allowed.  L           __________________________________________________________________  $    5.3    DECNET_SMTP Network Object  <           You must create a DECnet object called DECSMTP for@           establishing SMTP-over-DECnet connections. To do this,>           either use your mailer account or create a dedicated:           server account for use with the DECnet object (a=           dedicated server account is recommended). Using theE@           AUTHORIZE utility, set a password for the this account>           and set the account /NOPWDLIFETIME. Also be sure the-           account has network access enabled.   [                            UAF> MODIFY account/PASSWORD=some-password/NOPWDLIFETIME/networko  ;           A DECnet object needs to be created to handle thei>           incoming SMTP-over-DECnet connections and to map the?           DECSMTP object name to a DECnet object number. ChooseN<           an unused DECnet object number. To see what object8           numbers are currently in use, use the command:  6                            $ MCR NCP SHOW KNOWN OBJECT  <           Assign the object name DECSMTP to an unused object:           number; the number used must be identical on all?           nodes on your network that use SMTP-over-DECnet (this 8           example uses 254). In NCP, use these commands:  8                            NCP> PURGE OBJECT DECSMTP ALLR                            NCP> DEFINE OBJECT DECSMTP NUMBER 254 PROXY NONE FILE -d                            _NCP>    MX_EXE:DNSMTP_SERVER.EXE USER server-acct PASSWORD some-password6                            NCP> SET OBJECT DECSMTP ALL  @           You do not need to specify the FILE, USER, or PASSWORD<           parameters if you do not intend to accept incoming?           SMTP connections over DECnet. Be sure to use both then>           DEFINE and SET commands of NCP, and be sure that the>           password in the DECnet database matches the password6           you set for the server account in AUTHORIZE.  A                                                               5-5          '           Managing Message Entry Agents                      Using Proxiest  >           Instead of storing the username and password for the:           server account in the DECnet database, you could=           grant access using DECnet proxies. Proxies give youp<           more control over who on the network has access to<           the object, and eliminate the need for storing the=           password to the server account in the DECnet objectS           database.c  ?           To enable proxy access to the DECSMTP object, use the $           following commands in NCP:  8                            NCP> PURGE OBJECT DECSMTP ALLV                            NCP> DEFINE OBJECT DECSMTP NUMBER 254 PROXY INCOMING FILE -<                            _NCP>    MX_EXE:DNSMTP_SERVER.EXE6                            NCP> SET OBJECT DECSMTP ALL  @           Then in AUTHORIZE, create proxy entries for the mailer@           accounts on the other systems on the network that will3           be sending you mail via SMTP-over-DECnet:i  L                            UAF> ADD/PROXY remote::mailer server-acct/DEFAULT  >           For remote::mailer substitute the DECnet node of the>           remote system and the username of the mailer account=           on that system. For server-acct substitute the namer;           of the server account you set up for use with the            DECnet-SMTP object.h  L           __________________________________________________________________  !    5.4    X25_SMTP Network Object   =           You must create a DECnet object called X25_SMTP for @           establishing SMTP-over-X.25 connections, both incoming           and outgoing.   9           If you intend to accept incoming SMTP-over-X.25 >           connections, you should establish an account (either@           your mailer account or a dedicated server account) for;           use with each DECnet object. See Message Exchange 8           Installation Guide for more information on the5           requirements for the DECnet object account.e  
           5-6a o  o    A                                     Managing Message Entry Agentso          ;           A DECnet object needs to be created to handle the <           incoming SMTP-over-X.25 connections and to map the@           X25_SMTP object name to a DECnet object number. Choose<           an unused DECnet object number. To see what object8           numbers are currently in use, use the command:  6                            $ MCR NCP SHOW KNOWN OBJECT  =           Assign the object name X25_SMTP to an unused objecte:           number; the number used must be identical on all?           nodes on your network that use SMTP-over-DECnet (thisf8           example uses 253). In NCP, use these commands:  9                            NCP> PURGE OBJECT X25_SMTP ALLMS                            NCP> DEFINE OBJECT X25_SMTP NUMBER 253 PROXY NONE FILE - c                            _NCP>    MX_EXE:XSMTP_SERVER.EXE USER server-acct PASSWORD some-passwordy7                            NCP> SET OBJECT X25_SMTP ALLu  @           You do not need to specify the FILE, USER, or PASSWORD<           parameters if you do not intend to accept incoming?           SMTP connections over X.25. Be sure that the passwordi=           in the DECnet database matches the password you set_.           for the server account in AUTHORIZE.  ?           You must also add an X.25 "destination" to the P.S.I._2           database that maps to the DECnet object:  O                            NCP> DEFINE MODULE X25-SERVER DESTINATION X25_SMTP - ?                            _NCP>   OBJECT X25_SMTP PRIORITY 0 -lH                            _NCP>   CALL MASK  FFFFFFFFFFFFFFFFFFFFFFFF -F                            _NCP>   CALL VALUE FF0000005832355F534D5450  N                            NCP> SET MODULE X25-SERVER DESTINATION X25_SMTP ALL  8           Section 3.2, Defining Delivery Paths, contains>           information about defining X25_SMTP paths using MCP.        A                                                               5-7R e  u    '           Managing Message Entry Agentsi        L           __________________________________________________________________  '    5.5    Message Entry Agent Shutdowns   :           The two message entry mechanisms that do not get9           shut down with the rest of MCP are the VMS Mail_:           interface and the DECNET_SMTP server (if you are=           using SMTP-over-DECnet). The VMS Mail interface cane?           be deactivated by de-installing the MX_MAILSHR image:n  6                            $ INSTALL REMOVE MX_MAILSHR  4           The SMTP-over-DECnet server gets shut down<           automatically when you shut down DECnet, or can be<           manually removed by eliminating the DECSMTP object#           from the DECnet database:o  =                            $ MCR NCP CLEAR OBJECT DECSMTP ALLd  @           The SMTP-over-X.25 server gets shut down automatically?           when you shut down P.S.I., or can be manually removedU<           by eliminating the X25_SMTP object from the DECnet           database:g  >                            $ MCR NCP CLEAR OBJECT X25_SMTP ALL                                
           5-8U W  s                A           _______________________________________________________a  $    6      Managing the Message Queue      ?           This chapter describes the various commands needed to_1           control how the message queue operates.   L           __________________________________________________________________  %    6.1    Establishing the Queue Sizen  9           The maximum number of queue entries that can bet<           present in the MX message queue at any one time is>           determined by the size, in blocks, of the MX message:           queue file. Each entry in the queue requires one:           block, with 10 additional blocks used to store a<           bitmap of entries in use. This means, for example,;           that a queue file that is 510 blocks in size willm;           allow 500 entries to be present in the queue. The :           upper ceiling on the maximum entries is 131,072.  @           Most sites that process several thousand mail messages;           a day can probably work well with a queue file of :           about 5,000 blocks. If you are not short on disk=           space, creating a 131,072-block file will eliminatet6           the need to ever modify the queue file size.  L           __________________________________________________________________  $    6.2    Running the MX FLQ Manager  =           As entries in the message queue are processed, they >           are marked as being finished. By default, one of the=           MX Router processes will be responsible for purging            out finished entries.   :           You have the option of running a separate MX FLQ9           Manager process, whose sole job is to purge theG;           queue of finished entries and cancel or ready any ;           in-progress entries leftover from system crashes, =           disconnected processes, etc. Running a separate FLQX@           manager frees the MX Router to route messages, instead  A                                                               6-1          $           Managing the Message Queue          ?           of splitting its time between routing and maintainingr;           the queue. This means that the MX Router has moreM?           time for routing messages and queue maintenance isn'tE1           delayed while the MX Router is routing.   9           While the MX FLQ Manager can be run on multipleO?           nodes in a cluster, only one manager is ever activelya@           maintaining the queue. Running the manager on multiple=           nodes can provide failover backup in case of a node ;           crash, etc. If the MX FLQ Manager is shutdown and <           there are no managers running on another node, one=           of the MX Router processes will automatically start             maintaining the queue.  >           Sites that do not process many messages per day will>           probably not benefit from running the MX FLQ Manager           process.  L           __________________________________________________________________       6.3    Queue Cleanup Logicals  <           The Router process (or the MX FLQ Manager process)=           automatically handles cleanup of the message queue.t@           The time between cleanup events can be controlled with3           logical names, as described in Table 6-1.m  A           Table_6-1__FLQ_Manager/Router_queue-related_logicals___h  #                             Default A           Logical___________value___Description__________________   >           MX_FLQ_MGR_       2 min.  Amount of time FLQ Manager>           WAKEUP_INTERVAL           sleeps before checking for4                                     entries to purge  <           MX_ROUTER_        10      Amount of time MX Router>           WAKEUP_INTERVAL   min.    sleeps before checking for4                                     entries to purge  
           6-2  t  s    A                                        Managing the Message QueueL          =           Table 6-1 (Cont.)  FLQ Manager/Router queue-relatedfA           ___________________logicals____________________________   #                             DefaultiA           Logical___________value___Description__________________r  A           MX_FLQ_CHECK_     10      Amount of time between checkst;           WAIT              min.    for other queue-relatedH*                                     events  @           MX_FLQ_PURGE_     15      Amount of time a queue entry@           WAIT              min.    should remain in queue afterA           __________________________it_has_been_processed________C  >           To alter one of these values, use the DEFINE command@           to set the logical to a new time (using VMS delta-time>           format) and send a reset signal to the Router and/or            FLQ Manager processes:  I                            $ DEFINE/SYSTEM MX_FLQ_PURGE_WAIT "0 00:10:00"a1                            $ MCP RESET ROUTER,FLQ   8           (If the Router runs on a different node in the;           cluster, you will have to define the logical namen           there.)   =           If you want this change to be permanent and surviveo;           a system reboot, you should add this logical name ?           definition to your system startup procedure before MXy           is started.a  L           __________________________________________________________________  5    6.4    Automatic Purging of Finished Queue Entriesr  =           Finished queue entries are left in the queue for 15t<           minutes, by default, before they are purged. It is>           not necessary to leave the entries in the queue once@           they have been marked "FINished." If you prefer to not=           leave them around, you can enable automatic purginga9           of FIN entries and their related files. Use then@           MXCONFIG.COM command procedure, option 1, to configure*           the message queue logical names.  A                                                               6-3a a       $           Managing the Message Queue          7           Even when autopurging is enabled, it is stillt?           necessary for the MX FLQ Manager or MX Router processv>           to occasionally scan the queue for CANCELed entries.?           However, a dedicated MX FLQ Manager process is not asi>           beneficial as it is when autopurging is not enabled.  L           __________________________________________________________________       6.5    The MCP QUEUE Commands  ?           MCP includes a suite of commands for queue management <           to be used by privileged users. These commands are3           documented in the MCP command dictionary.   %           ___________________________h  ,    6.5.1  Interpreting MCP QUEUE SHOW Output  >           When there are messages in the queue, MCP QUEUE SHOW>           displays the following information about each entry:  P                            Entry Status  Size  Source  Agent  Entry Status  SizeQ                            ----- ------ ------ ------ ------- ----- ------ ------XR                             2980 INPROG    229 LOCAL  <usr01@myhost.mycompany.com>Q                                                       SMTP     2981 READY     229ie                                                               (waiting until 15-NOV-1991 15:07:21.75)rM                             9872 INPROG     34 JNET   <JUSER@SOMENODE.BITNET> Q                                                       LOCAL    9874 INPROG     34iY                            10859 READY   65120 LOCAL  <FileServ-Mgr@myhost.mycompany.com> H                                  (Waiting until 15-NOV-1991 18:00:00.00)  9           The fields of the display contain the followingt           information:  @           o  The first Entry field is the queue entry number forA              the base message, which can range from 1 to 131,071.l  ;           o  The first Status field describes the status ofc>              the base message and can be one of INPROG, READY,              FINISH, or CANCLD.U  ?             o  INPROG stands for "in progress" and is used whenf?                the base entry is being processed by the Router, @                or when one of its related entries is ready or in                progress.  
           6-4r a       A                                        Managing the Message Queue_          =             o  READY is used when the base entry is ready for (                processing by the Router.  ;             o  FINISH indicates that processing of the baser;                entry has completed. Finished entries remaini9                in the queue for a short time before beingE=                removed (see Table 6-1). They are not normally =                displayed; the /ALL qualifier on the MCP QUEUE ?                SHOW command can be used to force the display ofe                these entries.P  ?             o  CANCLD indicates that processing of the entry is @                terminated before completion, such as when CTRL/C@                is pressed during entry of a message in VMS MAIL.?                Cancelled entries also remain in the queue for aa@                short time before removal, and are only displayed/                when MCP QUEUE SHOW/ALL is used.r  A           o  The Size field displays the size of the message. The ?              size is calculated as the total number of bytes inm@              the body of the message multiplied by the number of@              intended recipients of the message. Headers are not<              counted when computing the size of the message.  >           o  The Source field describes the origin of the base>              message. It can have the value LOCAL, JNET, SMTP,@              DNSMTP (for SMTP-over-DECnet), UUCP, SITE, or MAIL.A              To the right of the source display is the address ofD1              the user who originated the message.E  :           If a message is being processed by one of the MX7           delivery agents, the base queue entry will be =           immediately followed by indented entries that beginc>           with the Agent field. The Agent field identifies the?           delivery agent that is working on the entry. Possibleh?           values are LOCAL, LSV, SMTP, JNET, UUCP, SITE, HOLDn,C,           and DNSMTP (for SMTP-over-DECnet).  ;           The second Entry, Status, and Size fields provide @           information about the queue entry used by the delivery=           agent. This agent-specific entry refers back to ther:           base entry for the message headers and text, and  A                                                               6-5F ,  E    $           Managing the Message Queue          ;           the base entry has pointers to the agent-specificn=           entries related to it. When an agent-specific entry ?           is finished, the reference to it in the base entry ist?           removed; when no agent-specific entries are left, theu(           base entry is marked FINISHED.  %           ___________________________-  2    6.5.2  Interpreting MCP QUEUE STATISTICS Output  7           The MCP command QUEUE STATISTICS displays the %           following entry statistics:r  0                            MCP> QUEUE STATISTICSU                            Total entries: 16/502  (3%)   Highest entry used: 24  (4%)                             MCP>o  @           The first number after "Total entries:" is the current>           number of entries in the queue. The second number is<           the maximum number of entries allowed by the queue;           file size. The percentage of entries used is alsoo           shown.  ?           The "Highest entry used:" is the largest entry number :           ever used during the life of the queue file. The=           percentage of the queue in use at that time is alsoS<           shown. This value can be used to determine whether=           or not the selected queue file size is sufficientlyo<           large. The MCP command QUEUE EXTEND can be used to.           increase the size of the queue file.                    
           6-6                      A           _______________________________________________________:  ;    7      Configuring MX for Part-Time Internet Connectionse      ;           This chapter describes how to configure MX to use =           holding queues for messages that get delivered overc=           a TCP/IP network path that is not available all thet           time._  L           __________________________________________________________________  /    7.1    Environment for Part-Time Connections   <           MX supports a messaging environment consisting of:  9           o  A server system, located at a main office org<              Internet Service Provider, that has a permanent#              TCP/IP connection; and   :           o  one or more client systems, located at remote>              offices, which periodically connect to the server0              system to pick up and deliver mail.  >           MX can act as either a client or server system; when?           configured as as a server, MX can service up to eight :           clients with part-time network links. The client;           systems must have static IP addresses assigned toh;           their domain names, or there must be an automatic <           assignment in the DNS between each client's domain*           name and its dynamic IP address.  L           __________________________________________________________________  .    7.2    Configuring MX as a Part-Time Client  ;           To configure MX as a part-time client, use MCP to 4           configure the delivery path to the server:  O                            MCP> DEFINE PATH * HOLDING_QUEUE=1/ROUTE=server-namee  >           If you have already used MXCONFIG.COM to create your<           MX configuration database, you may need to use the<           MODIFY PATH command to configure this path change.  A                                                               7-1X P  R    ;           Configuring MX for Part-Time Internet Connections           @           This path configuration causes MX to hold all messages>           that are not delivered through other, more specific,           paths.  ;           If your client system creates the network path tot>           the server, you should execute the following command;           to start the holding queue agent when the path is.           established:  :                            $ @SYS$STARTUP:MX_STARTUP HOLD1  =           The agent will then attempt to deliver all messagesN:           in the holding queue to the server. You may also;           use this command if the server system creates the >           dial-up connection, but this may not be necessary if<           the server system supports the SMTP ETRN extension?           (documented in Internet RFC 1985). The MX SMTP server5?           supports ETRN and can automatically start the holdingn<           queue agent when requested to do so by the server.  L           __________________________________________________________________  :    7.3    Configuring MX as a Server for Part-Time Clients  @           The configuration for MX as a server also uses holding?           queues, but defines paths for the specific host(s) orn'           domain(s) at the client site:   R           MCP> DEFINE PATH client.host.name HOLDING_QUEUE=n/ROUTE=client.host.nameO           MCP> DEFINE PATH client.domain HOLDING_QUEUE=n/ROUTE=client.host.namen  =           The value of n can be 1 through 8, representing onea<           of the eight available holding queues. If the name?           defined in the DEFINE PATH command does not match theP>           client's actual Internet host name, you must specify<           the /ROUTE qualifier to set the host name to which=           messages will be delivered. In addition, all /ROUTEa>           values for a single holding queue must be identical.  <           To start the delivery agent for one of the holding"           queues, use the command:  
           7-2     m    A                 Configuring MX for Part-Time Internet Connections           :                            $ @SYS$STARTUP:MX_STARTUP HOLDn  =           where n is the number 1 through 8, representing the =           number of the holding queue for a particular client_?           system. If a client system is also running MX, and isa>           configured to start its holding queue agent when the>           network path is established, the ETRN support in the@           MX SMTP server will be used to automatically start the/           holding queue agent for their system.Q  L           __________________________________________________________________      7.4    ETRN Support  <           When both the client and the server systems run MX;           or another mailer that supports the RFC 1985 ETRNy?           extension to SMTP, only one of the two systems has tol@           be set up to start its delivery agent when the dial-up@           connection is active; the SMTP ETRN command will cause>           the other system to start delivering messages in the           opposite direction.l  7           A parameter is sent on the ETRN command; thist=           parameter can identify the host or domain for which >           messages should be delivered, or it can be a special?           "queue name," a private identifier used by the clientn@           and server systems to identify the holding queue agent>           that should be started. By default, MX holding queue7           agents will send the following ETRN commands:   ,                            ETRN mx-host-name-                            ETRN #ip-host-name   =           Where mx-host-name is the value of the logical name >           MX_NODE_NAME, and ip-host-name is the local system's<           TCP/IP host name (either from the logical name MX_=           INET_HOST, or from your TCP/IP package's configureds>           host name). In the second case, the pound sign ("#")<           indicates that ip-host-name is a queue identifier.  A                                                               7-3g s  r    ;           Configuring MX for Part-Time Internet Connections,          =           If the system at the other end of the connection is :           running MX, and has PATH definitions with /ROUTE;           qualifiers that specify the same host name as then>           ip-host-name appearing in the ETRN command, then the@           remote system will automatically start the appropriate:           holding queue agent for that system. The holding>           queue agent will also be started if the mx-host-name<           appearing in the first ETRN command matches one of           PATH definitions.u  :           You can override the default ETRN behavior for a;           particular holding queue agent with the following            logical names:  O                            $ DEFINE/SYSTEM/EXEC MX_HOLDn_REQUEST_DELIVERY FALSE   <           This logical name prevents the holding queue agent>           from sending any ETRN commands at all; use this when@           the remote system does not support ETRN or if you need>           to control the holding queue agents manually at both!           ends of the connection._  O                            $ DEFINE/SYSTEM/EXEC MX_HOLDn_HOST_NAME "name"[,...]r  =           This logical names overrides the parameters sent on <           the ETRN command. Multiple names may be specified;<           enclose each in quotation marks, and separate them>           with commas. The value of each name is passed to the?           remote system exactly as entered; you may use the "@" ?           or "#" prefix character to specify a domain name or a_?           queue identifier (see RFC 1985 for more information). ?           Use this logical name when the remote system supportsr<           ETRN but is not running MX, or if the IP host name<           used on the local system does not match the /ROUTE?           host names used in the MX configuration on the remotei           system.         
           7-4  r       A                 Configuring MX for Part-Time Internet Connections         L           __________________________________________________________________      7.5    Example Configuration_  =           This example shows the commands used to configure a ?           client servicing the domain "mxclient.com", with host_@           name "mailer.mxclient.com", and a server with the host&           name "mailhub.mxserver.com".             Client configuration:   /           MCP> DEFINE PATH "mxclient.com" LOCAL 6           MCP> DEFINE PATH "mailer.mxclient.com" LOCALI           MCP> DEFINE PATH * HOLDING_QUEUE=1/ROUTE="mailhub.mxserver.com"              Server configuration:_  /           MCP> DEFINE PATH "mxserver.com" LOCAL 7           MCP> DEFINE PATH "mailhub.mxserver.com" LOCALaU           MCP> DEFINE PATH "mxclient.com" HOLDING_QUEUE=1/ROUTE="mailer.mxclient.com" \           MCP> DEFINE PATH "mailer.mxclient.com" HOLDING_QUEUE=1/ROUTE="mailer.mxclient.com"!           MCP> DEFINE PATH * SMTPL                                      A                                                               7-5r n  n                A           _______________________________________________________m  /    8      Reducing or Eliminating "Junk" E-Mails      9           This chapter describes the facilities in MX fory:           preventing unwanted "junk" e-mail messages (also.           called "spam") from being processed.  L           __________________________________________________________________       8.1    What is "junk" E-Mail?  =           The Internet has grown explosively since its humblee9           beginnings as a tool for researchers wishing to :           exchange information. The designers of the early8           Internet electronic mail systems and standards9           kept SMTP simple (in fact, the S in SMTP stands <           for "Simple"), operating under the assumption that?           Internet users were, for the most part, well-behaved.X  >           Due to the explosive growth, there are now many more>           people using the Internet that are not well-behaved,=           exploiting the openness of SMTP and the low cost ofa=           generating immense e-mail distribution lists eithern;           to annoy or to send unsolicited advertisements toQ>           the huge number of people who currently use Internet           e-mail.e  :           This use of e-mail, while costing almost nothing=           to the sender, can place a heavy burden-in terms ofi@           network and system resources-on the sites that receive=           these unsolicited messages. System managers wishings>           to reduce the number of unwanted "junk" messages can@           configure MX to block them from being received locally=           as well as prevent their systems from being used as =           a "relay" point, sometimes employed by unscrupulousQ<           "spammers" that have had their own systems blocked.           from direct delivery by other sites.  A                                                               8-1t S  u    /           Reducing or Eliminating "Junk" E-Mail           ?           You can get more information about junk e-mail on the 9           World Wide Web from http://spam.abuse.net/spam.m  L           __________________________________________________________________      8.2    MX Filtering Features   @           MX contains several features to help curb junk e-mail:  =           o  The MCP command SET SMTP/VALIDATE_SENDER_DOMAIN, 9              which causes the SMTP server to validate the 7              sender's domain name on incoming messages;   <           o  The MCP command SET SMTP/NORELAY, which rejectsA              mail that does not originate at your site and is not($              destined for your site;  <           o  The REJMAN utility, which manages a database of:              rejection criteria that you can populate with<              address and header patterns that have been used              by spammers.1  >           o  Heuristic junk mail filters, also managed through<              the REJMAN utility, which filter potential junkA              mail based on the characteristics and/or contents of 5              message headers in various combinations.   L           __________________________________________________________________      8.3    Sender Validationy  =           Spammers often hide their identity by using a false >           return address on their messages. In many cases, the=           return address contains a domain name that does not =           actually exist in the Domain Name System (DNS). You ;           can have the SMTP server validate the domain name =           appearing in SMTP MAIL FROM commands (which specify >           the return address for SMTP messages) to ensure that>           it exists in the DNS with the following MCP command:  ?                            MCP> SET SMTP/VALIDATE_SENDER_DOMAINO  
           8-2u    f    A                             Reducing or Eliminating "Junk" E-MailC          <           This feature should only be enabled if you use the>           Internet and the Domain Name System. You should also=           ensure that all of your legitimate users that mightn=           send mail via SMTP to your system (such as PC userss<           with POP mail clients) have their systems properly@           configured to send valid domain names as part of their           return addresses.s  <           Reliable DNS service is also helpful when enabling;           this feature; if the SMTP server cannot resolve a @           domain name due to communication problems with the DNS6           server, the validity check is not performed.  L           __________________________________________________________________  +    8.4    Disabling the SMTP Relay Function   4           In some cases, junk e-mail senders who are=           unsuccessful in getting messages delivered directlyf<           from their own systems, or who wish to obscure the<           source of the junk messages, take advantage of the=           "relay" function available in most SMTP servers. Bys@           default, most SMTP servers accept messages coming from?           any source and will attempt to deliver those messagesi<           to any destination, even if both the source of the>           message and its intended recipients are remote. This@           is called relaying. The MX SMTP server allows relaying?           by default; you can disable the relay function if youd@           wish to prevent your system from being used as a relay            point for junk e-mail:  8                            MCP> SET SMTP/NORELAY_ALLOWED  ?           Once relaying is disabled, the SMTP server checks the @           envelope FROM address (also called the Return-Path) of@           each incoming message to see if it is local or remote.@           It also checks each recipient address. If the envelope;           FROM address is remote and a recipient address ist@           remote, delivery to the remote recipient is refused by           the server.h  A                                                               8-3_ _  _    /           Reducing or Eliminating "Junk" E-MailC          ?           The SMTP server uses the following tests to determine <           whether or not an envelope address (either FROM or(           recipient) is local or remote:  >           1  The address is passed through the message routing:              rules (rewrite rules and path checks). If the?              resulting path is LOCAL, the address is considered               local.   =           2  If the address does not resolve to a LOCAL path,oA              the host name in the address is compared against thee>              MX host name. If both names are the same, or both?              hosts share the same parent domain, the address isl              considered local.  ?           3  If the previous check did not classify the address A              as local, it is repeated using the TCP/IP host name.n  ?           4  If none of the above checks classified the addressT<              as local, the host name is compared against the=              local domains list, which you configure with the )              DEFINE LOCAL_DOMAIN command._  =           You may need to use the DEFINE LOCAL_DOMAIN commandf7           if your host acts as a mail gateway for other 8           systems that are not part of your home domain.;           For example, if your system is part of the domainc:           mycompany.com but also acts as a gateway for the7           domain theircompany.com, you would define the_"           following local domains:  D                            MCP> DEFINE LOCAL_DOMAIN theircompany.comF                            MCP> DEFINE LOCAL_DOMAIN *.theircompany.com  <           These commands will cause the SMTP server to treat:           any address of the form user@theircompany.com or=           user@somehost.theircompany.com as being "local" forl2           the purposes of relay-rejection testing.    
           8-4h e  r    A                             Reducing or Eliminating "Junk" E-Maila        %           ___________________________   /    8.4.1  Identifying Inside Networks and Hostsp  =           You can further strengthen the anti-relay checks byl<           using the DEFINE INSIDE_NETWORK_ADDRESS command to;           create a list of IP network and/or host addressesa@           that are considered to be "inside" your local network.<           Creating this list prevents an outside system from@           using your system as a junk mail relay by masquerading<           as a local user (by using one of your local domain/           names in the SMTP MAIL FROM address).   ;           If your system is acting as a relay between other ;           hosts on your network(s) and the Internet, or youe@           have POP or IMAP mail clients that send their messages=           through your system, you should add your network(s)o<           to the list. For example, if your local network is?           10.10.10.0, set up with a 24-bit subnetwork mask, you            would specify   ^                            MCP> DEFINE INSIDE_NETWORK_ADDRESS 10.10.10.0/NETMASK=255.255.255.0  9           Any SMTP connection coming from a system on thet8           10.10.10.0 network would be allowed to specify9           a local domain in the SMTP MAIL FROM command inh@           combination with a list of recipients that are outside<           your domain; all other systems would be considered=           "outside", and would be unable to specify a list of$@           outside recipients even when sepcifying a local domain            in the SMTP MAIL FROM.  @           If there were another mailer for your network (such as?           another system in the Domain Name System list of mailo@           exchanger [MX] records for your domain) at the address-           10.10.20.37, you would also specify   I                            MCP> DEFINE INSIDE_NETWORK_ADDRESS 10.10.20.37E  <           By omitting the /NETMASK qualifier, the address is5           assumed to be a host rather than a network.   A                                                               8-5  7       /           Reducing or Eliminating "Junk" E-Mail           <           If your system is the only mailer for your domain,?           and you do not have any POP or IMAP mail clients, you            should specify  G                            MCP> DEFINE INSIDE_NETWORK_ADDRESS 127.0.0.1T  =           to enable the inside-address checks and prevent anyI?           other system from using a local e-mail address in then<           SMTP MAIL FROM in order to relay to outside hosts.  9           The DEFINE INSIDE_NETWORK_ADDRESS command has aD>           /REJECT qualifier that allows you to set up specific8           exceptions to the list for individual hosts or?           subnetworks. For example, if on your local 10.10.10.0l?           network, there is one host (10.10.10.100) that shoulds7           not be considered "inside", you could specifya  R                            MCP> DEFINE INSIDE_NETWORK_ADDRESS 10.10.10.100 /REJECT  8           to eliminate that host from the "inside" list.  :           Note that the list of addresses is kept in order?           based on the length of the network mask, from longestt:           (host addresses) to shortest. The list is search=           sequentially from the beginning for a match against (           the sending host's IP address.  L           __________________________________________________________________  !    8.5    Realtime Blackhole List   9           The Mail Abuse Protection System (MAPS) projectm=           maintains the Realtime Blackhole List (RBL), a listt<           of network and host addresses of known junk e-mail@           abusers. Information on RBL and other MAPS efforts can*           be found at http://maps.vix.com.  >           MAPS makes the RBL available in two forms: a routing@           protocol (for routers) and the domain name system (for           hosts).   @           Several Internet Service Providers (ISPs) subscribe to=           the RBL routing information, and will automatically 8           "black-hole" any TCP/IP packets that come from<           the offending hosts and networks. If your ISP does  
           8-6          A                             Reducing or Eliminating "Junk" E-Mails          ;           not subscribe to the RBL, you can configure MX to @           perform an RBL domain name system check for every host?           connecting to the SMTP server. If the connecting hosts>           is found in the RBL, the SMTP server will refuse any#           message it tries to send.   ?           Use the following MCP command to enable RBL checking:   2                            MCP> SET SMTP/RBL_CHECK  ?           RBL checking is disabled by default. Consult the MAPSs<           web site to get full information on how the RBL is2           maintained before enabling this feature.  %           ___________________________       8.5.1  Other RBL Providersn  1           If you would prefer to use the servicest3           of another RBL provider (for example, see >           http://www.dorkslayers.com), you may specfy a domain;           name on the /RBL_CHECK qualifier to have the SMTP,?           server check in that domain for a blocked system. Forc           example:  H                            MCP> SET SMTP/RBL_CHECK="rbl.dorkslayers.com"  <           If you specify /RBL_CHECK with no domain name, the9           MAPS RBL (rbl.maps.vix.com) is used by default.   L           __________________________________________________________________  5    8.6    Establishing Rejection Criteria with REJMANs  9           The REJMAN utility lets you create and manage aE9           database containing criteria by which MX's SMTP =           server will reject incoming messages as junk e-mail >           that you do not want to be processed. See REJMAN for4           information on how to invoke this utility.  ?           REJMAN provides commands for rejecting messages basedl?           on envelope contents (combinations of return address,i:           recipient address, and the TCP/IP address of the>           sending host) as well as on headers contained in the           message.  A                                                               8-7          /           Reducing or Eliminating "Junk" E-MailA        %           ___________________________s  "    8.6.1  Address-Based Rejections  9           The REJMAN ADD REJECTION command can be used to ?           configure the SMTP server to reject incoming messages >           with specific return addresses or matching specified8           patterns, or being sent from particular hosts.>           Messages matching the rejection criteria are refused<           by the SMTP server before the message contents are>           sent-reducing network load as well as the processing           load on your system.  <           If your users are being bombarded with unwanted e-<           mail, review the unwanted messages for the Return-<           Path: header and the Received: headers (you should<           ensure that your SET LOCAL settings do not prevent8           those headers from being included in delivered>           messages). You can program a rejection rule into the4           SMTP server based on the Return-Path with:  ?                            REJMAN> ADD REJECTION sender-addresse  <           For example, if some junk e-mail had a Return-Path>           address of <spammer@spamhost.com>, you would use the           command:  G                            REJMAN> ADD REJECTION "spammer@spamhost.com""  =           If the Return-Path has different usernames, but the.;           same host name, you could use a wildcard pattern:E  A                            REJMAN> ADD REJECTION "*@spamhost.com"   :           to reject all messages coming from spamhost.com.  =           If a large number of junk messages were all sent toH=           your host from another single host or network, they ;           would all have Received: headers that follow this1           pattern:  E           Received: from spam-source.com by yourhost.com with SMTP...   
           8-8          A                             Reducing or Eliminating "Junk" E-Mail           >           You can block incoming messages sent by a particular>           host or on hosts from a particular network using the=           /ADDRESS qualifier on the DEFINE REJECTION command.r>           For example, if spam-source.com has an IP address of-           10.0.0.1, you could use the command_  G                            REJMAN> ADD REJECTION "*@*"/ADDRESS=10.0.0.1   ?           to have the SMTP server refuse all messages that weree@           sent or relayed through that particular host. You must=           know the IP address of the host in order to use thef=           /ADDRESS qualifier. Address specifications may alsod=           contain wildcards so you can block entire networks.   @           Once you have added one or more rejection rules to the@           database, you must use MCP to reset the SMTP server to)           have the new rules take effect:a  1                            MCP> RESET SMTP_SERVER   <           Note: Exercise caution when establishing rejection9           rules. An incorrect rule could block legitimatem=           messages from reaching their intended destinations.n  8           The ADD REJECTION command has more options for?           narrowing the scope of a rejection based on recipient 8           addresses, for setting the text of the message>           returned when a rejection occurs, and for forwarding?           messages that would have been rejected to a different =           address to collect evidence of junk e-mail. See ADD )           REJECTION for more information.e  %           ___________________________c  !    8.6.2  Header-based Rejections   =           As spammers have become more sophisticated, junk e- ?           mail messages have started looking more and more like <           legitimate messages, with perfectly valid envelope<           information. Such messages, however, often contain=           RFC822 message headers that can be used to identify ?           them as junk. To block such messages, REJMAN provides @           for the addition of header-based rejection rules, with           ADD REJECTION/HEADER:.  A                                                               8-9_ _  _    /           Reducing or Eliminating "Junk" E-Mail           K                            REJMAN> ADD REJECTION/HEADER header-text-patterne  :           For example, some types of junk e-mail messages,?           advertising "get rich quick" schemes contain Subject:'<           headers that begin and end with a string of dollar           signs, as in:w  :                            Subject:  $$ MAKE MONEY FAST $$  =           Since it is unlikely that a legitimate message will =           contain a Subject: header that begins and ends with ;           dollar signs, you might want to add the following 8           header-based rejection to the REJMAN database:  H                            REJMAN> ADD REJECTION/HEADER "Subject: $$*$$"  ?           This will cause the SMTP server to reject any message 8           containing a header that matches this pattern.  ?           Note: As with address-based rejections, you should bes=           careful when creating header-based rejection rules,_@           to prevent the unwanted rejection of legitimate e-mail           messages.i  ?           For header-based rejections, the SMTP server receivess>           the entire text of an incoming message before it can?           identify an unwanted message and return a status codeN;           to the sending system indicating that the messagel<           was not accepted (due to the way the SMTP protocol>           operates). Address-based rejections occur before any           message data is sent.   :           Rejections based on header information cannot be;           redirected to other addresses, nor can you modify ;           the message returned to the sending system when au(           header-based rejection occurs.                   8-10 s  l    A                             Reducing or Eliminating "Junk" E-Maile        %           ___________________________       8.6.3  Tracking Rejections   ?           Tracking information is stored in the REJMAN databaser=           for each rejection rule. This information includes:y  @           o  the date and time you added a rule to the database;  >           o  the date and time the SMTP server last rejected a+              message based on the rule; anda  =           o  a count of the number of times the rule has been %              used to reject a messageD  =           This information is mainly for your use, so you can <           gauge the effectiveness of the rejection rules you@           have entered. The SMTP server periodically updates the>           statistics in the database, and updates the database(           when it is reset or shut down.  %           ___________________________       8.6.4  Purging Old Rules   ?           Since particular patterns of junk e-mail envelope and >           header characteristics tend to last only for a short?           time, REJMAN includes a PURGE command to allow you to @           delete rules from the database that have not been used           recently:v  <                            REJMAN> PURGE [/BEFORE=date-time]  =           Unless you specify the /BEFORE qualifier, the PURGEX?           command will remove rules from the database that havel?           not been used to reject messages for 30 days or more.e  =           Periodically using the PURGE command helps keep the @           database from growing too large, reducing the overhead4           involved in performing junk e-mail checks.  A                                                              8-11f         /           Reducing or Eliminating "Junk" E-Mailm        L           __________________________________________________________________      8.7    Heuristic Filterse  :           Senders of junk e-mail use various techniques to;           disguise the source of their messages, and change :           their source addresses frequently. This makes it:           difficult to keep rejection rules up-to-date. In;           spite of these changes in addresses, most junk e-e>           mail messages exhibit certain characteristics in the=           contents of their headers. The SMTP server containsT;           a number of heuristic filters that look for these @           characteristics and classify matching messages as junk           mail.L  9           The filters are called "heuristic" because they ;           determine only the probability that a message may ?           be junk e-mail, based on rules created from empirical ;           observation of thousands of junk e-mail messages. ;           It is possible for legitimate, non-junk e-mail tol=           match one or more of these filters, too. Because ofs=           this, the heuristic filters come with configuration ?           options for forwarding matching messages to a mailboxo<           (typically the local Postmaster or system manager)@           for further review, and for creating exceptions to the0           filters based on the sender's address.  ?           The REJMAN utility is used to configure the heuristic @           filters, using the commands described on the following           pages:  /           o  ENABLE HEURISTIC, ENABLE HEURISTIC   1           o  DISABLE HEURISTIC, DISABLE HEURISTICs  +           o  SET HEURISTICS, SET HEURISTICSu  )           o  ADD EXCLUSION, ADD EXCLUSIONo  /           o  DELETE EXCLUSION, DELETE EXCLUSION   9           The REJMAN SHOW HEURISTICS command displays theP5           current settings for the heuristic filters.              8-12 E  C    A                             Reducing or Eliminating "Junk" E-Mail         %           ___________________________t      8.7.1  Confidence Levelsr  <           The heuristic filters provided by MX are listed in?           Table 8-1. Each filter is assigned a confidence level @           (CL) that represents, on a scale from zero to ten, the@           probability that a message matching the filter is junk>           mail. The default CL for each filter is shown in the=           table; you can change these values when configuring             the heuristic filters.  <           When a message is received by the SMTP server, its@           headers are checked against each heuristic filter, and>           the message is assigned the highest CL found for all?           matching filters. When no filters match, the assignedy           CL is zero.   >           The message's assigned CL is the checked against two=           configurable threshold values, the accept thresholdt#           and the reject threshold.   <           o  If the assigned CL is less than or equal to the;              accept threshold, the message is classified asg=              legitimate mail, and no further action is taken.s  :           o  If the assigned CL is greater than the reject?              threshold, the message is classified as junk mail,o              and is rejected.   >           o  If the assigned CL is between the two thresholds,;              it is classified as "probable" junk; it is not :              rejected, but additional headers are inserted=              into the message to warn the recipient about itsP              classification.            A                                                              8-13i a  o    /           Reducing or Eliminating "Junk" E-Mail,          A           Table_8-1__Heuristic_Filters___________________________   )                                   DefaulttA           Filter_name_____________CL________Description__________u  <           FROM_TO_SENDER_SAME     10        Matches when the;                                             SMTP MAIL FROM:u@                                             address matches both=                                             the From: and To:_<                                             addresses in the;                                             RFC822 headers.   <           INVALID_AOL_ADDRESS     10        Matches when the?                                             RFC822 From: or To:t>                                             headers contain an?                                             invalid address for =                                             AOL.COM (username 7                                             too long or.>                                             containing invalid7                                             characers).l  <           INVALID_HOTMAIL_        10        Matches when the;           ADDRESS                           RFC822 From: or ?                                             To: headers containt>                                             an invalid address?                                             for HOTMAIL.COM, or0>                                             when the SMTP MAIL<                                             FROM: and RFC822;                                             From: addresses_;                                             are HOTMAIL.COMo=                                             addresses and thed>                                             message is missing>                                             the X-Originating-;                                             IP: header thatn?                                             HOTMAIL.COM mailers.?                                             add to all outgoing_5                                             messages.                  8-14 P  e    A                             Reducing or Eliminating "Junk" E-Maile          A           Table_8-1_(Cont.)__Heuristic_Filters___________________-  )                                   DefaultnA           Filter_name_____________CL________Description__________.  <           MSGID_HAS_FROM          10        Matches when the>                                             Message-ID: header?                                             contains the RFC822o:                                             From: address.  <           MSGID_HAS_TO            10        Matches when the>                                             Message-ID: header?                                             contains the RFC822 8                                             To: address.  >           NULL_FROM               8         Matches when there>                                             is no RFC822 From:9                                             header in thec;                                             message, or thel=                                             header is present 6                                             but empty.  <           NULL_MSGID              10        Matches when the>                                             RFC822 Message-ID:=                                             header contains a <                                             null message ID.  >           NULL_TO                 6         Matches when there<                                             is no RFC822 To:9                                             header in thed;                                             message, or theh=                                             header is presentk6                                             but empty.              A                                                              8-15"         /           Reducing or Eliminating "Junk" E-Mailt          A           Table_8-1_(Cont.)__Heuristic_Filters____________________  )                                   Default_A           Filter_name_____________CL________Description__________h  <           NUMERIC_ADDRESS         7         Matches when the@                                             username part of the@                                             From: or To: address9                                             contains onlyf>                                             digits. Exceptions<                                             are provided for<                                             domains known to;                                             use all-numerice>                                             usernames, such as8                                             MCIMAIL.COM.  <           PRECEDENCE_BULK         4         Matches when the>                                             message contains a>                                             Precedence: header?                                             containing the wordf3                                             "bulk".   :           RECEIVED_AFTER_FROM     4         Matches when a<                                             Received: header:                                             is found after=                                             the From: header. ;                                             This is usually >                                             an indication that>                                             the sender did not;                                             include a From:R9                                             header in theT=                                             original message,i>                                             or that the sender@                                             forged the misplaced3                                             header.D                     8-16         A                             Reducing or Eliminating "Junk" E-Mailr          A           Table_8-1_(Cont.)__Heuristic_Filters___________________   )                                   DefaultpA           Filter_name_____________CL________Description__________u  8           RECEIVED_ALL_ZEROS      10        Matches when7                                             a Received:>;                                             header is founde;                                             after the From:e<                                             header, and that<                                             Received: header?                                             contains the string >                                             "000.000.000.000".  <           UIDL_AUTH_SENDER        10        Matches when the<                                             message contains=                                             an X-UIDL: headert;                                             and a Comments:A7                                             header that ?                                             contains the string :                                             "authenticated7                                             sender is".   <           X_UIDL                  8         Matches when the?                                             message contains ant@                                             X-UIDL: header. This>                                             header is normally>                                             used internally by@                                             some POP servers and?                                             clients to uniquelyo=                                             identify messages =                                             in mailboxes, andc@                                             should not generally@                                             be found in outboundA           __________________________________messages.____________a          A                                                              8-17i n       /           Reducing or Eliminating "Junk" E-Maila        %           ___________________________       8.7.2  Rejection Actionse  7           When a message's confidence level exceeds the :           rejection threshold, the SMTP server applies the>           rejection action that you configure. This action can;           either be REJECT, which causes the SMTP server to ?           refuse the message, or FORWARD, which causes the SMTP @           server to accept the message, but forward it either to<           the local Postmaster or to an address you specify.  9           By setting the rejection action to FORWARD, you <           can review messages that have been rejected by the:           filters and recover those messages that may have9           been misclassified. Each forwarded message willl9           contain additional headers listing the original =           sender and recipients, plus a header that indicates ?           the filter that caused the message to be rejected. If =           a legitimate message was misclassified, you can use-<           the REJMAN ADD EXCLUSION command to prevent future?           messages from the same originating address from beingS           rejected.e  %           ___________________________       8.7.3  Junk Mail Warnings  @           For a message that is identified as possible junk mail=           but is not rejected, the SMTP server inserts one or ?           two headers to warn the recipient(s) that the message ;           was identified as junk mail. The first header is:   J                                 X-Junk-Mail-Rating: {LOW, MEDIUM, or HIGH}  >           LOW indicates a CL less than 4; MEDIUM, 4 through 7;=           HIGH, 8 or higher. If your users have e-mail client @           programs that can also perform filtering, the addition>           of this header should make it simple for them to set>           their own policy regarding junk mail that is sent to           them.e             8-18 m       A                             Reducing or Eliminating "Junk" E-Mailt          9           You may configure the SMTP server to include ans;           additional header that identifies the filter thatd?           caused the message to be classified as junk mail. Theg@           REJMAN command that turns on this additional header is(           SET HEURISTICS/INCLUDE_REASON.  L           __________________________________________________________________  (    8.8    Logging SMTP Server Rejections  9           You can have the SMTP server notify you when itu<           rejects a message due to sender validation, REJMAN<           rules, or heuristic checks by defining the logical-           name MX_SMTP_REJECTION_EVENT_CLASS:   ^                            $ DEFINE/SYSTEM/EXEC MX_SMTP_REJECTION_EVENT_CLASS opcom-class-name  7           If that logical name is defined as one of thei=           OPCOM event class names, the SMTP server will log ai?           notification each time it rejects an incoming message ;           based on DNS validation of the sender address, ort<           based on the rejection rules you have added to the           REJMAN database.  L           __________________________________________________________________  9    8.9    Debugging Rejection Rules and Heuristic Filtersn  ?           The SMTP server contains some additional logging codet<           for debugging REJMAN rejection rules and heuristic=           filters. You can enable this debug logging with thee,           following logical name definition:  H                            $ DEFINE/SYSTEM/EXEC MX_ANTI_SPAM_DEBUG level  @           where level is an integer value greater than zero that>           specifies how much information should be included in?           the debug log. Basic information is included when them<           debug level is 1; more detail is included when the%           debug level is 2 or higher.e  <           After defining this logical name, you must use MCP>           to RESET the SMTP server. To turn off debug logging,<           you should DEASSIGN the logical name and RESET the>           SMTP server. That will close the log file so you can#           examine the debug output.l  A                                                              8-19r n  o                A           _______________________________________________________.  '    9      Other Miscellaneous Utilities       ?           This chapter describes other utilities available withn
           MX.m  L           __________________________________________________________________      9.1    The MLFAKE Utility  ?           For those times when you need to act on behalf of oneo=           of your users to sign off or subscribe to a mailing 5           list, the MLFAKE utility may come in handy:   8                             $ MLFAKE  :== $MX_EXE:MLFAKEO                             $ MLFAKE  listname  hostname  [command] [arguments]m3                                 /LISTSERV[=lsvname] 3                                 /REQUEST=reqaddressn.                                 /FROM=fromuser  ;           Specify the name of the mailing list and its hostn9           (with no @ in between). If you omit command, itr6           defaults to SIGNOFF. If the command requires=           additional arguments, you should specify them after ?           command (in which case you must specify the command).t>           If the mailing list is managed by a BITNET LISTSERV,<           use the /LISTSERV qualifier; otherwise the request;           will go to the -Request address for the list (theh@           Internet convention). You can override this altogether=           by specifying the request address with the /REQUESTl>           qualifier. Finally, you must specify who the request:           is supposed to be from with the /FROM qualifier.             For example:  G                            $ MLFAKE/FROM=someuser MX-List LISTS.WKU.EDU L                            $ MLFAKE/FROM=someuser ESL-L UBVM.BITNET/LISTSERVF                            $ MLFAKE/FROM=someuser/REQUEST="FileServ" -A                            _$         "" WKU.EDU SEND MX040.BLURBT  A                                                               9-1          '           Other Miscellaneous Utilities           ;           The first example is for an Internet-type mailingr?           list. The message will be constructed with "someuser"C?           as the originator and MX-List-Request@vms.ecs.rpi.eduE?           as the destination, with the message reading SIGNOFF.1?           In the second example, for a BITNET mailing list, theb<           destination will be LISTSERV@UBVM.BITNET, with the@           message reading SIGNOFF ESL-L. The third example shows@           how MLFAKE can be used with file servers by specifying>           the destination user with the /REQUEST qualifier and?           omitting the listname argument (which is ignored whenu!           /REQUEST is specified).   <           MLFAKE requires SYSPRV privilege. SYSLCK privilege;           is not required, but will speed processing of theh=           message. DO NOT install the MLFAKE image with thesei;           privileges! Only trusted users should have accessi>           to this utility, since it can be used to fake a mail&           message from any other user.  L           __________________________________________________________________      9.2    The MAILQUEUE Utility   =           MAILQUEUE is a program that scans the message queue ?           for entries still in progress. It can be used by non- ;           privileged users to view only those entries which ;           were sent by them. When used from an account with @           SYSPRV privilege turned on, it lists all pending queue           entries.  ;           MAILQUEUE resides in the MX_EXE: directory and isr;           designed to be executed as a DCL foreign command:t  =                            $ MAILQ*UEUE :== $MX_EXE:MAILQUEUEt"                            $ MAILQ  =           If there are no delayed messages, MAILQUEUE returns            the message   V                            %MAILQ-I-MQNONE, no MX mail messages queued on local system  
           9-2M ,       A                                     Other Miscellaneous Utilities_          <           Otherwise, the MAILQUEUE display will resemble the           following:  Q                            Entry: 9872, Origin: [Jnet] <SOMEUSER@YOYODYNE.BITNET>e0                              Status: IN-PROGRESS=                              Local entry #9874, status: READYsQ                                  Waiting for retry until: 15-NOV-1991 16:46:44.12 S                                  Recipient #1: SOMEUSER, Route=myhost.mycompany.com /                                  Error count=93AY                                  Last error: %MAIL-E-OPENOUT, error opening !AS as output   X                            Entry: 10859, Origin: [Local] <FileServ@myhost.mycompany.com>Q                              Status: READY, waiting until 15-NOV-1991 18:00:00.00 \                                Recipient #1: <SOMEUSER%SOMEHOST.BITNET@myhost.mycompany.com>  L           __________________________________________________________________      9.3    The MX_DECODE Utilityr  :           The MX_DECODE utility will decode MIME-compliant:           mail messages with contents encoded as BASE64 or>           QUOTED-PRINTABLE. If the content type of the message<           is APPLICATION/VMS-RMS, it will also automatically9           restore the file's original RMS attributes. The :           MX Local agent automatically decodes VMS-RMS and<           QUOTED-PRINTABLE when they are received. MX_DECODE<           is provided for use in decoding messages delivered?           by other mailers, as well as for use with the MX Site ?           agent, so that messages destined for MX Site may sent            using SEND/FOREIGN.   ?           MX_DECODE should be executed using a foreign command:   @                            $ MX_DECODE :== $MX_EXE:MX_DECODE.EXEB                            $ MX_DECODE MAIL_MESSAGE.BASE64 XYZ.xxx  @           It accepts two required parameters: the input file and=           the output file. By default, in order to decode the =           file properly, the input file must include the MIME =           RFC822 headers before the encoded body. The headersM?           are used only to find the stored VMS file attributes._<           If the file has a content type of APPLICATION/VMS-<           RMS, the resulting decoded output file will retain  A                                                               9-3e         '           Other Miscellaneous Utilities-          >           all of the VMS file attributes of the original file.:           Otherwise, the format of the resulting file will>           either be fixed-length, 512-byte records (for binary>           BASE64-encoded messages) or a text file (for QUOTED-6           PRINTABLE and BASE64-encoded text messages).  :           You can also decode base64-encoded files without;           the mail headers by using the qualifier /NOHEADERe=           to tell MX_DECODE that there are no mail headers in <           the file, only encoded text. By default, MX_DECODE?           will produce a standard VMS binary file (fixed-lengtho=           512-byte records). If the text you're decoding is ar=           text file, you can specify /TEXT to create a normal ;           VMS text file. If it is a text file encoded usinge@           QUOTED-PRINTABLE, use the /QUOTED_PRINTABLE qualifier.                                                  
           9-4                      A           _______________________________________________________       10     Troubleshooting MX      <           This chapter contains information on MX useful for"           debugging MX components.  L           __________________________________________________________________  +    10.1   Queue Files Used by MX Componentse  ?           As has already been discussed, each MX component usesm>           files in the message queue when processing messages.@           Each queue entry has at least one file associated with@           it, usually containing envelope information. The files<           created by MX are stored in a directory tree under@           the MX_FLQ_DIR: directory. The files are named n.type,>           where n is the queue entry number and type is a file;           type indicating the type of information is in the            file.t  9           There are ten subdirectories under the MX queuea<           directory. The subdirectories are used to keep the=           size of the MX queue .DIR files below 128 blocks sot=           that they can be cached by RMS. The subdirectory inf<           which a file is located is determined by using the>           last digit in the file name as the subdirectory name"           ([.0], [.1], ..., [.9]).  =           Most of the queued files used by MX contain records ;           written in tag-length-value (TLV) format. The tag 9           and length fields are written in binary format, ;           although the value may contain plain ASCII. While =           more efficient for MX, this storage format makes it @           more difficult to display the contents of these files,=           since the binary headers tend to confuse terminals. ?           When examining these files, it is usually best to usee8           DUMP or a text editor, rather than using TYPE.  A                                                              10-1  d                  Troubleshooting MX        %           ___________________________       10.1.1 File Types  :           The following list describes the file types used>           for queue files, the agents that write them, and the            agents that read them.  <           SRC_INFO. This is the envelope information written:           on message entry. This file contains TLV records?           indicating the source of the message, the originating ?           address, and the recipient addresses. Written by: MX_ @           MAILSHR, DNSMTP_SERVER, XSMTP_SERVER, SMTP_SERVER, MX_=           JNET (incoming), MX_RMAIL, MX_SITE_IN. Read by: MX_            ROUTER.   >           HDR_INFO. This file contains the message headers, in>           TLV format. The headers are only used during address<           conversion when gatewaying mail into UUCP or Jnet,>           or for making return-address determinations on local<           delivery of mail. Written on message entry by: MX_@           MAILSHR, DNSMTP_SERVER, XSMTP_SERVER, SMTP_SERVER, MX_=           JNET (incoming), MX_RMAIL, MX_SITE_IN. Read by: MX_ ?           LOCAL, MX_JNET (outgoing), MX_SMTP, MX_UUCP, MX_SITE, .           MX_MLF, MX_LSV, MX_DNSMTP, MX_XSMTP.  >           MSG_TEXT. This file contains the text of the body of?           the message, in plain ASCII. Written on message entry <           by: MX_MAILSHR, DNSMTP_SERVER, XSMTP_SERVER, SMTP_@           SERVER, MX_JNET (incoming), MX_RMAIL, MX_SITE_IN. Read?           on message delivery by: MX_LOCAL, MX_JNET (outgoing), ?           MX_SMTP, MX_UUCP, MX_SITE, MX_MLF, MX_LSV, MX_DNSMTP,            MX_XSMTP.   >           DNSMTP_INFO, JNET_INFO, LOCAL_INFO, SMTP_INFO, UUCP_=           INFO, SITE_INFO, MLF_INFO, XSMTP_INFO . These filesa;           contain envelope information used by the deliveryd<           agents. Written by: MX_ROUTER. Read by: MX_DNSMTP,?           MX_JNET, MX_LOCAL, MX_SMTP, MX_UUCP, MX_SITE, MX_MLF,o"           MX_XSMTP (respectively).             10-2 -  L    A                                                Troubleshooting MXo          =           JNET_INPUT. This file is used by the Jnet interface >           for holding the original message as it comes in from@           Jnet until it can be processed by MX_JNET. Written by:2           MX_MFSDISP. Read by: MX_JNET (incoming).  >           Note that the SRC_INFO, HDR_INFO, and MSG_TEXT files=           remain attached to the original (base) queue entry.t<           When the queue entries for the delivery agents are=           created, a back link to the original queue entry iss?           entered so the delivery agents can gain access to the >           headers and message text. In addition, forward links@           to the delivery agent entries are kept in the original<           queue entry, which are zeroed out as each delivery?           agent finishes its processing. When all forward linkse<           are zeroed, the original queue entry is changed to           FINISH status.  L           __________________________________________________________________      10.2   Process NamesF  ?           The MX_START.COM command procedure assigns a specifica?           process name to each of the MX detached processes. Too?           determine whether an agent is running or not, use thet>           MCP command STATUS or examine the SHOW SYSTEM output*           for the following process names:  #           MX Router      The Router   -           MX FLQ         The MX queue managerw           Managert  ,           MX SMTP        SMTP delivery agent  8           MX DNSMTP      SMTP-over-DECnet delivery agent  6           MX XSMTP       SMTP-over-X.25 delivery agent  $           SMTP Server    SMTP server  -           MX Local       Local delivery agentE  ;           MX Jnet        Jnet interface (delivery agent ands4           Intfc          incoming message processor)  ?           MX LSV         Gateway to L-Soft's LISTSERV processor3  A                                                              10-3  s  e               Troubleshooting MX            1           MX MLF         Mailing list/file server   6           MX Site        Site-specific interface agent           Agentk  =           MX->SITE       Subprocess created by site interface-  '           MX uucp        UUCP interface            Intfci  =           MX->uucp       Subprocess created by UUCP interfacer  =           Note that the subprocesses are not created until ata=           least one message is processed by the correspondinge           delivery agent.f  L           __________________________________________________________________      10.3   Debug/Trace Output  :           Each of the delivery agents has debug/trace code?           that can be enabled to provide information on messageM>           processing. Tracing is enabled by defining a system-=           wide logical name, and disabled by deassigning thats?           logical. Debugging can be enabled or disabled "on thet=           fly": the process being debugged will automaticallyO8           start logging trace information for each entry6           processed after the logical name is defined.  @           The trace log file, by default, is created in the same>           directory used for the agent's main log file, with a@           file type of .LOG_process-id (for the SMTP server, the@           default file type is .LOG_process-id_thread-id). Trace<           output can be redirected by defining a system-wide@           logical name. The logical names used for debugging are!           outlined in Table 10-1.   9           There is no debugging code available in the MX_i;           MAILSHR/MX_MAILSHRP (the VMS MAIL interface), MX_ <           MFSDISP (the Jnet mail/file dispatcher), or in MX_           SITE_IN.             10-4 t       A                                                Troubleshooting MX_          A           Table_10-1__Debug/Trace_logical_names__________________   F                                                                DefaultB                                                                di-C                                                                rec-eC           Agent__________Enabling_logical___Trace_file_________tory   B           Jnet intfc     MX_JNET_DEBUG      MX_JNET_LOG        MX_D                                                                JNET_C                                                                DIR:.  B           Local          MX_LOCAL_DEBUG     MX_LOCAL_LOG       MX_E                                                                LOCAL_eC                                                                DIR:   B           Local          MX_LSV_DEBUG       MX_LSV_LOG         MX_C                                                                LSV_rC                                                                DIR:e  B           ML/FS          MX_MLF_DEBUG       MX_MLF_LOG         MX_C                                                                MLF__C                                                                DIR:t  B           RMAIL (UUCP    MX_UUCP_RMAIL_     MX_RMAIL_LOG       MX_D           in)            DEBUG                                 UUCP_C                                                                DIR:   B           Router         MX_ROUTER_DEBUG    MX_ROUTER_LOG      MX_F                                                                ROUTER_C                                                                DIR:   B           Router/file    MX_FLQ_DEBUG       MX_FLQ_LOG         MX_F           queue                                                ROUTER_C                                                                DIR:T  B           SMTP out       MX_SMTP_DEBUG      MX_SMTP_LOG        MX_D                                                                SMTP_C                                                                DIR:I  B           SMTP server    MX_SMTP_SERVER_    SMTP_SERVER_LOG    MX_D                          DEBUG                                 SMTP_C                                                                DIR:I  A                                                              10-5r e                  Troubleshooting MX          A           Table_10-1_(Cont.)__Debug/Trace_logical_names__________t  F                                                                DefaultB                                                                di-C                                                                rec- C           Agent__________Enabling_logical___Trace_file_________tory   B           SMTP-over-     MX_DNSMTP_DEBUG    MX_DNSMTP_LOG      MX_F           DECnet out                                           DNSMTP_C                                                                DIR:   B           SMTP-over-     MX_DNSMTP_SERVER_  DNSMTP_SERVER_LOG  MX_F           DECnet         DEBUG                                 DNSMTP_C           server                                               DIR:t  B           SMTP-over-     MX_XSMTP_DEBUG     MX_XSMTP_LOG       MX_E           X.25 out                                             XSMTP_dC                                                                DIR:   B           SMTP-over-     MX_XSMTP_SERVER_   XSMTP_SERVER_LOG   MX_E           X.25 server    DEBUG                                 XSMTP_sC                                                                DIR:A  B           Site Agent     MX_SITE_DEBUG      MX_SITE_LOG        MX_D                                                                SITE_C                                                                DIR:)  B           UUCP intfc     MX_UUCP_DEBUG      MX_UUCP_LOG        MX_D                                                                UUCP_C           _____________________________________________________DIR:l                               10-6 c  i                A           _______________________________________________________        11     The MX Startup Process      ;           This chapter describes the command procedures and .           files used by MX when it is started.  L           __________________________________________________________________  $    11.1   Startup Command Procedures  >           Typically, MX is started up by executing the command<           procedure SYS$STARTUP:MX_STARTUP.COM. This file is@           created at installation time simply to make MX easy to@           start; all it does is execute MX___STARTUP.COM,  which=           is located in the directory that eventually becomesc;           the equivalence name for the logical name MX_EXE.X=           MX___STARTUP.COM  contains the commands for settingf<           up the MX logical names and invoking MX_START.COM,?           also located in the MX_EXE directory, to start the MX            processing agents.  <           Individual MX components can be started by passing9           their names (one or more, separated with commas 9           and with no intervening blanks) as arguments to :           SYS$STARTUP:MX_STARTUP.COM. Table 11-1 lists the8           components that the startup command procedures           recognize.  A           Table_11-1__Component_names_for_use_with_MX_STARTUP.COME  A           Name___________Description_____________________________V  >           LOGICALS       Defines MX logical names and installs4                          the MX shareable libraries.      A                                                              11-1  o  %                The MX Startup Process          >           Table 11-1 (Cont.)  Component names for use with MX_A           ____________________STARTUP.COM________________________Y  A           Name___________Description_____________________________   :           NETLIB         Executes NETLIB's startup command=                          procedure. (Prerequisite for ROUTER,_>                          SMTP, and SMTP_SERVER if using TCP/IP"                          with MX.)  3           ROUTER         Starts the Router process.   9           LOCAL          Starts the local delivery agent.e  =           SMTP           Starts the SMTP-over-TCP/IP delivery                           agent.t  =           SMTP_SERVER    Starts the SMTP server (for TCP/IP).a  =           DNSMTP         Starts the SMTP-over-DECnet deliveryE                          agent.E  ;           XSMTP          Starts the SMTP-over-X.25 delivery                           agent.l  3           JNET           Starts the Jnet Interface.t  8           UUCP           Starts the UUCP delivery agent.  3           SITE           Starts the SITE interface.u  =           MLF            Starts the mailing list/file server.E  7           LSV            Starts the gateway to L-Soft's_A           _______________LISTSERV._______________________________i  L           __________________________________________________________________      11.2   Startup Data Files  =           MX___STARTUP.COM  uses two data files, both located8=           in the MX root directory (MX_DIR:). MX_LOGICALS.DAT >           contains logical name definitions, some of which can=           be customized or altered after MX is installed. MX_,?           STARTUP_INFO.DAT contains information on which of the >           MX components are installed, and on which nodes they           should be run.             11-2         A                                            The MX Startup Process           @           Do not edit these files directly. Use the MXCONFIG.COM=           procedure provided in the MX root directory to maked@           any changes to the standard MX logical names and agent           startup information.                                                                        A                                                              11-3  D  D              A           _______________________________________________________e              MCP Command Dictionary e  s    A                                                      MCP Commands A                                                               MCPy        A           _______________________________________________________n  
           MCP   *           Executes the MX Control Program.  A           _______________________________________________________              FORMAT             MCP  [command]  A           _______________________________________________________r)           Command Qualifiers     Defaultst  =           /[NO]FILE=file-spec    /FILE=MX_DIR:MX_CONFIG.MXCFGc  A           ________________________________________________________             PARAMETERS           [command] ?           Any MCP command except the input redirection operator,?           (@). The specified command is executed and control ise1           returned to DCL immediately thereafter.h  A           _______________________________________________________g             DESCRIPTIONe@           MCP was written to be used as a DCL "foreign" command.;           To use it as a foreign command, you must define an           symbol as follows:  0                            $ MCP :== $MX_EXE:MCP  ?           Defining the symbol in this way allows you to use thet@           /FILE qualifier and specify "one-shot" commands on the           command line.b  <           By default, MCP loads in the current configuration5           file, MX_DIR:MX_CONFIG.MXCFG, when started.a  A                                                             MCP-3o e  s               MCP Commands
           MCPg      A           _______________________________________________________              QUALIFIERS           /[NO]FILE=file-spec 7           Loads the specified MX configuration file forT>           editing. If not specified, MX_DIR:MX_CONFIG.MXCFG is<           loaded. The default file type is MXCFG. If /NOFILE:           is specified, MCP is started without loading any$           configuration information.                                                                           MCP-4e t       A                                                      MCP CommandsaB                                         @ (Redirect Command Input)        A           _______________________________________________________   $           @ (Redirect Command Input)  1           Executes MCP commands read from a file.   A           _______________________________________________________l             FORMAT             @  file-spec  A           _______________________________________________________              PARAMETERS           file-speca?           Name of the file containing MCP commands. If omitted,r'           the default file type is MCP.f  A           _______________________________________________________a             DESCRIPTION ;           Use this command to have MCP take further command,=           input from the specified file. There is no built-in =           limit on the number of levels of nesting of commandi@           files, so be careful when using input redirection from            within a command file.  :           This command can only be used at the MCP command<           prompt, not as a "one-shot" MCP command. To have a?           file be used for input for an entire MCP session, use 1           the following sequence of DCL commands.M  <                            $ DEFINE/USER SYS$INPUT file-spec                             $ MCP          A                                                             MCP-5S .                  MCP Commands           ATTACH        A           _______________________________________________________              ATTACH  =           Transfers control to another process in the currentR           process tree.R  A           _______________________________________________________X             FORMAT              ATTACH  [process-name]  A           _______________________________________________________P)           Command Qualifiers     DefaultsC  $           /IDENTIFICATION=process-id           /PARENT   A           _______________________________________________________              PARAMETERS           process-name:           Name of the process to which the terminal should9           be attached. The process must be in the current ?           process tree. This parameter is omitted if one of the "           qualifiers is specified.  A           _______________________________________________________              DESCRIPTIONg?           This command is similar to the DCL ATTACH command. Itp?           is used in interactive jobs to attach the terminal toM=           another process in the current process tree for theO           job.  A           _______________________________________________________              QUALIFIERS$           /IDENTIFICATION=process-id@           Specifies the process by its process identification, a           hexadecimal number.              MCP-6e t  h    A                                                      MCP Commands A                                                            ATTACH                    /PARENTz?           Specifies that the terminal should be attached to then>           current subprocess's immediate parent in the process           tree.n                                                                        A                                                             MCP-7F                    MCP Commands           DEFINE/KEY        A           _______________________________________________________o             DEFINE/KEY  ?           Defines an equivalence string and a set of attributesT.           with a key on the terminal keyboard.  A           _______________________________________________________u             FORMAT  1           DEFINE/KEY  key-name equivalence-stringt  A           _______________________________________________________T)           Command Qualifiers     Defaults              /ECHO            /ERASE           /IF_STATE            /LOCK_STATET           /LOG           /SET_STATE           /TERMINATE  A           _______________________________________________________              DESCRIPTIONn8           See the DCL help entry for DEFINE/KEY for more&           information on this command.  >           You can have a set of keys defined automatically for<           use with MCP by placing DEFINE/KEY commands in the>           file SYS$LOGIN:MX_MCP_KEYDEFS.INI. Note that this is=           the same file that is used with the REJMAN program.                        MCP-8a    s    A                                                      MCP CommandsnA                                                      DEFINE ALIASc        A           _______________________________________________________              DEFINE ALIAS  @           Defines a local alias for transparent mail forwarding.  A           ________________________________________________________             FORMAT  4           DEFINE ALIAS  local-name fwd-address[,...]  A           _______________________________________________________i             PARAMETERS           local-name<           A string up to 32 characters in length. Any E-mail?           addressed to this name on the local host will be sentc$           to the forwarding address.             fwd-address ?           A valid E-mail address, which will be substituted for >           the matching local alias address. Multiple addresses=           may be given; use commas to separate the addresses. ?           The maximum character length for all addresses is 255m'           characters, including commas.   A           _______________________________________________________t             DESCRIPTIONr;           An alias can be used to cause mail messages to beg<           forwarded automatically to another address. Unlike9           forwarding using the SET FORWARD command in VMS =           Mail, no "Resent" headers are added to the message. =           In addition, alias-based forwarding is performed by =           the MX routing agent rather than the local delivery :           agent, thus affording a small savings in message=           queue space and processing time. Due to the lack of ?           notification, however, it is recommended that aliases            be used sparingly.  A                                                             MCP-9                     MCP Commands           DEFINE FILE_SERVER        A           ________________________________________________________             DEFINE FILE_SERVER              Creates a file server.  A           _______________________________________________________              FORMAT  "           DEFINE FILE_SERVER  name  A           _______________________________________________________ )           Command Qualifiers     Defaults   "           /BEGIN_SEND_PERIOD=hh:mm#           /[NO]DELAY_THRESHOLD=sizee/           /[NO]DESCRIPTION=text  /NODESCRIPTION             /END_SEND_PERIOD=hh:mm!           /[NO]HOST_LIMIT=hostlimX$           /[NO]MAILING_LIST=listname           /MANAGER=address           /ROOT=rootspec#           /[NO]SERVER_LIMIT=servlim !           /[NO]USER_LIMIT=userlim   A           _______________________________________________________              PARAMETERS           name=           Local name to be used for the file server, up to 32            characters in length.   A           _______________________________________________________              DESCRIPTIONB;           This command is used to establish or remove an MX @           mail-based file server on the local system. The server<           can be set up to distribute groups of files called=           "packages" using E-mail as the distribution medium. >           The file server responds to commands placed, one per>           line, in the text of a mail message sent to the file             MCP-10 u       A                                                      MCP Commands A                                                DEFINE FILE_SERVERM        @           server username. The commands the file server responds7           to are HELP, LIST, SENDME, QUIT, and ADDRESS.   ;           The root you specify with /ROOT qualifier is used >           by the file server software to locate packages. Each<           package must have a directory [package-name] under>           that root where all its files are kept. In addition,@           the file name of each of the files in the package must=           also match the package name. Each package must alsoX<           have a file called package-name.DESCRIPTION in the>           top-level root directory that contains a description6           of the package and the files in the package.  =           The .DESCRIPTION files may be placed in the package >           subdirectories, if desired, but they cannot exist in/           both the root and the subdirectories.   >           The SENDME command takes one argument, the name of a=           package or an individual file. If a package name is @           specified, all files in the package directory are sent?           to the requesting user. Otherwise, just the specifiedM           file is sent.   9           The LIST command can take a wildcard pattern asT;           an argument (if omitted, it defaults to "*"). The ;           contents of the description files of all packagesX@           whose names match the wildcard pattern are placed in a/           file and sent to the requesting user.   9           The HELP command causes the file server to sendP<           the file FILESERV_HELP.TXT from the top-level root>           directory to the requesting user. A sample help file;           is provided with MX, which the system manager can 6           modify to provide site-specific information.  ;           The QUIT command causes the file server to ignore ?           any remaining lines in the message. It can be used to ?           prevent the unintentional parsing of mail signatures.P  <           The ADDRESS command takes a valid RFC822-compliant:           address. It causes all file server replies to be?           redirected to the given address instead of the Reply-            To or From addresses.   A                                                            MCP-11_ _                  MCP Commands           DEFINE FILE_SERVER      A           _______________________________________________________X             QUALIFIERS"           /BEGIN_SEND_PERIOD=hh:mm=           Identifies the time of day when the file server cano=           begin sending files that exceed the delay thresholde"           size. Defaults to 17:00.  #           /[NO]DELAY_THRESHOLD=sizel=           Use /DELAY_THRESHOLD to establish the maximum size,e?           in bytes, a file can be to be sent at any time during <           the day. Files exceeding size are sent only during>           the sending period established by /BEGIN_SEND_PERIOD@           and /END_SEND_PERIOD. Use /NODELAY_THRESHOLD to remove           size restrictions.             /[NO]DESCRIPTION=text,<           This qualifier defines a brief description for the<           file server. This description is added to the file?           server address in the X-FileServer header on outgoingo           server messages.              /END_SEND_PERIOD=hh:mm@           Identifies the time of day when the file server should<           stop sending files that exceed the delay threshold"           size. Defaults to 09:00.  !           /[NO]HOST_LIMIT=hostlim_?           Specifies that a maximum of hostlim bytes may be sents%           per day to any single host.   %           /[NO]MAILING_LIST=list-namei;           Specifies a mailing list to be linked to the filea<           server. Only those users who are subscribed to the@           specified list may have access to the file server. The@           specified list must exist on the local system in order0           for this qualifier to have any effect.             /MANAGER=address@           When establishing a file server, you can provide an E-@           mail address to which all error messages and mail that?           bounces back to the file server can be forwarded. The_             MCP-12    S    A                                                      MCP Commands)A                                                DEFINE FILE_SERVER         >           local alias name-Mgr will be created to direct those=           error messages to the /MANAGER address. If you omit ?           the /MANAGER qualifier, bounced mail will be directed            to the Postmaster.             /ROOT=rootspec>           You must specify a location (either a rooted logical;           or a device plus root directory specification) to ;           be used as the root for the file server files andt<           directories. Examples of valid roots are FILESERV_:           ROOT: (if it is defined as a rooted logical) and<           DISK:[FILE_SERVER.] (note the final dot before the:           bracket, indicating it is a root specification).  #           /[NO]SERVER_LIMIT=servlim_?           Specifies that a maximum of servlim bytes may be sent_"           per day from the server.  !           /[NO]USER_LIMIT=userlim ?           Specifies that a maximum of userlim bytes may be sent "           per day to any one user.                                      A                                                            MCP-13i c                  MCP Commands'           DEFINE INSIDE_NETWORK_ADDRESS         A           _______________________________________________________m  '           DEFINE INSIDE_NETWORK_ADDRESSh  <           Defines an "inside" network address for SMTP relay           determination.  A           _______________________________________________________              FORMAT  3           DEFINE INSIDE_NETWORK_ADDRESS  ip-address   A           _______________________________________________________ )           Command Qualifiers     Defaultsu  9           /NETMASK=ip-netmask    /NETMASK=255.255.255.255 *           /[NO]REJECT            /NOREJECT1           /[NO]RELAY_ALLOWED     /NORELAY_ALLOWEDD  A           ________________________________________________________             PARAMETERS           ip-address>           IP address of the network or host to be added to the>           list, in dotted-decimal form. The address is assumed;           to be for a host unless the /NETMASK qualifier is_           specified.  A           _______________________________________________________t             DESCRIPTION @           This command establishes an IP address or network that=           is in one of the local domains, is permitted to use_@           your SMTP server as a relay, or to reject a particular?           host or network from being considered as part of yourM           local domain.   ?           Inside network address definitions are only used with <           the SMTP server is set to disallow relays with SET@           SMTP/NORELAY_ALLOWED. When at least one inside address=           is defined, messages coming in via SMTP are allowedu@           to have recipients outside of the local domain(s) only             MCP-14 _  _    A                                                      MCP Commands A                                     DEFINE INSIDE_NETWORK_ADDRESSc        =           if the sending system's IP address is on the inside            network address list.M  9           By default, the SMTP server will still reject a @           message that contains non-local addresses for both the@           sender and the receiver, even from hosts on the inside=           network address list. You can ease that restrictionF,           with the /RELAY_ALLOWED qualifier.  A           _______________________________________________________              QUALIFIERS           /NETMASK=ip-netmask_9           Specifies the network mask to be applied to the 9           address, in dotted-decimal form. The default isd>           255.255.255.255, which indicates that the IP address'           is for a host, not a network.s             /[NO]REJECTe<           Indicates whether relay is to be rejected from the:           specified host or network. This qualifier can be<           used to reject SMTP relay from particular hosts or=           subnetworks that are below a parent network that is 5           already on the inside network address list.              /[NO]RELAY_ALLOWED;           Indicates that the host(s) should be allowed full_;           relay permission; that is, messages sent from thed@           host(s) are allowed to contain non-local addresses for#           both sender and receiver._  @           This qualifier is useful when your system is acting as?           a central mail hub, and there are hosts on your local_?           network that automatically forward messages for theire@           local users to hosts outside your domain via an alias.=           When such messages are sent back to your system (as_>           the mail hub), they will contain non-local addresses0           for both the sender and the recipient.    A                                                            MCP-15e    b               MCP Commands           DEFINE LISTf        A           _______________________________________________________e             DEFINE LISTh  !           Creates a mailing list.c  A           _______________________________________________________a             FORMAT              DEFINE LIST  list-name  A           _______________________________________________________ .           Command Qualifiers          Defaults  4           /[NO]ADD_MESSAGE=fspec      /NOADD_MESSAGE0           /[NO]ARCHIVE=fspec          /NOARCHIVE5           /[NO]CASE_SENSITIVE         /CASE_SENSITIVE 7           /[NO]CC_POST_ERRORS         /NOCC_POST_ERRORS 4           /[NO]DESCRIPTION=text       /NODESCRIPTION/           /[NO]DIGEST                 /NODIGESTf.           /ERRORS_TO=address          See text8           /[NO]FORWARD_MESSAGE=fspec  /NOFORWARD_MESSAGE5           /[NO]HIDE_ERRORS_TO         /HIDE_ERRORS_TOT5           /[NO]LIST_HEADERS=(keyword[,/NOLIST_HEADERS_2           /[NO]MODERATOR=(address[,.../NOMODERATOR            /OWNER=(address[,...])0           /PRIVATE                    /NOPRIVATE.           /PROTECTION=prot-spec       See text@           /[NO]RECIPIENT_MAXIMUM={DEFA/RECIPIENT_MAXIMUM=DEFAULT7           /[NO]REMOVE_MESSAGE=fspec   /NOREMOVE_MESSAGEw6           /REPLY_TO=(kwd[,...])       /REPLY_TO=SENDER.           /[NO]RETURN_ADDRESS=addressSee  text7           /SETTINGS=(kwd[,...])       /SETTINGS=DEFAULT .           /STRIP_HEADERS=keyword      See text7           /SUBJECT_PREFIX=string      /NOSUBJECT_PREFIX 1           /XHEADERS=(string[,...])    /NOXHEADERSo                 MCP-16 p       A                                                      MCP Commands A                                                       DEFINE LISTo      A           _______________________________________________________              PARAMETERS           list-nameT>           Local name to be used for the mailing list, up to 32           characters in length.e  A           _______________________________________________________              DESCRIPTION @           This command is used to establish a mailing list. When<           a message is sent to the mailing list address, the?           mailing list processor forwards a copy of the messageu;           to all the addresses on the list. In addition, it >           can place a copy of the message in a file, called an           archive.  ?           Mailing lists are fully described in Message Exchange )           Mailing List/File Server Guide.E  A           ________________________________________________________             QUALIFIERS            /[NO]ADD_MESSAGE=fspec6           Specifies the name of a file to be sent to a7           user subscribing to the list. If omitted, the_<           device and directory default to MX_MLIST_DIR: (MX_?           ROOT:[MLF.MAILING_LISTS]), and the file type defaults            to TXT._  ;           The default for this qualifier is /NOADD_MESSAGE,m8           which causes the global add message, MX_MLIST_;           DIR:MLIST_ADD_MESSAGE.TXT, to be sent when a user >           subscribes to the list. See Message Exchange Mailing;           List/File Server Guide for more information about             notification messages.             /[NO]ARCHIVE=fspec<           Specify /ARCHIVE to have the mailing list messages@           placed in an archive file automatically by the mailing=           list processor. For fspec you must provide at least <           a device/directory specification. If the file name:           is omitted, the mailing list name is used as the  A                                                            MCP-17                     MCP Commands           DEFINE LIST         :           file name for the archive file. If the file type=           is omitted, yyyy-mm is used as the file type, where >           yyyy is the current year and mm is the number of the=           current month at the time a message is added to the_           archive.             /[NO]CASE_SENSITIVE =           This qualifier enables or disables case-sensitivity_>           with regard to mailing list subscribers. By default,>           MX treats the left-hand side of subscriber addresses?           in a case-sensitive manner with regard to SIGNOFF ande?           SET commands. If a list is defined /NOCASE_SENSITIVE,r@           then the case of subscriber addresses will be ignored.             /[NO]CC_POST_ERRORS <           This qualifier enables or disables copying mailing:           post failure messages to the /ERRORS_TO address.;           By default, if a message cannot be forwarded to ai>           list, an error message is sent back to the sender of=           the message. If /CC_POST_ERRORS is set, those error ;           messages are also sent to the /ERRORS_TO address.l;           This lets the list owner see attempted posts fromr5           non-subscribers and other posting failures.R             /[NO]DESCRIPTION=textl8           This qualifier defines a brief description for<           the mailing list. This description is added to the?           mailing list address in the X-ListName header on list            messages.n             /[NO]DIGESTa>           This qualifier enable or disables digest support for@           the list. A list marked /DIGEST can support the DIGEST?           flag for subscribers. Mail sent to the "-digest" form =           of the list address will be forwarded only to those 3           subscribers marked as digest subscribers.                    MCP-18 _  _    A                                                      MCP Commands A                                                       DEFINE LIST_                   /ERRORS_TO=address=           This qualifier is used to direct error messages and_<           mail returned to the mailing list processor to the=           specified address. If not specified, the address ofD>           the the first specified owner of the mailing list is           used.O  $           /[NO]FORWARD_MESSAGE=fspec;           Specifies the name of a file to be sent to a userI=           subscribing to the list when the list does not have=<           W:E access set. The message should notify the user<           that the subscription request was forwarded to the:           list owner. If omitted, the device and directory9           default to MX_MLIST_DIR: (MX_ROOT:[MLF.MAILING_e5           LISTS]), and the file type defaults to TXT.   ?           The default for this qualifier is /NOFORWARD_MESSAGE, ?           which causes the global forward-to-owner message, MX_r@           MLIST_DIR:MLIST_FORWARD_MESSAGE.TXT, to be sent when a?           user tries to subscribe. See Message Exchange Mailingi;           List/File Server Guide for more information aboutt            notification messages.             /[NO]HIDE_ERRORS_TO,=           Controls how the mailing list processor formats the =           envelope FROM address and Errors-To: header. When a @           list is set /HIDE_ERRORS_TO (the default), the address?           specified with the /ERRORS_TO qualifier (or the first <           /OWNER address, if /ERRORS_TO is not specified) is=           replaced automatically in outbound list postings by =           the alias "owner-listname". Setting /NOHIDE_ERRORS_y<           TO prevents this substitution, using the errors-to           address explicitly.p  3           /[NO]LIST_HEADERS=(keyword[=value][,...])i>           The /LIST_HEADERS qualifier instructs MLF to include@           or omit special X-List-* headers that provide URLs for?           subscribing to a list, unsubscribing from a list, andn%           getting help for that list.e  A                                                            MCP-19a a  t               MCP Commands           DEFINE LISTI        4           There are three valid keywords: SUBSCRIBE,=           UNSUBSCRIBE, and HELP. All three accept values thato?           are used in the creation of the actual headers, whicho=           will be added to each message posted to the mailingf;           list. However, only HELP requires a value. If the =           value is omitted for SUBSCRIBE and UNSUBSCRIBE, ther=           proper URLs for those actions will be automatically            generated by MLF.t  >           The List-* headers are currently a proposed Internet<           standard. The actual headers generated are X-List-9           Subscribe, X-List-Unsubscribe, and X-List-Help.d  ;           Clients that support these headers (both X-List-*q?           and List-*) will provide click buttons to perform thee4           specified actions (usually "mailto" URLs).  =           See Message Exchange Mailing List/File Server Guide 7           for more information on mailing list headers.e  (           /[NO]MODERATOR=(address[,...])=           This qualifier is for future use. Moderated mailingc,           lists are currently not supported.              /OWNER=(address[,...]):           This qualifier specifies the addresses of one or<           more owners of the mailing list. Each mailing list:           must have at least one owner, who is responsible8           for handling subscription requests not handled9           automatically by the mailing list processor ande4           problems with or questions about the list.             /[NO]PRIVATE;           This qualifier specifies that the list is privateR>           and should not be displayed in response to DIRECTORY>           commands sent to the MXserver or -Request addresses.@           The list protection is not affected by this qualifier.             /PROTECTION=prot-spec 9           This qualifier determines the protection of thet@           mailing list. The protection specification, prot-spec,>           is identical to a VMS file protection specification,             MCP-20    t    A                                                      MCP CommandsoA                                                       DEFINE LIST_        ;           and defaults to (S:RWED,O:RWED,G:RWED,W:RWE). Theo>           four protection classes are described in Table MCP-18           and the four protection types are described in           Table MCP-2.  A           Table_MCP-1__Mailing_list_protection_classes___________e  A           Class______Description_________________________________.  >           SYSTEM     any address matching one of the addresses@                      on the system user list (see DEFINE SYSTEM_                      USERS)o  :           OWNER      any address matching one of the owner@                      addresses specified on the /OWNER qualifier  >           GROUP      any address matching one the addresses on=                      the subscriber list for the mailing listi  A           WORLD______any_other_address___________________________a  ;           Just as with VMS file protections, the SYSTEM andt:           OWNER classes are implicitly granted C (control)9           access, allowing them to use the ADD and REMOVEt?           commands to add and remove addresses from the mailinge           list.e  A           Table_MCP-2__Mailing_list_protection_codes_____________r  A           Code_______Description_________________________________   9           R (Read)   allows the use of the REVIEW command   A           W          allows the user to post messages to the list            (Write)   9           E          allows the automatic handling of thea&           (Enroll)   SUBSCRIBE command  A           D          allows the automatic handling of the SIGNOFFiA           (Delete)___command_____________________________________   6           Note that protection code E (enroll) is only<           meaningful when used with the WORLD class and that  A                                                            MCP-21     e               MCP Commands           DEFINE LIST         <           protection code D (delete) is only meaningful when$           used with the GROUP class.  @           Some typical GROUP and WORLD protection specifications<           are shown in Table MCP-3. In most cases, you would7           also want to give SYSTEM and OWNER users RWEDc           access.m  A           Table_MCP-3__Typical_protection_codes__________________   @           (G:RWED,W:RWE) Public list. Anyone can subscribe, sign=                          off, and review the list; anyone canu*                          post to the list.  ?           (G:RWED,W:E)   Semi-public list. Anyone can subscribe 8                          and sign off the list, but only>                          subscribers can review or post to the                          list.  ;           (G:W,W)        Private list. Only subscribers can ?                          post to the list, and all subscriptiono?                          requests are screened by the owners of_*                          the mailing list.  ?           (G,W)          One-way list. Only the owners can post_>                          to the list, and they also screen allA           _______________the_subscription_requests.______________5  <           Note: Since electronic mail can readily be forged,=           you should not depend on this protection scheme for_>           absolute security of your mailing lists. The mailing@           list processor attempts no authentication of addresses$           when it receives messages.  ,           /[NO]RECIPIENT_MAXIMUM={DEFAULT|n}:           Specifies the maximum number of recipients to be;           entered per outbound mailing list message for the_>           list being defined. The default setting, /RECIPIENT_?           MAXIMUM=DEFAULT, causes this setting to be taken from ;           the SET MLF/RECIPIENT_MAXIMUM setting. Specifyingt7           /NORECIPIENT_MAXIMUM causes a single outboundc;           message to be created for each list posting, withe             MCP-22         A                                                      MCP CommandslA                                                       DEFINE LISTi        ?           all recipients listed. You may also specify a postive 8           integer for n, which instructs MLF to enter no<           more than n recipients in a single message. If the=           mailing list has more than n subscribers, each list ?           posting will cause multiple, duplicate messages to be 9           generated, each with no more than n recipients.   #           /[NO]REMOVE_MESSAGE=fspecs;           Specifies the name of a file to be sent to a user 6           signing off the list. If omitted, the device5           and directory default to MX_MLIST_DIR: (MX_o?           ROOT:[MLF.MAILING_LISTS]), and the file type defaults            to TXT.e  >           The default for this qualifier is /NOREMOVE_MESSAGE,;           which causes the global remove message, MX_MLIST__>           DIR:MLIST_REMOVE_MESSAGE.TXT, to be sent when a user:           signs off the list. See Message Exchange Mailing;           List/File Server Guide for more information aboutd            notification messages.             /REPLY_TO=(kwd[,...])t@           Specifies how the mailing list processor should handle?           Reply-To headers. Available reply-to types are SENDER 9           and LIST, which may be combined. The default isT;           SENDER, which prevents the mailing list processorm;           from modifying the headers. If LIST is specified,p<           a Reply-To header is added to list messages to re-=           direct replies to the mailing list, eliminating anyi>           existing Reply-To header in the original message. If?           LIST and SENDER are both specified, a Reply-To headerr:           containing both the mailing list address and the=           original Reply-To address is added to list messagese?           (using the From address if no Reply-To header existedr#           in the original message).   >           The /RETURN_ADDRESS=address qualifier can be used to>           supply an alternate list return address when /REPLY_           TO=LIST is specified.k  A                                                            MCP-23l l  d               MCP Commands           DEFINE LISTi        %           /[NO]RETURN_ADDRESS=address @           This qualifier is used to specify an alternate address<           to be used as the "Reply-To:" address when /REPLY_=           TO=LIST is specified. This qualifier is most useful 9           when multiple lists should have a common return_:           address. For example, it can be used to redirect<           replies to a "-Digest" list back to the non-digest           address.  #           /SETTINGS=(keyword[,...]) 9           The /SETTINGS qualifier is used to override theD;           default subscriber settings for a list. The validp>           keywords are MAIL, REPRO, CONCEAL, DIGEST, POST, and           their "NO" forms.O  :           A special keyword, DEFAULT, can be used to reset=           the settings to the MLF default for a mailing list. :           The default settings for a list are MAIL, REPRO,(           NOCONCEAL, NODIGEST, and POST.              /STRIP_HEADERS=keyword@           This qualifier is used to strip certain RFC822 headers1           from messages posted to a mailing list.M  /           The following keywords are supported:R  $           o  RECEIVED and NORECEIVED             o  OTHER and NOOTHER  >           When /STRIP_HEADERS=RECEIVED is set, the "Received:"?           headers are stripped from the incoming message beforeE;           it is mailed out to the list subscribers, thereby.=           reducing the total number of "Received:" headers ins=           the final message. This is especially beneficial toA@           BITNET hosts because there can be a substantial number=           of "Received:" headers added to a message that mustR<           pass through one or more Internet/BITNET gateways.               MCP-24         A                                                      MCP Commands A                                                       DEFINE LIST_        ?           When /STRIP_HEADERS=OTHER is set, all "other" headers :           are stripped from posts. The "other" headers are:           any headers not recognized by MX, which includes=           such headers as X- headers, return-receipt headers,_7           X.400 headers, etc. Setting a list to /STRIP_s>           HEADERS=OTHER handily gets around potential problems>           with subscribers using the DOS package Pegasus Mail,:           which will send message receipt messages back to<           a list. Note that this may not be a viable setting>           for a mailing list that is gatewayed to a newsgroup,?           depending on the gateway software, since headers used (           by the gateway may be omitted.  =           See Message Exchange Mailing List/File Server Guide_7           for more information on mailing list headers.f  &           /[NO]SUBJECT_PREFIX="string"<           The /SUBJECT_PREFIX qualifier can be used to add a>           prefix to the Subject line of messages posted to the@           list. By default, no prefix is added. When the list is>           set to /REPLY_TO=(SENDER), a short prefix string may@           be supplied to help subscribers recognize mailing list;           messages. The given string is bracketed by square,;           brackets ([])  when it is prefixed to the subjecte<           lines. The maximum length for the prefix string is?           32 characters. Prefix strings should be kept short to 8           avoid generating extremely long subject lines.  (           /[NO]XHEADERS=("string"[,...])?           The /XHEADERS qualifier can be used to add additionali:           site-specific headers to mailing list posts. For?           example, you can use /XHEADERS to add additional non-s?           standard "X-List-" headers such as "X-List-Archives". >           The format of the header string is: "Keyword: text".:           For example, "Precedence: Bulk", which is a non-/           standard header used by some mailers.         A                                                            MCP-25     y               MCP Commands           DEFINE LIST         =           Extreme care should be taken when adding additional ;           headers to mailing lists to ensure that duplicatea=           headers or improperly formatted headers (those thatg<           don't comply with RFC 822) aren't added to mailing           list posts.o  =           See Message Exchange Mailing List/File Server Guide 7           for more information on mailing list headers.                                                                            MCP-26 b  g    A                                                      MCP CommandslA                                               DEFINE LOCAL_DOMAINt        A           _______________________________________________________d             DEFINE LOCAL_DOMAINr  >           Defines a host name or wildcard pattern as a "local"%           domain for the SMTP server.   A           _______________________________________________________              FORMAT  .           DEFINE LOCAL_DOMAIN  name-or-pattern  A           _______________________________________________________x             PARAMETERS           name-or-patternp?           A host name or a string containing VMS-style wildcardo>           characters against which an SMTP host name should be           matched.  A           _______________________________________________________r             DESCRIPTIONf;           This command is used in conjunction with the SMTP =           server's /NORELAY setting to establish domains thats>           the SMTP server considers local, to prevent messages;           to or from these domains from being refused. When =           relaying in the SMTP server is disabled, it refuses :           to deliver messages to remote mailboxes when the=           originating mailbox is also remote. By default, the @           SMTP server considers any mailbox resolving to a LOCAL;           path, or with a host name sharing the same parentg<           domain as the MX host name or TCP/IP host name, as<           being local. If your system is acting as a gateway:           for hosts in other domains, and you disable SMTP<           relaying, you should list the names of those other<           hosts, or a wildcard pattern that will match those<           names, in a DEFINE LOCAL_DOMAIN command, to ensure@           that messages coming from or going to those hosts will           not be refused.   A                                                            MCP-27a    M               MCP Commands           DEFINE LOCAL_DOMAINd        9           You may specify multiple local domains by usingq>           multiple DEFINE LOCAL_DOMAIN commands. Only one name>           or wildcard pattern is accepted per command. Use the@           REMOVE LOCAL_DOMAIN command to delete domains from the           local-domain list.                                                                                 MCP-28 n  s    A                                                      MCP CommandsiA                                                       DEFINE PATHn        A           _______________________________________________________f             DEFINE PATH   7           Defines a mapping between a domain name and a            distribution path.  A           _______________________________________________________u             FORMAT  ,           DEFINE PATH  domain-name path-name  A           _______________________________________________________t)           Command Qualifiers     Defaultsp             /ROUTE=host-name  A           _______________________________________________________t             PARAMETERS           domain-name <           A domain name or pattern containing VMS wildcards.             path-nameg@           One of the supported MX path names: LOCAL, SMTP, JNET,@           SITE, DECNET_SMTP, X25_SMTP, UUCP, or HOLDING_QUEUE=n.  A           _______________________________________________________              DESCRIPTIONi=           This command is used to associate a domain name andr?           a distribution path. The Router uses this information =           to determine which distribution path should be used >           when routing mail messages. Each DEFINE PATH command9           adds a path definition to the list. The list isI>           automatically sorted based on the length of the path<           and the presence of wildcards. The Router searches>           this list until the domain name of the address it is@           trying to route to matches the domain name or wildcard)           pattern of the path definition.-  A                                                            MCP-29q                    MCP Commands           DEFINE PATHr      A           _______________________________________________________              QUALIFIERS           /ROUTE=host-name?           Specifies the name of a host that will route messages >           for the specified domain. For SMTP and HOLDING_QUEUE;           paths, this host name must directly resolve to anr<           IP address; it cannot be the name that has only MX0           information in the Domain Name System.                                                                           MCP-30 v  t    A                                                      MCP CommandsoA                                               DEFINE REWRITE_RULE         A           _______________________________________________________              DEFINE REWRITE_RULEs  :           Defines an address-rewriting rule for use by the           Router.a  A           _______________________________________________________              FORMAT  -           DEFINE REWRITE_RULE  pattern result   A           _______________________________________________________s             PARAMETERS           patternt<           An RFC 821-compliant address string, possibly with?           the addition of one or more substitution strings. Theo=           address string must include the opening and closing >           angle brackets. Any address matching pattern will be=           rewritten by the Router based on the result string.n             result@           An RFC 821-compliant address string, possibly with the7           addition of one or more substitution strings.t  A           ________________________________________________________             DESCRIPTIONc?           This command is used to provide the Router with rules_;           for transforming some addresses into other forms.e>           The pattern string is an address string that must be@           matched to have the transformation apply. For example:  \                            MCP> DEFINE REWRITE_RULE "<{user}@{host}.DECnet.mycompany.com>" -`                            _MCP>                     "<""{host}::{user}""@myhost.mycompany.org>"  6           The strings "{user}" and "{host}" are called:           substitution strings. They are identified by the9           curly braces surrounding the substitution name,n;           which you may specify arbitrarily. In the patterna=           string, a substitution string matches any number ofD  A                                                            MCP-31  l  e               MCP Commands           DEFINE REWRITE_RULEr        =           any characters, like the asterisk in a VMS wildcard_8           pattern. The matched string can be substituted;           into the rewritten address by specifying the same @           substitution string in the result string, or it may be           omitted.  @           Rewriting rules can be used when the DEFINE PATH/ROUTE<           command is inadequate, such as when a message must9           pass through two or more gateways to get to its_;           destination, or when the rewrite affects both the <           local-part and the domain-part of an address. They@           should be used sparingly, however, since every address9           must be matched against the rewrite rules list.   =           The rewrite rules list is searched in the order yout:           specify, so you should place more specific rules<           before more general rules. All pattern matching is"           done from right to left.                                                       MCP-32    T    A                                                      MCP CommandsTA                                               DEFINE SYSTEM_USERSW        A           _______________________________________________________n             DEFINE SYSTEM_USERS   :           Defines the address to be given SYSTEM access to           mailing lists.  A           _______________________________________________________              FORMAT  ,           DEFINE SYSTEM_USERS  address[,...]  A           _______________________________________________________a             PARAMETERS           address[,...] :           One or more addresses, separated by commas. Each9           of the users identified by these addresses will :           be considered "system" users by the mailing list6           processor, and granted access via the SYSTEM8           protection class to all mailing lists. Case is@           important only in the username portion of the address.=           To retain the case of the address, surround it with            quotation marks.  A           _______________________________________________________              DESCRIPTIONg:           This command is used to provide the mailing list@           processor with a list of privileged users. These users<           are granted access to mailing lists via the SYSTEM@           protection class, and are also given CONTROL access to>           all mailing lists. They receive all messages sent to>           MXserver that cannot be handled automatically by the!           mailing list processor.h  >           The first address on the SYSTEM_USER list is used as@           the return address for generic MXserver replies (those>           replies that are not about a specific mailing list).>           For this reason, you may want to specify an alias as            the first system user.  A                                                            MCP-33i n  l               MCP Commands           DEFINE SYSTEM_USERSo        =           Typically only the system manager and/or postmasteri>           for the system should be identified as system users.;           This will allow them to control a mailing list oni:           the system when the owners of the list cannot be           contacted.                                                                                 MCP-34    s    A                                                      MCP Commands A                                                              EXITO        A           _______________________________________________________              EXIT             Exits MCP.  A           _______________________________________________________e             FORMAT             EXIT  A           _______________________________________________________              DESCRIPTIONi=           Use this command to leave MCP. If you have modifiedd>           the MX configuration, it is saved before exiting. If<           the configuration file has not been named, you are2           prompted for a file name before exiting.                                          A                                                            MCP-35  v  s               MCP Commands           HELP        A           _______________________________________________________              HELP  $           Displays help information.  A           _______________________________________________________e             FORMAT             HELP  [topic...]  A           _______________________________________________________g             PARAMETERS           topic @           The name of a topic in the help library. If omitted, a&           list of topics is displayed.                                                       MCP-36         A                                                      MCP CommandsyA                                                            MODIFYs        A           _______________________________________________________M             MODIFY  6           Modifies existing configuration information.  A           _______________________________________________________d             FORMAT5                   { ALIAS alias new-fwdaddr         }d5                   { FILE_SERVER fsrv-name           }s5           MODIFY  { LIST list-name                  }t5                   { PATH domain new-path            }e5                   {                                 }o5                   { REWRITE_RULE pattern new-result }r  A           _______________________________________________________              DESCRIPTIONr:           This command alters configuration information of7           the types listed in above. Each of the MODIFYD=           commands takes the same arguments and qualifiers asp;           its corresponding DEFINE command, so refer to thee=           appropriate DEFINE command for further information.e                                A                                                            MCP-37S P  A               MCP Commands           QUEUE CANCEL        A           _______________________________________________________t             QUEUE CANCEL              Cancels a queue entry.  A           _______________________________________________________              FORMAT  *           QUEUE CANCEL  entry-number[,...]  A           _______________________________________________________ )           Command Qualifiers     Defaultss  '           /[NO]LOG               /NOLOGm  A           _______________________________________________________e             PARAMETERS           entry-number@           Queue entry number to be cancelled. If the number of a>           base queue entry, all related agent-specific entries!           will also be cancelled.y  A           _______________________________________________________              DESCRIPTIONC7           This command sets the status of the specified <           queue entries to CANCELLED, which prevents further@           processing of the entries. This should only be done on@           entries which are not currently being processed by the/           Router or one of the delivery agents.h  A           _______________________________________________________n             QUALIFIERS           /[NO]LOG=           Causes a message to be displayed for each cancelledi'           entry. The default is /NOLOG.              MCP-38 n  e    A                                                      MCP CommandstA                                                    QUEUE COMPRESSd        A           _______________________________________________________s             QUEUE COMPRESS  *           Compress the message queue file.  A           _______________________________________________________i             FORMAT             QUEUE COMPRESS  A           _______________________________________________________e)           Command Qualifiers     Defaultsj  %           /MAXIMUM_ENTRIES=valueNone. '           /[NO]LOG               /NOLOG   A           _______________________________________________________              DESCRIPTIONs?           Shrinks the message queue file by creating a new files?           and renumbering all the existing entries in the file.s>           This command may be used to create a smaller message<           queue, which affects the maximum number of entries           allowed in the queue.t  5           The /MAXIMUM_ENTRIES qualifier is required.j  :           This command requires exclusive access to the MX>           message queue file. Before compressing the file, all9           MX agents must either be shut down or inactive.   A           _______________________________________________________              QUALIFIERS,           /MAXIMUM_ENTRIES=number-of-entries=           Specifies the maximum number of queue entries to beo@           allowed. MX will not allow more entries to be added to>           the queue than the specified value. MCP QUEUE EXTEND@           can be used to increase the number of allowed entries.  :           The size of the queue file in blocks is equal to=           the maximum number of entries, plus 10 blocks, plusr1           whatever is added for the disk cluster.   A                                                            MCP-39o    p               MCP Commands           QUEUE COMPRESS                   /[NO]LOG7           Causes a status message to be displayed after 2           successful operation. Default is /NOLOG.                                                                                     MCP-40         A                                                      MCP Commands A                                                      QUEUE CREATE         A           _______________________________________________________              QUEUE CREATE  &           Create a message queue file.  A           _______________________________________________________              FORMAT             QUEUE CREATE  A           _______________________________________________________m)           Command Qualifiers     Defaults_  %           /MAXIMUM_ENTRIES=valueNone.   A           _______________________________________________________m             DESCRIPTIONV9           Creates a new, empty MX message queue file. TheM1           /MAXIMUM_ENTRIES qualifier is required.   A           Note: This command simply creates a new queue file; the ?           existing queue file is not automatically deleted. Anyi?           files for any existing queue entries are also left inm           place.  :           This command requires exclusive access to the MX>           message queue file. Before compressing the file, all9           MX agents must either be shut down or inactive.   A           _______________________________________________________r             QUALIFIERS,           /MAXIMUM_ENTRIES=number-of-entries=           Specifies the maximum number of queue entries to be @           allowed. MX will not allow more entries to be added to>           the queue than the specified value. MCP QUEUE EXTEND@           can be used to increase the number of allowed entries.  :           The size of the queue file in blocks is equal to=           the maximum number of entries, plus 10 blocks, plusd1           whatever is added for the disk cluster.   A                                                            MCP-41i f                  MCP Commands           QUEUE EXTEND        A           _______________________________________________________              QUEUE EXTEND  )           Extends the message queue file.   A           _______________________________________________________              FORMAT             QUEUE EXTEND  A           _______________________________________________________e)           Command Qualifiers     Defaults   %           /MAXIMUM_ENTRIES=valueNone.a  A           _______________________________________________________              DESCRIPTION ?           Extends the existing message queue file to allow more 7           entries to be in the queue at any given time.   5           The /MAXIMUM_ENTRIES qualifier is required._  :           This command requires exclusive access to the MX>           message queue file. Before compressing the file, all9           MX agents must either be shut down or inactive._  A           _______________________________________________________              QUALIFIERS,           /MAXIMUM_ENTRIES=number-of-entries=           Specifies the maximum number of queue entries to ben@           allowed. MX will not allow more entries to be added to>           the queue than the specified value. MCP QUEUE EXTEND@           can be used to increase the number of allowed entries.  :           The size of the queue file in blocks is equal to=           the maximum number of entries, plus 10 blocks, plusJ1           whatever is added for the disk cluster.o             MCP-42         A                                                      MCP Commands A                                                       QUEUE PURGEn        A           _______________________________________________________              QUEUE PURGEw  <           Purges the message queue of finished and cancelled           entries.  A           _______________________________________________________              FORMAT             QUEUE PURGEd  A           _______________________________________________________T)           Command Qualifiers     Defaultsi  '           /[NO]LOG               /NOLOG   A           _______________________________________________________              DESCRIPTIONi9           This command searches the message queue for all @           entries of FINISH or CANCELLED status and deletes them           from the queue.   A           _______________________________________________________              QUALIFIERS           /[NO]LOG;           Causes a message to be displayed for each deleted '           entry. The default is /NOLOG.                   A                                                            MCP-43                     MCP Commands           QUEUE READYX        A           _______________________________________________________              QUEUE READY               Readies a queue entry.  A           _______________________________________________________a             FORMAT  )           QUEUE READY  entry-number[,...]E  A           ________________________________________________________)           Command Qualifiers     DefaultsL  '           /[NO]LOG               /NOLOGg  A           ________________________________________________________             PARAMETERS           entry-number>           Queue entry number to be readied. If the number of a>           base queue entry, the base entry will be readied and@           all existing agent-specific entries will be cancelled.  A           _______________________________________________________o             DESCRIPTIONn=           This command sets the status of the specified queuen:           entries to READY and clears the delay flag. This@           should only be done on entries which are not currently>           being processed by the Router or one of the delivery           agents.,  A           _______________________________________________________r             QUALIFIERS           /[NO]LOG;           Causes a message to be displayed for each readied '           entry. The default is /NOLOG.h             MCP-44         A                                                      MCP CommandsaA                                                        QUEUE SHOWo        A           _______________________________________________________M             QUEUE SHOW  !           Displays queue entries."  A           _______________________________________________________{             FORMAT  (           QUEUE SHOW  [entry-number,...]  A           _______________________________________________________e)           Command Qualifiers     Defaultso             /ALL           /BEFORE=time           /BRIEF           /CREATED           /DATE            /DELAY"           /DESTINATION_AGENT=agent           /EXPIRE            /FULL            /IN_PROGRESS           /MODIFIED            /ORIGIN_AGENT=agent            /OUTPUT=file-spec            /SINCE=timer           /WAITING  A           _______________________________________________________e             PARAMETERS           entry-number=           Queue entry number to be displayed. If omitted, alle6           READY and IN-PROGRESS entries are displayed.      A                                                            MCP-45o n  s               MCP Commands           QUEUE SHOW      A           _______________________________________________________,             DESCRIPTIONc=           This command displays entries in the message queue.d  A           _______________________________________________________a             QUALIFIERS           /ALL>           Causes all queue entries to be displayed, regardless?           of status. If omitted, just the READY and IN-PROGRESSa            entries are displayed.             /BEFORE[=time]?           Selects only those entries dated before the specified ;           time. You can specify time as an absolute time, aT?           combination of absolute and delta times, or as one ofm?           the following keywords: TODAY (default), TOMORROW, orE<           YESTERDAY. Specify one of the following qualifiers9           with the /BEFORE qualifier to indicate the time :           attribute to be used as the basis for selection:<           /CREATED (default), /DELAY, /EXPIRE, or /MODIFIED.             /BRIEF<           Causes a brief listing of all the queue entries to=           be displayed, including those that have finished or_<           been cancelled. The information displayed is taken@           only from the MX queue file and includes the target MX!           process for each entry.t             /CREATED?           Modifies the time value specified with the /BEFORE ori>           the /SINCE qualifier. The /CREATED qualifier selects3           entries based on their dates of creation.              /DATE :           Causes the creation and modification dates to be)           displayed for each queue entry.w                 MCP-46 a  .    A                                                      MCP Commands A                                                        QUEUE SHOW                    /DELAY<           Modifies the time value specified with the /BEFORE?           or the /SINCE qualifier. The /DELAY qualifier selects -           entries based on their delay dates.a  "           /DESTINATION_AGENT=agent@           Selects only those entries that are to be or have been=           processed by the specified MX agent. Valid keywordss?           are: ROUTER, MLF, LOCAL, SMTP, SITE, LSV, JNET, UUCP,e?           DNSMTP, and XSMTP. This qualifier is most useful whent           used with /BRIEF.a             /EXPIREi?           Modifies the time value specified with the /BEFORE ori=           the /SINCE qualifier. The /EXPIRE qualifier selects 5           entries based on their dates of expiration.              /FULL <           Provides more details about the displayed entries,?           including intended recipients, error counts, and last >           error status messages. If omitted, a brief, one-line-           display is produced for each entry.t             /IN_PROGRESS;           Displays only entries marked as being in-progress            (INPROG).              /MODIFIED ?           Modifies the time value specified with the /BEFORE or ?           the /SINCE qualifier. The /MODIFIED qualifier selects 7           entries based on their dates of modification.              /ORIGIN_AGENT=agent_?           Selects only those entries that were entered into the >           queue by the specified MX agent. Valid keywords are:=           LOCAL, SMTP, JNET, UUCP, SITE, MAIL, DNSMTP, XSMTP,            and BSMTP.             /OUTPUT=file-spec_@           Directs the results to the specified file. If omitted,2           the results are displayed on SYS$OUTPUT.  A                                                            MCP-47g t                  MCP Commands           QUEUE SHOW                   /SINCE[=time].>           Selects only those entries dated after the specified9           time. You can specify time as an absolute time, :           a combination of absolute and delta times, or as9           one of the following keywords: TODAY (default), >           TOMORROW, or YESTERDAY. Specify one of the following>           qualifiers with the /SINCE qualifier to indicate the?           time attribute to be used as the basis for selection:_<           /CREATED (default), /DELAY, /EXPIRE, or /MODIFIED.             /WAITING=           Limits the display to only those entries with READYm           status.                                                                  MCP-48         A                                                      MCP Commands A                                                  QUEUE STATISTICS         A           ________________________________________________________             QUEUE STATISTICS  9           Displays statistical information concerning thet*           entries in the MX message queue.  A           _______________________________________________________              FORMAT             QUEUE STATISTICS  A           _______________________________________________________l             DESCRIPTION >           This command displays the total number of entries in?           the queue, the maximum number of entries possible for ?           the queue file, the percentage of entries in use, and_?           the largest entry number ever used during the life ofT           the file.c                                      A                                                            MCP-49     o               MCP Commands           QUEUE SYNCHRONIZE         A           _______________________________________________________t             QUEUE SYNCHRONIZEf  ?           Synchronizes the message queue bitmap with the actual            entries in the queue.   A           _______________________________________________________              FORMAT             QUEUE SYNCHRONIZE_  A           _______________________________________________________ )           Command Qualifiers     Defaults_             /LOG           /RESET  A           _______________________________________________________]             DESCRIPTION_;           This command updates the bitmap for the MX systemn9           message queue to synchronize it with the actual >           entries in the queue. The only time this command may@           be necessary is in the event of a system crash or disk           failure.  <           The command may be issued at any time; it does not@           require exclusive access to the MX message queue file.  A           ________________________________________________________             QUALIFIERS           /LOG7           Causes a status message to be displayed after 2           successful operation. Default is /NOLOG.             /RESET;           Resets the "Highest entry used" counter displayed =           by QUEUE STATISTICS. By default, the counter is not            reset.             MCP-50 n  h    A                                                      MCP Commands A                                                              QUITa        A           _______________________________________________________L             QUIT  >           Leaves MCP without saving any configuration changes.  A           _______________________________________________________              FORMAT             QUIT  A           _______________________________________________________              DESCRIPTION 7           Use this command leave MCP without saving any_9           of the changes made to the MX configuration. If 9           the configuration was changed, MCP will ask for_/           confirmation before returning to DCL.                                           A                                                            MCP-51     O               MCP Commands           REMOVE        A           _______________________________________________________h             REMOVE  )           Removes a configuration record.b  A           _______________________________________________________m             FORMAT7                   { ALIAS alias                       }x7                   { FILE_SERVER fileserv-name         } 7                   { INSIDE_NETWORK_ADDRESS ip-address } 7                   {                                   } 7           REMOVE  { LIST list-name                    }f7                   { LOCAL_DOMAIN name-or-pattern      } 7                   { PATH domain                       }_7                   {                                   } 7                   { REWRITE_RULE pattern              }h  A           _______________________________________________________n             DESCRIPTIONb?           This command removes one record of the specified typeU@           from the MX configuration. The specified alias, inside@           network address, list name, domain, rejection rule, or?           rewrite rule pattern must match exactly the identicalu,           field in the record to be removed.  @           When removing an inside network address, you must also@           specify the /NETMASK qualifier when the address is for'           a network rather than a host.                              MCP-52 a       A                                                      MCP Commands A                                                             RESET         A           _______________________________________________________              RESET   >           Sends a reset signal to one or more delivery agents.  A           ________________________________________________________             FORMAT              RESET  [agent-name...]  A           ________________________________________________________)           Command Qualifiers     Defaults              /ACCOUNTING            /CLUSTER           /NODE=(node[,...])  A           _______________________________________________________M             PARAMETERS           agent-name..._;           One or more MX delivery agent names, separated byE;           commas. Valid names are DECNET_SMTP, JNET, LOCAL,i>           LSV, MLF, ROUTER, SITE, SMTP, UUCP, and X25_SMTP. If=           omitted, all agents running on the same node as theh0           user executing this command are reset.  A           _______________________________________________________e             DESCRIPTION =           The RESET command can be used to signal one or moreh:           MX delivery agents to reload their configuration7           information. This command requires the SYSLCK            privilege.  A           _______________________________________________________              QUALIFIERS           /ACCOUNTING-=           Causes the specified agents to open new versions ofr>           their accounting files. Only useful for those agents  A                                                            MCP-53  E                  MCP Commands           RESETo        ?           that support accounting, and with MLF (which causes aq8           new version of FILESERV_LOG.LOG to be opened).  3           If /ACCOUNTING is specified, no reload ofc>           configuration data is performed; only the accounting           files are reset.             /CLUSTER<           Specifies that the RESET command should affect all;           of the specified agents cluster-wide, rather thanE=           just the ones on the node from which the command is_           executed._             /NODE=(node[,...])=           Specifies that the RESET command should affect only_:           the specified agents running on the given nodes.                                                           MCP-54 l  o    A                                                      MCP Commands_A                                                            REVIEWe        A           _______________________________________________________e             REVIEW  ;           Displays the subscribers of a local mailing list.s  A           _______________________________________________________              FORMAT             REVIEW  mailing-list  A           ________________________________________________________)           Command Qualifiers     Defaults              /OUTPUT=file-spec   A           _______________________________________________________u             PARAMETERS           mailing-list;           Name of the mailing list whose subscriber list is >           to be displayed. The mailing list must reside on the           local system.h  A           _______________________________________________________i             DESCRIPTION <           This command performs the functional equivalent of=           the mailing list processor's REVIEW command for anyC<           mailing list on the local system. All subscribers'=           addresses and personal names (if any) listed, along (           with their MAIL/NOMAIL status.  A           _______________________________________________________              QUALIFIERS           /OUTPUT=file-spece@           Directs the results to the specified file. If omitted,2           the results are displayed on SYS$OUTPUT.  A                                                            MCP-55_ _  _               MCP Commands           SAVE        A           _______________________________________________________O             SAVE  4           Saves the current configuration to a file.  A           _______________________________________________________g             FORMAT             SAVE  file-specC  A           _______________________________________________________              PARAMETERS           file-spec_<           The name of the file to which the configuration is?           written. If omitted, the file type defaults to MXCFG.   A           _______________________________________________________              DESCRIPTION @           Use this command to write the MX configuration you are=           creating or changing to a file. You should save the_=           configuration to the file MX_DIR:MX_CONFIG.MXCFG if =           you want it to be used by the MX processing agents._                                       MCP-56 O  T    A                                                      MCP Commands_A                                                   SET DECNET_SMTPl        A           _______________________________________________________              SET DECNET_SMTP_  :           Alters settings specific to the SMTP-over-DECnet           delivery agent.u  A           _______________________________________________________e             FORMAT             SET DECNET_SMTP   A           _______________________________________________________ )           Command Qualifiers     Defaults_             /[NO]ACCOUNTING             /MAXIMUM_RETRIES=count$           /RETRY_INTERVAL=delta-time  A           _______________________________________________________              DESCRIPTION =           This command is used to change the SMTP-over-DECnety           agent settings.e  A           ________________________________________________________             QUALIFIERS           /[NO]ACCOUNTING 9           Enables or disables the recording of accountingy>           information. Accounting is disabled by default. When@           enabled, accounting information is written to the file?           MX_DNSMTP_DIR:MX_DNSMTP_ACC.DAT. You can redirect the @           accounting information to another file by defining the%           logical name MX_DNSMTP_ACC._  1           The format of the accounting record is:e  a           dd-mmm-yyyy hh:mm XMIT: PROTO=DECNET_SMTP, SOURCE="src-addr", HOST="host", BYTES_SENT=nT  A                                                            MCP-57_ _  _               MCP Commands           SET DECNET_SMTP         ?           where dd-mmm-yyyy hh:mm is the date/time stamp of the ?           accounting record; src-addr is the source address forY@           the message; host is the host to which the message was=           sent; and n is the number of bytes in the delivered            message.              /MAXIMUM_RETRIES=count8           Sets the maximum number of retries for message>           delivery. The default count is 96, which for a half-:           hour retry interval comes to roughly two days of           retries.  $           /RETRY_INTERVAL=delta-time<           Sets the amount of time that should elapse between?           delivery attempts. The default is 30 minutes. Specify $           as a VMS delta time value.                                                           MCP-58 _  _    A                                                      MCP CommandsnA                                                          SET JNET_        A           _______________________________________________________a             SET JNET  9           Alters settings specific to the Jnet interface.,  A           _______________________________________________________              FORMAT             SET JNET  A           _______________________________________________________ )           Command Qualifiers     Defaults              /[NO]ACCOUNTINGt           /[NO]BSMTP_REPLY           /[NO]LENIENT           /[NO]PERCENT_HACKt(           /[NO]USERNAME=(username[,...])  A           _______________________________________________________i             DESCRIPTION ?           This command is used to enable or disable the various 2           settings specific to the Jnet interface.  A           _______________________________________________________              QUALIFIERS           /[NO]ACCOUNTING 9           Enables or disables the recording of accounting >           information. Accounting is disabled by default. When;           enabled, accounting information is written to thee@           file MX_JNET_DIR:MX_JNET_ACC.DAT. You can redirect the@           accounting information to another file by defining the#           logical name MX_JNET_ACC.   1           The format of the accounting record is:   [           dd-mmm-yyyy hh:mm XMIT: PROTO=proto, SOURCE="src-addr", HOST="dest", BYTES_SENT=na  A                                                            MCP-59                     MCP Commands           SET JNET        @           where proto is one of the BITNET mailer protocol types:           (BSMTP, JNET, or BITNET), src-addr is the source=           address for the message, dest is the BITNET host to <           which the message was sent, and n is the number of@           bytes transmitted. Note that with the BSMTP and BITNET<           protocol types, one transmission can have multiple(           destinations on a single host.             /[NO]BSMTP_REPLY>           Controls whether replies are sent for incoming BSMTP;           transactions. Most hosts supporting BSMTP discard ?           any replies, so this is disabled by default to reduce            network traffic.             /[NO]LENIENT<           Controls whether BITNET gateway rules are strictly?           or leniently enforced. The gateway rules specify that ?           no messages may be gatewayed to or from a BITNET/EARNl@           host that does not run a BSMTP-compliant mailer. Until?           more BITNET and EARN hosts start running mailers, youa@           may wish to use the lenient setting to avoid excessive&           rejection of gatewayed mail.             /[NO]PERCENT_HACK)4           Enables or disables automatic percent-hack<           translation. The default is to enable translation.  =           Percent hacking should be disabled when Jnet is thee5           only network transport being used for mail._  (           /[NO]USERNAME=(username[,...])?           Specifies the username(s) in the NJE tags on incomingi@           mail files that should be considered as being destined9           for the mailer. The first username in the list, :           called the primary mailer username, will also be;           used as the NJE origin user on outgoing messages,p@           which should match the value of the :mailer tag in the6           XMAILER.NAMES file entry for the local host.               MCP-60 W       A                                                      MCP CommandstA                                                          SET JNETa        ;           If omitted or disabled by SET JNET/NOUSERNAME, MXo>           uses the username of the process running the MX/Jnet+           interface as the mailer username.n  <           Generally, only one mailer username will be needed<           per system, which by BITNET recommendations should9           be MAILER. The need for recognition of multipleY=           mailer usernames should occur only if you decide tos@           change the mailer username for your system, during the,           transition period from old to new.                                                            A                                                            MCP-61                     MCP Commands           SET LOCAL         A           _______________________________________________________              SET LOCAL   2           Alters Local-delivery-specific settings.  A           ________________________________________________________             FORMAT             SET LOCAL_  A           ________________________________________________________)           Command Qualifiers     Defaults_             /[NO]ACCOUNTINGT           /[NO]CC_POSTMASTER           /[NO]DISALBE_EXQUOTA2           /[NO]HEADERS=(loc:(hdrname[,...])[,...])            /MAXIMUM_RETRIES=count           /[NO]MULTIPLE_FROM           /[NO]QP_DECODE$           /RETRY_INTERVAL=delta-time  A           _______________________________________________________              DESCRIPTION ;           This command is used to change the local delivery            agent settings.n  A           ________________________________________________________             QUALIFIERS           /[NO]ACCOUNTING 9           Enables or disables the recording of accountinge>           information. Accounting is disabled by default. When@           enabled, accounting information is written to the file=           MX_LOCAL_DIR:MX_LOCAL_ACC.DAT. You can redirect the @           accounting information to another file by defining the$           logical name MX_LOCAL_ACC.  1           The format of the accounting record is:_  \                            dd-mmm-yyyy hh:mm DELIVER: SOURCE="src-addr", USER="user", SIZE=n             MCP-62         A                                                      MCP CommandsaA                                                         SET LOCAL         ?           where dd-mmm-yyyy hh:mm is the date/time stamp of the ?           accounting record; src-addr is the source address for ?           the message; user is the address on the local host toe>           which the message was delivered; and n is the number,           of bytes in the delivered message.             /[NO]CC_POSTMASTER;           Specifies whether or not error messages resultinga<           from LOCAL delivery errors are mailed to the local9           POSTMASTER, in addition to the original messageQ           sender.              /[NO]DISABLE_EXQUOTA;           Specifies whether the local delivery agent should :           disable the EXQUOTA privilege when attempting to;           deliver messages to VMS MAIL. By default, EXQUOTA 8           privilege remains enabled during local message8           delivery. Using the /DISABLE_EXQUOTA qualifier<           will prevent users' mailboxes from exceeding their           diskquotas._  .           /HEADERS=(loc:(hdrname[,...])[,...])9           Controls the inclusion and placement of RFC 822_:           headers in messages delivered to VMS Mail. Valid=           values for loc are TOP and BOTTOM. Valid values fore,           hdrname are listed in Table MCP-4.  A           Table_MCP-4__Header_name_keywords______________________o  A           Keyword____________Meaning_____________________________   )           ALL                All headers.   @           BCC                The Bcc (blind carbon copy) header.  9           CC                 The CC (carbon copy) header._  -           DATE               The Date header.E  -           FROM               The From header.   4           IN_REPLY_TO        The In-Reply-To header.  A                                                            MCP-63                     MCP Commands           SET LOCALe        A           Table_MCP-4_(Cont.)__Header_name_keywords______________   A           Keyword____________Meaning_____________________________   >           KEYWORDS           The Keywords header (not strictly&                              RFC 822).  3           MESSAGE_ID         The Message-Id header._  =           OTHER              Any header not recognized by MX.   4           RECEIVED           The Received header(s).  @           REFERENCES         The References header (not strictly&                              RFC 822).  1           REPLY_TO           The Reply-To header.   3           RESENT_BCC         The Resent-Bcc header.n  2           RESENT_CC          The Resent-CC header.  4           RESENT_DATE        The Resent-Date header.  4           RESENT_FROM        The Resent-From header.  :           RESENT_MESSAGE_ID  The Resent-Message-Id header.  8           RESENT_REPLY_TO    The Resent-Reply-To header.  6           RESENT_SENDER      The Resent-Sender header.  2           RESENT_TO          The Resent-To header.  4           RETURN_PATH        The Return-Path header.  /           SENDER             The Sender header.   0           SUBJECT            The Subject header.  A           TO_________________The_To_header.______________________   @           The header names can be negated by prefixing them with<           NO. You may include any combination of headers for=           inclusion at the top and/or the end of the message.a>           For example, you might want to move the Received and>           Return-Path headers to the bottom of messages, since?           the information they convey are of interest only when.%           there are network problems:_  W                            MCP> SET LOCAL/HEADERS=(TOP:(ALL,NORECEIVED,NORETURN_PATH),- X                            _MCP>                    BOTTOM:(NOALL,RECEIVED,RETURN_PATH))             MCP-64 i       A                                                      MCP Commands A                                                         SET LOCALr                    /MAXIMUM_RETRIES=count?           Sets the maximum number of retries for DECnet message >           delivery. The default count is 96, which for a half-:           hour retry interval comes to roughly two days of           retries.             /[NO]MULTIPLE_FROM;           Controls whether or not the VMS Mail "From:" line :           on incoming messages can contain multiple return=           addresses. By default, if an RFC822 From: or Reply-s=           To: line contains more than one address, as many of =           those addresses as will fit are included on the VMS >           Mail "From:" line (up to 255 characters). Specifying>           /NOMULTIPLE_FROM limits the "From:" line to a single           address.             /[NO]QP_DECODE@           Controls whether or not incoming MIME quoted-printable?           messages are automatically decoded by MX Local beforeo>           delivery through VMS Mail. By default, such messages?           are decoded. If your users read their mail via POP ore=           IMAP, you might want to disable the decoding to lete.           the users' browsers do the decoding.  $           /RETRY_INTERVAL=delta-time<           Sets the amount of time that should elapse between?           delivery attempts. The default is 30 minutes. Specify $           as a VMS delta time value.                        A                                                            MCP-65o                    MCP Commands           SET MLF         A           _______________________________________________________              SET MLF   9           Alters MLF (Mailing List/File server) settings.e  A           _______________________________________________________              FORMAT             SET MLF_  A           _______________________________________________________ )           Command Qualifiers     Defaults_  $           /[NO]DELAY_DAYS[=(dow...)]$           /[NO]RECIPIENT_MAXIMUM[=n]  A           ________________________________________________________             DESCRIPTION_=           This command sets global parameters for the Mailingl'           List/File Server agent (MLF).i  A           _______________________________________________________l             QUALIFIERS$           /[NO]DELAY_DAYS[=(dow...)]?           Specifies the days of the week on which file servers' ?           send-delay threshold should be respected. The defaulte:           is to respect send-delay thresholds on every day9           of the week. A list of day-of-week names may bem>           specified. Specify /NODELAY_DAYS to globally disable4           send-delay thresholds on all file servers.  $           /[NO]RECIPIENT_MAXIMUM[=n];           Sets the maximum number of recipients per message @           generated by the MLF agent. If your MLF agent services?           large mailing lists with many remote subscribers, you =           may want to use this setting to limit the number of <           recipients per message generated by MLF. This will<           break up the distribution to the mailing list into             MCP-66 O       A                                                      MCP Commands A                                                           SET MLFg        :           smaller chunks, allowing for more parallelism in           delivery._  <           Setting too small a value, however, could create a@           lengthy backlog in your MX message queue, depending on?           the number of subscribers on your mailing list(s) ando<           the number of messages the list receives each day.  @           The default is /NORECIPIENT_MAXIMUM, which forces each?           incoming mailing list message to be forwarded as justh           one outbound message.                                                           A                                                            MCP-67g s                  MCP Commands           SET ROUTER        A           _______________________________________________________              SET ROUTER  *           Alters Router-specific settings.  A           ________________________________________________________             FORMAT             SET ROUTER  A           _______________________________________________________y)           Command Qualifiers     Defaults_             /[NO]ACCOUNTING_"           /[NO]OMIT_VMSMAIL_SENDER           /[NO]PERCENT_HACK   A           _______________________________________________________              DESCRIPTIONf7           This command is used to enable or disable theR:           automatic de-hacking of percent signs in a local?           address. Percent-hacking is explained in Section 3.3.   A           _______________________________________________________T             QUALIFIERS           /[NO]ACCOUNTING 9           Enables or disables the recording of accounting_>           information. Accounting is disabled by default. When@           enabled, accounting information is written to the file?           MX_ROUTER_DIR:MX_ROUTER_ACC.DAT. You can redirect the,@           accounting information to another file by defining the%           logical name MX_ROUTER_ACC.c  ;           The format of the accounting record is one of thei           following:  g           dd-mmm-yyyy hh:mm ROUTE: SENDER="src-addr", RCPT="rcp-addr", ROUTE="host", PATH=path, BYTES=nhl           dd-mmm-yyyy hh:mm BOUNCE: SENDER="src-addr", RCPT="rcp-addr", ORIGRCPT="orcp-addr", ERROR="errmsg"             MCP-68    M    A                                                      MCP Commands A                                                        SET ROUTER         ?           where dd-mmm-yyyy hh:mm is the date/time stamp of the ?           accounting record; src-addr is the source address for ;           the message; rcp-addr is the recipient's address; 8           orcp-addr is the recipient's address before it<           was changed by any rewrite rules; host is the host>           route associated with the matching path; path is the>           delivery path (agent) that will deliver the message;@           errmsg is the text of the error message describing why=           routing failed; and n is the number of bytes in they           delivered message.  "           /[NO]OMIT_VMSMAIL_SENDER@           Enables or disables the omission of the Sender: header>           for messages sent from VMS Mail. Normally, a Sender:=           line is included if the Sender: and From: addresses ?           are different. However, some sites using the MX_SITE__?           NAME_CONVERSION feature with the FULL_CONVERT routineN=           have had problems sending mail to some mailers when,?           the Sender: and From: are different, despite the fact_=           that it is allowed by RFC822 (in fact, according to_<           RFC822, the Sender: should be omitted if it is the<           same address as the From: address). To allow those?           sites to work around the problems with those mailers, >           /OMIT_VMSMAIL_SENDER can be used to omit the Sender:           line in all cases.  >           MX_SITE_NAME_CONVERSION is documented in the Message&           Exchange Programmer's Guide.  >           Note: If /OMIT_VMSMAIL_SENDER is specified, then the=           Sender: line is also omitted from any SMTP messages_<           forwarded by users with the MX_FAKE_RFC822 process           rights identifier.             /[NO]PERCENT_HACKn4           Enables or disables automatic percent-hack<           translation. The default is to enable translation.      A                                                            MCP-69t e                  MCP Commands           SET SITE        A           _______________________________________________________t             SET SITE  >           Alters settings specific to the SITE delivery agent.  A           _______________________________________________________              FORMAT             SET SITE  A           _______________________________________________________ )           Command Qualifiers     Defaultsr              /MAXIMUM_RETRIES=count$           /RETRY_INTERVAL=delta-time  A           _______________________________________________________              DESCRIPTION 7           This command is used to change the SITE agent.           settings.S  A           _______________________________________________________u             QUALIFIERS            /MAXIMUM_RETRIES=count8           Sets the maximum number of retries for message>           delivery. The default count is 96, which for a half-:           hour retry interval comes to roughly two days of           retries.  $           /RETRY_INTERVAL=delta-time<           Sets the amount of time that should elapse between?           delivery attempts. The default is 30 minutes. Specifyt$           as a VMS delta time value.                 MCP-70 t  r    A                                                      MCP CommandstA                                                          SET SMTPm        A           _______________________________________________________i             SET SMTP  1           Alters SMTP-delivery-specific settings.   A           _______________________________________________________l             FORMAT             SET SMTP  A           _______________________________________________________ )           Command Qualifiers     Defaults              /[NO]ACCOUNTINGU"           /DEFAULT_ROUTER=hostname           /DNS_RETRIES=dnscountN            /MAXIMUM_RETRIES=count!           /[NO]RBL_CHECK[=domain]a/           /[NO]RELAY_ALLOWED     /RELAY_ALLOWEDi$           /RETRY_INTERVAL=delta-time%           /[NO]VALIDATE_SENDER_DOMAINl           /[NO]VERIFY_ALLOWED   A           _______________________________________________________t             DESCRIPTIONa;           This command is used to change the SMTP interfaces           settings.-  A           _______________________________________________________M             QUALIFIERS           /[NO]ACCOUNTING 9           Enables or disables the recording of accountingo>           information. Accounting is disabled by default. When;           enabled, accounting information is written to thes@           file MX_SMTP_DIR:MX_SMTP_ACC.DAT. You can redirect the@           accounting information to another file by defining the#           logical name MX_SMTP_ACC..  A                                                            MCP-71o    u               MCP Commands           SET SMTP        1           The format of the accounting record is:i  z           dd-mmm-yyyy hh:mm XMIT: PROTO=SMTP, SOURCE="src-addr", HOST="dest", SENT-TO="relay", BYTES_SENT=n, RCPT=rcp-addr  ?           where src-addr is the source address for the message; 8           dest is the name of the Internet host to which<           the message was directed; relay is the name of the?           Internet host to which the message was actually sent; <           n is the number of bytes transmitted; and rcp-addr<           is the recipient's address. One accounting message?           is written for each successful delivery of a message,n<           so one message could result in multiple accounting           records.  "           /DEFAULT_ROUTER=hostname=           Specifies the name of a host to which SMTP messagesM<           can be forwarded if MX cannot resolve a host name.;           This qualifier should only be used if you are not >           using the Internet domain name service. The hostname<           should be the name of a host which appears in your           local host table.              /DNS_RETRIES=dnscount_>           Sets the maximum number of retries for SMTP delivery;           when the cause of the failure is the inability to =           determine the address corresponding to a host name..>           Certain types of domain server failures can cause MX=           to believe a host name is invalid. When a host nameD=           is genuinely invalid, however, the sender should beg?           told relatively quickly. Therefore, the default counta>           is 12 (giving about 6 hours' worth of attempts for a$           half-hour retry interval).              /MAXIMUM_RETRIES=count=           Sets the maximum number of retries for SMTP message >           delivery. The default count is 96, which for a half-:           hour retry interval comes to roughly two days of           retries.               MCP-72    m    A                                                      MCP Commands A                                                          SET SMTPe        !           /[NO]RBL_CHECK[=domain]h=           Controls whether the SMTP server checks to see if as?           connecting host is on the Internet Realtime Blackhole 8           List (RBL) before allowing it to start an SMTP/           session. This is disabled by default.t  <           When /RBL_CHECK is specified without a domain, the-           default domain is rbl.maps.vix.com.B  8           See Section 8.5 for more information about the"           Realtime Blackhole List.             /[NO]RELAY_ALLOWED<           Controls whether the SMTP server accepts "relayed"@           messages. A relayed message is a message from a remote<           source that lists recipients that are also remote.)           Relaying is allowed by default.e  =           When relaying is disabled, the SMTP server examinesr>           the originator's address on each incoming message as=           well as each recipient's address. If both addressesM<           are remote, delivery to the remote recipient(s) is?           refused. By default, any address that maps to a LOCAL <           path is considered local, as is any host name that>           shares the same parent domain as the MX host name or=           the TCP/IP host name. You may specify other host or @           domain names that should also be considered local with*           the DEFINE LOCAL_DOMAIN command.  $           /RETRY_INTERVAL=delta-time<           Sets the amount of time that should elapse between?           delivery attempts. The default is 30 minutes. Specify $           as a VMS delta time value.  %           /[NO]VALIDATE_SENDER_DOMAIN ?           Enables or disables a check by the SMTP server on thea@           validity of the domain name appearing in the SMTP MAIL?           FROM: command on incoming messages. When enabled, the @           SMTP server attempts to look up the domain name of the@           sender in the domain name system; if the name does not?           appear in the DNS (with any type of resource record),   A                                                            MCP-73e r  .               MCP Commands           SET SMTP        @           the MAIL FROM command, and hence the incoming message,@           will is rejected. This setting is disabled by default.  :           Enabling this option can be useful in preventing?           unwanted junk e-mail from entering your system, since-;           junk e-mail is often sent using fictitious returnh=           addresses, sometimes with nonexistent domain names.a             /[NO]VERIFY_ALLOWED =           Enables or disables the processing of VRFY commandsT:           in the SMTP server. The VRFY command, a required>           command in the SMTP protocol, is often used by users?           on other systems to check whether or not a particular <           mailbox is valid. This information can be regarded;           as a security risk, and security-conscious system ?           administrators may want to prevent VRFY commands from            being processed.  0           By default, VRFY commands are allowed.                                                     MCP-74 l  y    A                                                      MCP CommandsoA                                                      SET X25_SMTPe        A           _______________________________________________________              SET X25_SMTP  8           Alters settings specific to the SMTP-over-X.25           delivery agent._  A           _______________________________________________________              FORMAT             SET X25_SMTP  A           _______________________________________________________ )           Command Qualifiers     Defaults              /[NO]ACCOUNTINGT            /MAXIMUM_RETRIES=count$           /RETRY_INTERVAL=delta-time  A           _______________________________________________________              DESCRIPTIONr;           This command is used to change the SMTP-over-X.25            interface settings.   A           _______________________________________________________c             QUALIFIERS           /[NO]ACCOUNTING 9           Enables or disables the recording of accounting >           information. Accounting is disabled by default. When@           enabled, accounting information is written to the file=           MX_XSMTP_DIR:MX_XSMTP_ACC.DAT. You can redirect the @           accounting information to another file by defining the$           logical name MX_XSMTP_ACC.  1           The format of the accounting record is:t  ^           dd-mmm-yyyy hh:mm XMIT: PROTO=X25_SMTP, SOURCE="src-addr", HOST="dest", BYTES_SENT=n  A                                                            MCP-75I o  u               MCP Commands           SET X25_SMTP        ?           where src-addr is the source address for the message;r?           dest is the name of the host to which the message was >           sent; and n is the number of bytes transmitted. Note@           that with X25_SMTP messages, one transmission can have1           multiple destinations on a single host.               /MAXIMUM_RETRIES=count9           Sets the maximum number of retries for X25_SMTP @           message delivery. The default count is 96, which for a?           half-hour retry interval comes to roughly two days of            retries.  $           /RETRY_INTERVAL=delta-time<           Sets the amount of time that should elapse between?           delivery attempts. The default is 30 minutes. Specify_$           as a VMS delta time value.                                                           MCP-76    O    A                                                      MCP Commands A                                                              SHOW         A           _______________________________________________________l             SHOW  ?           Displays all or part of the current MX configuration._  A           _______________________________________________________O             FORMAT+                 { ALIASES [pattern]       }o+                 { CONFIGURATION_FILE      }t+                 { DECNET_SMTP             } +                 { FILE_SERVER [pattern]   }n+                 {                         }d+                 { JNET                    }.+                 { KEY [key]               } +                 { LISTS [pattern]         }v+                 {                         } +                 { LOCAL                   }t+           SHOW  { PATHS [pattern]         }F+                 { REWRITE_RULES [pattern] } +                 {                         }e+                 { ROUTER                  }i+                 { SITE                    }n+                 { SMTP                    } +                 {                         }i+                 { SYSTEM_USERS            } +                 { VERSION                 } +                 { X25_SMTP                } +                 {                         } +                 { ALL                     }m  A           _______________________________________________________l)           Command Qualifiers     Defaults   +           /[NO]COMMAND           /NOCOMMANDe4           /OUTPUT=file-spec      /OUTPUT=SYS$OUTPUT:  A           _______________________________________________________v             DESCRIPTION :           The SHOW command displays the specified parts of9           the current MX configuration. For aliases, fileh>           servers, lists, paths, and rewrite rules, only those>           records matching pattern (which may contain wildcard=           characters) are displayed; if you omit pattern, allm            records are displayed.  A                                                            MCP-77                     MCP Commands           SHOW        :           SHOW CONFIGURATION_FILE displays the name of the9           configuration file loaded when MCP was started.T>           SHOW VERSION displays the version identifier for the            current version of MX.  A           ________________________________________________________             QUALIFIERS           /[NO]COMMAND;           The /COMMAND qualifier indicates that the display_;           should be formatted as the commands that would bed?           entered to create the specified records. Use /COMMANDc=           with the /OUTPUT qualifier to create an MCP commandl=           file that can be altered with your favorite editor,_@           then read back into MCP to create a new configuration.             /OUTPUT=file-spece:           The /OUTPUT qualifier is used to direct the SHOW;           result to a file or other device. By default, theb;           result is displayed on the current output device,            SYS$OUTPUT._                                                 MCP-78 a  n    A                                                      MCP CommandscA                                                          SHUTDOWN         A           _______________________________________________________              SHUTDOWN  9           Sends a shutdown signal to one or more deliveryN           agents.r  A           _______________________________________________________              FORMAT  #           SHUTDOWN  [agent-name...]   A           _______________________________________________________ )           Command Qualifiers     Defaults              /CLUSTER           /NODE=(node[,...])  A           _______________________________________________________              PARAMETERS           agent-name...s;           One or more MX delivery agent names, separated byf@           commas. Valid names are DECNET_SMTP, JNET, LOCAL, LSV,>           MLF, ROUTER, SITE, SMTP, SMTP_SERVER, UUCP, and X25_?           SMTP. If omitted, all agents running on the same node;;           as the user executing this command are shut down.g  <           Note that the SMTP delivery agent may be shut down>           separately from the SMTP_SERVER message entry agent.  A           _______________________________________________________e             DESCRIPTIONg@           The SHUTDOWN command can be used to signal one or more@           MX delivery agents to finish processing and exit. This0           command requires the SYSLCK privilege.    A                                                            MCP-79e d  o               MCP Commands           SHUTDOWN      A           _______________________________________________________t             QUALIFIERS           /CLUSTER?           Specifies that the SHUTDOWN command should affect thee@           specified agents on all nodes in the cluster, not just           the current node.t             /NODE=(node[,...])?           Specifies that the SHUTDOWN command should affect the 3           specified agents only on the given nodes.E                                                                       MCP-80         A                                                      MCP Commands A                                                             SPAWNw        A           _______________________________________________________.             SPAWNP             Spawns a subprocess.  A           _______________________________________________________i             FORMAT             SPAWN  [dcl-command]  A           _______________________________________________________C             PARAMETERS           dcl-command <           A DCL command to be executed in the subprocess. If@           omitted, MCP is suspended and the terminal is attached>           to the subprocess for interactive entry of commands.;           To return to the process running MCP, use the DCL /           LOGOUT command to end the subprocess._  A           _______________________________________________________              DESCRIPTIONI=           This command creates a subprocess to execute one or_;           more DCL commands. See the description of the DCL 0           SPAWN command for further information.                        A                                                            MCP-81_ _  _               MCP Commands           STATUS        A           _______________________________________________________f             STATUS  =           Displays a list of the MX agent processes currently >           running and the current state of each agent process.  A           _______________________________________________________n             FORMAT  !           STATUS  [agent-name...]a  A           _______________________________________________________a)           Command Qualifiers     Defaultsr             /NODE=(node[,...])  A           _______________________________________________________              PARAMETERS           agent-name... :           One or more MX agent names, separated by commas.=           Valid names are DECNET_SMTP, JNET, LOCAL, LSV, MLF,e>           ROUTER, SITE, SMTP, SMTP_SERVER, UUCP, and X25_SMTP.@           If omitted, information about all agents is displayed.  A           _______________________________________________________              DESCRIPTIONe@           For each process running one of the MX agent programs,?           the process ID, process name, MX status, and MX agentX9           type is displayed. In a VMScluster environment, :           the VMScluster node name for the process is also@           displayed. This command requires the SYSLCK privilege.  ?           The status field indicates the action currently being_?           performed by the agent. Valid status descriptions are            shown in Table MCP-5.t             MCP-82         A                                                      MCP Commands_A                                                            STATUS         A           Table_MCP-5__MCP_STATUS_Descriptions___________________o  5           Unknown        Current status is not known.b  ;           Reading        Reading the MX configuration file.M           Config.A  >           Idle           Process is idle, waiting for an entry$                          to process.  =           Enabling       Requesting single agent enable lock.   ?           Selecting      Searching in-memory queue for an entrys$                          to process.  ?           Searching      Searching in-memory queue for an entry $                          to process.  <           Locating       Initializing the in-memory queue by@                          searching the MX queue file for entries7                          to be processed by that agent.h  >           Searching2     Searching in-memory queue for located!                          entries.m  8           Processing     Processing the specified entry.  ;           Retrying       Retrying delivery of the specifiede                          entry.   5           Inserting      Inserting a new queue entry.n  7           Search. for    Searching for delayed entries.i           wait  ?           Waiting for    Idle, waiting to process the specifiedh                          entry.s  =           Req update     Requesting other agents to update anm                          entry.l  >           FLQ Cleanup    Performing MX queue file maintenance.  =           FLQread wait   Waiting for a read from the MX queueo                          file.  5           Wlock wait     Waiting for entry work lock._  @           Connected      SMTP Server has the specified number ofA           _______________incoming_connections_active.____________   A                                                            MCP-83t    e               MCP Commands           STATUS      A           _______________________________________________________g             QUALIFIERS           /NODE=(node[,...])@           Specifies that the STATUS command should show only the6           specified agents running on the given nodes.                                                                                 MCP-84 s  e              A           _______________________________________________________n  #           REJMAN Command Dictionaryo r  y    A                                                   REJMAN Commands A                                                            REJMAN         A           _______________________________________________________              REJMAN  ,           Executes the MX Rejection Manager.  A           _______________________________________________________c             FORMAT             REJMAN  [command]   A           _______________________________________________________s)           Command Qualifiers     Defaults              /DATABASE=file-specw  A           _______________________________________________________              PARAMETERS           commanda9           Any REJMAN command except the input redirection =           operator (@). The specified command is executed andv<           control is returned to DCL immediately thereafter.  A           _______________________________________________________              DESCRIPTION :           REJMAN was written to be used as a DCL "foreign"?           command. To use it this way, you must define a symbolr           as follows:m  6                            $ REJMAN :== $MX_EXE:REJMAN  ?           Defining the symbol in this way allows you to use ther@           /DATABASE qualifier and specify "one-host" commands on           the command line.h  ?           By default, REJMAN loads in the current configuratione8           file, MX_DIR:MX_REJECTION_DATABASE.MXCFG, when           started.  ?           Note: REJMAN requires the SYSLCK privilege to be ables?           to lock the rejection database from being modified bym           other processes.  A                                                          REJMAN-3e t  n               REJMAN CommandsT           REJMAN      A           _______________________________________________________V             QUALIFIERS           /DATABASE=file-spec =           Loads the specified rejection database for editing.a<           If not specified, the default database, MX_DIR:MX_.           REJECTION_DATABASE.MXCFG, is loaded.                                                                               REJMAN-4 m  y    A                                                   REJMAN CommandsoB                                          Command Input Redirection        A           _______________________________________________________M  #           Command Input Redirectionm  3           Execute REJMAN commands stored in a file.   A           _______________________________________________________t             FORMAT             @  file-spec  A           _______________________________________________________              PARAMETERS           file-spect=           Name of the file containing REJMAN commands. If them8           file type is omitted, the default type is MCP.  A           _______________________________________________________e             DESCRIPTION >           Use this command to have REJMAN take further command=           input from the specified file. There is no built-inp=           limit on the number of levels of nesting of command @           files, so be careful when using input redirection from            within a command file.  =           This command can only be used at the REJMAN command ?           prompt, not as a "one-shot" REJMAN command. To have a >           file be used for input for an entire REJMAN session,5           use the following sequence of DCL commands.a  <                            $ DEFINE/USER SYS$INPUT file-spec#                            $ REJMAN_          A                                                          REJMAN-5                     REJMAN Commands            ADD EXCLUSION         A           ________________________________________________________             ADD EXCLUSIONM  ;           Adds an exclusion to heuristic junk mail filters._  A           _______________________________________________________D             FORMAT  #           ADD EXCLUSION  sender-patR  A           ________________________________________________________)           Command Qualifiers     Defaults_  #           /HEURISTIC=heuristic-name   A           _______________________________________________________e             PARAMETERS           sender-pat@           E-mail address or wildcard pattern to match the sender:           of the message, as it would appear in either the;           RFC822 From header or the SMTP MAIL FROM command.   A           _______________________________________________________o             DESCRIPTION <           This command adds a new exception to one or all of;           the heuristic filters. If the sender (from eitherg>           the RFC822 From header, or the SMTP MAIL FROM return=           path) of a message matches this address or pattern, >           the message is excluded from the specified heuristic7           filter check (or all checks if the /HEURISTIC             qualifier is omitted).  A           _______________________________________________________-             QUALIFIERS#           /HEURISTIC=heuristic-namei@           Specifies the heuristic filter to which this exclusion>           applies. If not specified, the exclusion is added to<           the global exclusion list for all heuristic filter           checks.              REJMAN-6         A                                                   REJMAN CommandsfA                                                     ADD REJECTIONw        A           _______________________________________________________              ADD REJECTION   <           Adds a rejection rule to the database for the SMTP           server.p  A           _______________________________________________________p             FORMAT  .           ADD REJECTION  sender-pat [rcpt-pat]  A           _______________________________________________________ )           Command Qualifiers     Defaultsm             /ACCEPT[=accept-kwd]           /ADDRESS=ip-addr-pat           /HEADER $           /MESSAGE=rejection-message  A           _______________________________________________________l             PARAMETERS           sender-pat@           E-mail address or wildcard pattern to match the sender=           of the message, as it would appear in the SMTP MAIL >           FROM command. If the /HEADER qualifier is specified,<           this parameter is treated as a wildcard pattern to>           match an RFC822 header in the message, and the rcpt-:           pat parameter and other qualifiers are not used.             rcpt-pat9           E-mail address or wildcard pattern to match the =           recipient of the message, as it would appear in the @           SMTP RCPT TO command. If omitted, matching only occurs>           against the sender, and a match causes the rejection>           to happen immediately after receipt of the MAIL FROM8           command, rather than on a per-recipient basis.  8           This parameter is not permitted if the /HEADER!           qualifier is specified.   A                                                          REJMAN-7                     REJMAN Commands_           ADD REJECTION       A           _______________________________________________________              DESCRIPTION 7           This command adds a new rejection rule to thel<           database. For address-based rejection rules (those@           not specifying /HEADER), a match occurs for any of the           following:  >           1  sender-pat is specified with no rcpt-pat, and the>              address in the SMTP MAIL FROM command matches the=              specified address or pattern. The sending system <              is notified of the rejection in the status code0              returned for the MAIL FROM command.  @           2  sender-pat and rcpt-pat are both specified. In this@              case, the SMTP MAIL FROM address must match sender-A              pat and the RCPT TO address must match the rcpt-pat. @              The check occurs on receipt of the RCPT TO command,>              and if a match occurs, the sending SMTP system is=              notified of the rejection in the status returnedH?              on the RCPT TO. Note that this may not prevent ther>              delivery of the message to other users who do not(              match the rcpt-pat pattern.  :           In both cases, the rule can be restricted by the:           use of the /ADDRESS qualifier; if specified, the=           sending SMTP system's numeric IP address must matchh=           the address or pattern specified on that qualifier.q>           You may modify the behavior of MX's SMTP server when;           a match occurs by using other qualifiers; see thei6           qualifier descriptions for more information.  ;           Header-based rules are specified with the /HEADERc>           qualifier. Header-based rules are checked only after<           the entire message is received by the SMTP server,>           and if a match occurs, the sender is notified of the?           rejection after it transmits the termination sequence =           (CRLF-dot-CRLF) for the message. Header-based rules :           affect delivery to all specified recipients of a<           message; the rcpt-pat parameter is not used. Other?           qualifiers are not allowed when the /HEADER qualifier            is used.             REJMAN-8    _    A                                                   REJMAN CommandsMA                                                     ADD REJECTION_      A           _______________________________________________________s             QUALIFIERS           /ACCEPT[=accept-kwd]>           Specifies that the message should be accepted rather>           than rejected. This qualifier can be used to provide>           exceptions to other rejection rules; it applies only>           when both the sender-pat and rcpt-pat parameters are5           specified. Valid values for accept-kwd are:P  :           o  AS_IS. This is the default when no keyword is@              specified, and indicates that the recipient address#              should not be altered.   ;           o  REWRITE=new-rcpt-addr. This indicates that the ;              recipient's address should be rewritten to the_A              specified new address. This mechanism can be used toO@              re-direct messages that would otherwise be rejected@              to the postmaster or to another party that might be:              interested in tracking the unwanted messages.  ?           This qualifier cannot be used in combination with thed6           /MESSAGE qualifier or the /HEADER qualifier.             /ADDRESS=ip-addr-pat;           Specifies either an IP address (in dotted-decimal 8           form) or a wildcard pattern for matching an IP>           address. If specified, the IP address of the sending=           SMTP system is obtained for the incoming connection ?           and matched against the specified address or pattern. 7           This qualifier is not allowed when /HEADER isl           specified.             /HEADER 9           Modifies the type of rejection rule to be based 9           on RFC822 headers, rather than on SMTP envelope @           addresses. When specified, the sender-pat parameter is@           used for matching RFC822 headers that might be present=           in the incoming message, and no other parameters orp!           qualifiers are allowed._  A                                                          REJMAN-9M                    REJMAN Commands            ADD REJECTION_        $           /MESSAGE=rejection-message@           Specifies the message emitted by the SMTP server which>           accompanies the SMTP status code indicating that the<           MAIL FROM or RCPT TO command has been rejected. By;           default, a generic message is emitted, indicatingr=           that rejection for the sender or recipient has beenm?           programmed. You cannot use this qualifier with either_9           the /HEADER qualifier or the /ACCEPT qualifier.                                                                            REJMAN-10m d  S    A                                                   REJMAN CommandsoA                                                            ATTACH         A           _______________________________________________________              ATTACH  =           Transfers control to another process in the currentf           process tree.   A           _______________________________________________________              FORMAT              ATTACH  [process-name]  A           _______________________________________________________ )           Command Qualifiers     Defaultse  $           /IDENTIFICATION=process-id           /PARENT_  A           _______________________________________________________              PARAMETERS           process-name:           Name of the process to which the terminal should9           be attached. The process must be in the currentm?           process tree. This parameter is omitted if one of ther"           qualifiers is specified.  A           _______________________________________________________              DESCRIPTIONm?           This command is similar to the DCL ATTACH command. It_?           is used in interactive jobs to attach the terminal toe=           another process in the current process tree for them           job.  A           _______________________________________________________i             QUALIFIERS$           /IDENTIFICATION=process-id@           Specifies the process by its process identification, a           hexadecimal number.r  A                                                         REJMAN-11  n                  REJMAN Commandst           ATTACH                   /PARENTh?           Specifies that the terminal should be attached to the >           current subprocess's immediate parent in the process           tree.                                                                                    REJMAN-12o _  _    A                                                   REJMAN CommandsbA                                                             CHECK         A           _______________________________________________________n             CHECK   =           Checks to see if an address would be blocked by thei           rejection rules.  A           _______________________________________________________              FORMAT  3           CHECK  sender-address [recipient-address]e  A           _______________________________________________________ )           Command Qualifiers     Defaultsm             /ADDRESS=ip-address   A           _______________________________________________________              PARAMETERS           sender-address>           An e-mail address as it would appear on an SMTP MAIL@           FROM: command, representing the sender of the message.             recipient-addressr>           An e-mail address as it would appear on an SMTP RCPT:           TO: command, representing the message recipient.;           If not specified, only the sender address will bey           checked.  A           _______________________________________________________c             DESCRIPTION @           This command simulates the check performed by the SMTP>           server on a sender address, optionally combined with=           a recipient address and the numeric IP address of a            host.i  ?           CHECK will signal its success or failure in finding a @           matching rule. If successful, the patterns in the rule'           are displayed in the message.e  A                                                         REJMAN-13e _  _               REJMAN Commands            CHECK       A           _______________________________________________________              QUALIFIERS           /ADDRESS=ip-address_>           Specifies the IP address to be used in the rejection;           check. This should be specified in dotted-decimalh           format.                                                                                REJMAN-14          A                                                   REJMAN Commands A                                                        DEFINE/KEY         A           _______________________________________________________              DEFINE/KEY  ?           Defines an equivalence string and a set of attributes .           with a key on the terminal keyboard.  A           _______________________________________________________              FORMAT  1           DEFINE/KEY  key-name equivalence-string_  A           _______________________________________________________ )           Command Qualifiers     Defaults_             /ECHO_           /ERASE           /IF_STATEm           /LOCK_STATEu           /LOG           /SET_STATE           /TERMINATE  A           _______________________________________________________E             DESCRIPTION 8           See the DCL help entry for DEFINE/KEY for more&           information on this command.  >           You can have a set of keys defined automatically for?           use with REJMAN by placing DEFINE/KEY commands in the_>           file SYS$LOGIN:MX_MCP_KEYDEFS.INI. Note that this is:           the same file that is used with the MCP program.            A                                                         REJMAN-15                     REJMAN CommandsM           DELETE EXCLUSION        A           _______________________________________________________u             DELETE EXCLUSION  @           Removes an exclusion from heuristic junk mail filters.  A           ________________________________________________________             FORMAT  &           DELETE EXCLUSION  sender-pat  A           _______________________________________________________o)           Command Qualifiers     Defaultsi  #           /HEURISTIC=heuristic-name   A           _______________________________________________________t             PARAMETERS           sender-pat@           E-mail address or wildcard pattern to match the sender:           of the message, as it would appear in either the;           RFC822 From header or the SMTP MAIL FROM command.e  A           _______________________________________________________D             DESCRIPTIONO>           This command removes an entry from either the global:           exclusion list, or from the exclusion list for a?           specific heuristic filter. If the sender (from eitherm>           the RFC822 From header, or the SMTP MAIL FROM return=           path) of a message matches this address or pattern,_>           the message is excluded from the specified heuristic7           filter check (or all checks if the /HEURISTIC             qualifier is omitted).  A           _______________________________________________________f             QUALIFIERS#           /HEURISTIC=heuristic-name_@           Specifies the heuristic filter to which this exclusion:           applies. If not specified, the matching entry is             REJMAN-16s i  d    A                                                   REJMAN Commands_A                                                  DELETE EXCLUSIONh        <           removed from the the global exclusion list for all"           heuristic filter checks.                                                                            A                                                         REJMAN-17  i  n               REJMAN Commandsh           DELETE REJECTION        A           _______________________________________________________d             DELETE REJECTION  5           Removes a rejection rule from the database.   A           _______________________________________________________              FORMAT  1           DELETE REJECTION  sender-pat [rcpt-pat]A  A           _______________________________________________________ )           Command Qualifiers     Defaultsm             /ADDRESS=ip-addr-pat           /HEADER_  A           _______________________________________________________D             DESCRIPTION 8           This command deletes a rule from the rejection6           database. Deletion occurs when the specified>           parameters and qualifiers match the values used when           the rule was added._  A           _______________________________________________________s             QUALIFIERS           /ADDRESS=ip-addr-pat;           Specifies either an IP address (in dotted-decimal_8           form) or a wildcard pattern for matching an IP=           address. This qualifier is not allowed when /HEADER            is specified.s             /HEADERi<           Modifies the type of selected rejection rule to be?           based on RFC822 headers, rather than on SMTP envelope_           addresses.             REJMAN-18     s    A                                                   REJMAN Commands A                                                 DISABLE HEURISTICd        A           _______________________________________________________              DISABLE HEURISTIC   :           Disables junk mail heuristic filters in the SMTP           server.a  A           _______________________________________________________              FORMAT  0           DISABLE HEURISTIC  [heuristic-name...]  A           _______________________________________________________f)           Command Qualifiers     Defaultsu             /ALL  A           _______________________________________________________b             PARAMETERS           heuristic-name=           A comma-separated list of one or more keywords that >           identifies the heuristic filters to be disabled. See;           ENABLE HEURISTIC for the list of heuristic filter            names.  A           _______________________________________________________E             DESCRIPTIONs<           This command disables one or more of the heuristic           junk mail filters.  A           _______________________________________________________              QUALIFIERS           /ALL;           Disables all heuristic filters. No parameters are_5           permitted when this qualifier is specified.m  A                                                         REJMAN-19                     REJMAN Commandsj           ENABLE HEURISTIC        A           _______________________________________________________E             ENABLE HEURISTIC  9           Enables junk mail heuristic filters in the SMTPr           server.m  A           _______________________________________________________              FORMAT  /           ENABLE HEURISTIC  [heuristic-name...]a  A           _______________________________________________________ )           Command Qualifiers     Defaultse             /ALL,           /CONFIDENCE_LEVEL={DEFAULT|clevel}  A           _______________________________________________________e             PARAMETERS           heuristic-name@           A comma-separated list of one or more of the following?           keywords which identify the heuristics to be enabled:               o  FROM_TO_SENDER_SAME              o  INVALID_AOL_ADDRESS  $           o  INVALID_HOTMAIL_ADDRESS             o  MSGID_HAS_FROMm             o  MSGID_HAS_TO/             o  NULL_FROM             o  NULL_MSGID              o  NULL_TO             o  NUMERIC_ADDRESS             o  PRECEDENCE_BULK              o  RECEIVED_AFTER_FROM             o  RECEIVED_ALL_ZEROS_             REJMAN-20_ _  _    A                                                   REJMAN CommandseA                                                  ENABLE HEURISTIC                    o  UIDL_AUTH_SENDER/             o  X_UIDL   A           _______________________________________________________e             DESCRIPTIONa@           This command enables one or more of the heuristic junk           mail filters.i  A           _______________________________________________________o             QUALIFIERS           /ALL9           Enables all heuristic filters. No parameters or <           other qualifiers are permitted when this qualifier           is specified.F  ,           /CONFIDENCE_LEVEL={DEFAULT|clevel}@           Specifies the confidence level to be associated with a>           match against this filter. This is a local qualifier>           that must be specified immediately after a heuristic           name.r  7           The confidence level for a filter is a numberT=           representing the likelihood that a message matchingf:           that filter is junk mail. A low confidence level9           indicates that the message is more likely to bea@           legitimate; a high confidence level indicates that the>           message is more likely to be junk mail. Each message>           passed through the heuristic filters is assigned the;           highest possible confidence level for each filter':           it matches, until either all enabled filters are<           checked or the message is given a confidence level@           that is greater than the REJECT level set with the SET           HEURISTIICS command.  ;           If the DEFAULT keyword is specified, the built-ini<           default confidence level for the heuristic is set.?           Otherwise, specify a decimal number from 0 through 10 0           to set a non-default confidence level.  A                                                         REJMAN-21  e  d               REJMAN Commandse           EXIT        A           _______________________________________________________s             EXIT  >           Saves changes to the database and exits the program.  A           _______________________________________________________M             FORMAT             EXIT  A           ________________________________________________________             DESCRIPTION_@           This command saves the changes made during the current/           REJMAN session and exits the program.s                                                         REJMAN-22a e  e    A                                                   REJMAN Commands A                                                              HELPe        A           ________________________________________________________             HELP  5           Displays information about REJMAN commands.i  A           _______________________________________________________              FORMAT             HELP  [topic]d  A           _______________________________________________________n             PARAMETERS           topice?           Topic, such as a REJMAN command, about which you wante;           help. If omitted, a list of available commands isa           displayed.  A           _______________________________________________________s             DESCRIPTIONq6           This command displays descriptions and other)           information on REJMAN commands.f                              A                                                         REJMAN-23a                    REJMAN Commandsr           QUIT        A           _______________________________________________________              QUIT  3           Exits the program without saving changes.a  A           _______________________________________________________i             FORMAT             QUIT  A           _______________________________________________________p             DESCRIPTION @           This command causes the program to exit without saving?           the changes made during the current session. You wills;           be prompted for confirmation if you have made anye           changes.                                                     REJMAN-24l e  a    A                                                   REJMAN Commands A                                                             PURGEE        A           _______________________________________________________              PURGE   7           Purges old rejection rules from the database.a  A           _______________________________________________________h             FORMAT             PURGE,  A           _______________________________________________________f)           Command Qualifiers     Defaults   *           /BEFORE=date-time      See text.%           /[NO]LOG               /LOGl  A           _______________________________________________________              DESCRIPTION <           The PURGE command deletes rejection rules from the<           database considered "old;" that is, they were last=           used by the SMTP server to reject messages before a =           date in the past. By default, rules not used for 30 =           days are purged from the database; you may overrides3           this by specifying the /BEFORE qualifier.   A           _______________________________________________________              QUALIFIERS           /BEFORE=date-time <           By default, the PURGE command deletes records that?           have not been used for 30 days. You may override thisC2           cut-off date with the /BEFORE qualifier.             /LOG6           By default, the PURGE command logs a message8           indicating the number of rules purged from the@           database, along with the cut-off date when successful.;           Specify /NOLOG to prevent this message from beingt'           issued on a successful PURGE.u  A                                                         REJMAN-25_ _  _               REJMAN CommandsC           SAVE        A           _______________________________________________________e             SAVE  6           Writes out the rejection database to a file.  A           ________________________________________________________             FORMAT             SAVE  [file-spec]i  A           _______________________________________________________              PARAMETERS           file-spect:           Name of the file to which the database should be8           written. If omitted, the default is MX_DIR:MX_=           REJECTION_DATABASE.MXCFG, or the file pointed to by 1           the logical name MX_REJECTION_DATABASE.r  A           _______________________________________________________d             DESCRIPTIONs?           This command writes the rejection database to a file. >           To ensure that the MX SMTP server uses the rejection>           database information, omit the file specification to>           allow REJMAN to write the information to the default           location.                                  REJMAN-26_ _  _    A                                                   REJMAN Commands A                                                    SET HEURISTICS_        A           _______________________________________________________              SET HEURISTICS  >           Modifies global settings for the heuristic junk mail           filters.  A           _______________________________________________________S             FORMAT             SET HEURISTICS  A           _______________________________________________________ )           Command Qualifiers     Defaults   ;           /CONFIDENCE_LEVEL=[(ACCEPT=number,REJECT=number)]p2           /[NO]INCLUDE_REASON    /NOINCLUDE_REASON1           /REJECT_ACTION={DROP|FORWARD[=address]}   A           _______________________________________________________              DESCRIPTION ;           This command modifies the global settings for the 8           heuristic junk mail filter in the SMTP server.  A           _______________________________________________________m             QUALIFIERS           /CONFIDENCE_LEVEL @           Sets the confidence levels for accepting and rejecting<           messages as junk mail. Each heuristic filter has a<           confidence level, representing the likelihood that;           a message matching that filter is junk mail. This ?           qualifier is used to set the thresholds for accepting <           a message as legitimate and rejecting a message as           junk mail.  :           This qualifier takes a list of keywords (ACCEPT,@           REJECT) that assign the threshold values. Each keyword;           must be specified with a value, which is either ae<           number from 0 to 10 or the keyword DEFAULT. If you?           specify both the ACCEPT and REJECT keywords, you must *           enclose the list in parentheses.  A                                                         REJMAN-27                     REJMAN CommandsE           SET HEURISTICS        #           The default settings are:D  @                            /CONFIDENCE_LEVEL=(ACCEPT=0,REJECT=8)  ;           A message is considered fully acceptable when its @           assigned confidence level is less than or equal to the?           ACCEPT threshold; in that case, the message is passed_<           on to recipients with no further action. A message>           is considered junk mail when its assigned confidence=           level is greater than the REJECT threshold; in thato>           case, the action specified by SET HEURISTICS/REJECT_           ACTION is taken.  =           Messages assigned confidence levels between the two >           thresholds are considered partially acceptable. They<           are passed on to the recipients with an additional;           header (X-Junk-Mail-Rating) warning them that them>           message may be junk mail. A second additional header;           containing the reason for the warning may also beg=           included based on the SET HEURISTICS/INCLUDE_REASONE           setting.             /INCLUDE_REASONf;           For a message that is assigned a confidence level >           that falls between the ACCEPT and REJECT thresholds,;           specifies that an additional header (X-Junk-Mail- >           Reason) be included in the message to explain to the>           recipient why the message was flagged with a warning?           indicating that it might be junk mail. The default is_           /NOINCLUDE_REASON.             /REJECT_ACTION@           Specifies the action to take when the confidence level=           assigned to a message exceeds the REJECT threshold. =           This qualifier takes one of two keyword values. Theu<           DROP keyword specifies that the SMTP server should=           drop the message by sending an error status back top@           the sending SMTP system. The FORWARD keyword specifies<           that the message should be diverted to a different@           address. You may specify an address as a value for the             REJMAN-28_ _  _    A                                                   REJMAN Commands A                                                    SET HEURISTICSl        =           FORWARD keyword; if omitted, the default address ist)           Postmaster on the local system.   <           When the FORWARD keyword is specified, the message>           is silently diverted to the forwarding address, with<           headers added to the top of the message indicating;           the reason the message was rejected, the original >           sending address, and the original recipients for the=           message. This setting is provided so that the local @           postmaster or other responsible person can verify that?           any messages rejected by the heuristic filters are ine=           fact junk mail. In the case that a rejected message =           is actually legitimate, the system manager can then_?           forward the message on to its intended recipients andO>           modify the heuristic filter configuration to prevent:           such messages from being rejected in the future.  5           The default setting is /REJECT_ACTION=DROP.                                             A                                                         REJMAN-29                     REJMAN Commands            SHOW        A           _______________________________________________________N             SHOW  ;           Displays rejection entries and other information._  A           _______________________________________________________              FORMAT             SHOW  keywordt  A           ________________________________________________________)           Command Qualifiers     Defaultst             /COMMAND           /OUTPUT=file-specA  A           ________________________________________________________             PARAMETERS           keywordh;           Specifies the information to be shown. Acceptablea6           keywords are DATABASE_FILE, HEURISTICS, KEY,@           REJECTIONS, and VERSION. You must specify one of these           keywords.   A           _______________________________________________________              DESCRIPTION >           SHOW DATABASE_FILE displays the name of the database&           file that you are modifying.  =           SHOW KEY displays key definitions. Refer to the DCLl3           SHOW KEY command for further information.i  ?           SHOW REJECTIONS displays the entries in the rejectione>           database, inculding their reference counts, the date=           and time they were entered in the database, and theM?           date and time they were last used by the SMTP server.   @           SHOW VERSION displays the version of MX running on the           system.d             REJMAN-30_ _  _    A                                                   REJMAN CommandsSA                                                              SHOW       A           ________________________________________________________             QUALIFIERS           /COMMAND<           Formats the output as REJMAN commands. This can be<           used with the /OUTPUT qualifier to create a REJMAN?           command file to re-create the rejection database from_           scratch.             /OUTPUT=file-spec_<           Directs the displayed information to the specified>           file. By default, output is displayed on the current9           standard output device (based on the SYS$OUTPUT            logical name).                                                      A                                                         REJMAN-31                     REJMAN Commandsc           SPAWNn        A           ________________________________________________________             SPAWN_             Spawns a subprocess.  A           _______________________________________________________c             FORMAT             SPAWN  [dcl-command]  A           _______________________________________________________              PARAMETERS           dcl-command <           A DCL command to be executed in the subprocess. If:           omitted, REJMAN is suspended and the terminal is=           attached to the subprocess for interactive entry ofi@           commands. To return to the process running REJMAN, use7           the DCL LOGOUT command to end the subprocess.   A           _______________________________________________________a             DESCRIPTION_=           This command creates a subprocess to execute one or ;           more DCL commands. See the description of the DCLE0           SPAWN command for further information.                                   REJMAN-32e                       K           _________________________________________________________________t             Index   )           _______________________________ ?           A                                  HDR_INFO file,10-2I  L           _______________________________    _______________________________.           address-rewriting rules,3-1        JL           Alias,3-4                          _______________________________  @           _______________________________    JNET_INFO file,10-2A           B                                  JNET_INPUT file,10-3   L           _______________________________    _______________________________.           BITEARN.NODES file,4-5,  4-6       LL           BSMTP,4-9                          _______________________________  A           _______________________________    LOCAL_INFO file,10-2_:           C                                  Logical namesF           _______________________________     MAIL$PROTOCOL_prefix,5-2B           component names,11-1                MX_DNSMTP_DEBUG,10-5I                                               MX_DNSMTP_SERVER_DEBUG,10-6eG           _______________________________     MX_ENVELOPE_FROM_HOST,5-3tF           D                                   MX_EVENT_OPER_CLASS,3-5,5           _______________________________        4-11dC           Debugging,10-4                      MX_FLQ_CHECK_WAIT,6-2e?           DEFINE PATH,3-2                     MX_FLQ_DEBUG,10-5m<           delivery path,3-2                   MX_FLQ_DIR,1-4I           DNSMTP_INFO file,10-2               MX_FLQ_MGR_WAKEUP_INTERVAL,l4           DOMAIN.NAMES file,3-3,  4-5,           6-2C              4-8                              MX_FLQ_PURGE_WAIT,6-3s>           Domain/path mapping,MCP-29          MX_FROM_HOST,5-3@                                               MX_JNET_DEBUG,10-5>           _______________________________     MX_JNET_NODE,4-4  A           F                                   MX_LOCAL_DEBUG,10-5e?           _______________________________     MX_LSV_DEBUG,10-5dH           File server,MCP-10                  MX_MAILSHR_IGNORE_8BIT,5-4?                                               MX_MLF_DEBUG,10-5TD           _______________________________     MX_PROTOCOL_PREFIX,5-3  C           H                                   MX_RESTRICT_USAGE,5-1hB           _______________________________     MX_ROUTER_DEBUG,10-5  K                                                                     Index-1                     Index           B           Logical names (cont'd)             MCP commands (cont'd)  A             MX_ROUTER_WAKEUP_INTERVAL,        QUEUE CREATE,MCP-41_A                6-2                            QUEUE EXTEND,MCP-42s@             MX_SHUTDOWN,4-10                  QUEUE PURGE,MCP-43@             MX_SITE_DEBUG,10-6                QUEUE READY,MCP-44?             MX_SMTP_DEBUG,10-5                QUEUE SHOW,MCP-45_E             MX_SMTP_SERVER_DEBUG,10-5         QUEUE STATISTICS,MCP-49sF             MX_SMTP_SERVER_THREADS,5-4        QUEUE SYNCHRONIZE,MCP-509             MX_UUCP_DEBUG,10-6                QUIT,MCP-51 ;             MX_UUCP_REWRITE,4-9               REMOVE,MCP-52 :             MX_UUCP_RMAIL_DEBUG,10-5          RESET,MCP-53;             MX_XSMTP_DEBUG,10-6               REVIEW,MCP-55_9             MX_XSMTP_SERVER_DEBUG,10-6        SAVE,MCP-56 D           _______________________________     SET DECNET_SMTP,MCP-57=                                               SET JNET,MCP-59_>           M                                   SET LOCAL,MCP-62<           _______________________________     SET MLF,MCP-66?           Mail exchanger,4-2                  SET ROUTER,MCP-68R=           Mailing lists,MCP-16                SET SITE,MCP-70d=           MAILQUEUE utility,9-2               SET SMTP,MCP-71 A           MCP commands                        SET X25_SMTP,MCP-75 9             @,MCP-5                           SHOW,MCP-77i=             ATTACH,MCP-6                      SHUTDOWN,MCP-79 :             DEFINE/KEY,MCP-8                  SPAWN,MCP-81;             DEFINE ALIAS,MCP-9                STATUS,MCP-82M6             DEFINE FILE_SERVER,MCP-10        MLF agent=             DEFINE INSIDE_NETWORK_ADDRESS     settings,MCP-66U?                ,MCP-14                       MLFAKE utility,9-1 ?             DEFINE LIST,MCP-16               MLF_INFO file,10-2 ?             DEFINE LOCAL_DOMAIN,MCP-27       MSG_TEXT file,10-2_B             DEFINE PATH,3-2,  MCP-29         MX___STARTUP.COM,11-1F             DEFINE REWRITE_RULE,MCP-31       MXBITNET.MAILERS file,4-7E             DEFINE SYSTEM_USERS,MCP-33       MX Control Program,MCP-3pB             EXIT,MCP-35                      MX_DECODE utility,9-3;             HELP,MCP-36                      MX_MAILSHR,5-1l>             MODIFY,MCP-37                    MX_START.COM,11-1             QUEUE CANCEL,MCP-38 !             QUEUE COMPRESS,MCP-39              Index-2          K                                                                       Index           D           MX_STARTUP.COM,11-1                startup components,11-1  L           _______________________________    _______________________________  .           N                                  TL           _______________________________    _______________________________<           NETDATA format,4-5,  4-7           Trace logs,10-4L           next hop,3-2                       _______________________________  .           _______________________________    U  L           P                                  _______________________________6           _______________________________    Utilities;           Percent-hack,3-4                    MAILQUEUE,9-2 8           Process names,10-3                  MLFAKE,9-1;           _______________________________     MX_DECODE,9-3sJ                                              UUCP rewrite rules, using,4-9@           Q                                  UUCP_INFO file,10-2)           _______________________________ L           Queue files,10-1                   _______________________________  .           Queue file types,10-2              VL           Queue status,6-4                   _______________________________5           _______________________________    VMS MAILeB                                               foreign protocol,5-2A           R                                   protocol prefix,5-2mC           _______________________________     restricting usage,5-1 )           rewrite rules,3-1,  4-9, MCP-31 L                                              _______________________________.           _______________________________    X  L           S                                  _______________________________H           _______________________________    XMAILER.NAMES file,4-5, 4-8A           Shutting down MX,4-10              XSMTP_INFO file,10-2            SITE_INFO file,10-2_!           SMTP default router,4-2 #           SMTP local domains,MCP-27i           SMTP_INFO file,10-2            SRC_INFO file,10-2%           startup command procedures,t              11-1R  K                                                                     Index-3 