PMDF System Manager's Guide
Total Page:16
File Type:pdf, Size:1020Kb
PMDF System Manager’s Guide Order Number: N-5301-66-NN-N February 2020 This document describes the configuration and usage of version 6.8 of the PMDF, PMDF- MTA, and PMDF-TLS software. Revision/Update Information: This manual supersedes the V6.7 PMDF System Man- ager’s Guide Software Version: PMDF V6.8 Operating System and Version: Red Hat Enterprise Linux 7 or later on x86_64; (or other compatible Linux distribution) OpenVMS Alpha V7.3-2 or later; OpenVMS I64 V8.2 or later; Copyright ©2020 Process Software, LLC. Unpublished — all rights reserved under the copyright laws of the United States No part of this publication may be reproduced, 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 without the prior written permission of: Process Software, LLC 959 Concord Street Framingham, MA 01701-4682 USA Voice: +1 508 879 6994; FAX: +1 508 879 0042 [email protected] Process Software, LLC (‘‘Process’’) makes no representations or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Furthermore, Process Software reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of Process Software to notify any person of such revision or changes. Use of PMDF, PMDF-MSGSTORE, PMDF-MTA, and/or PMDF-TLS and associated documentation is authorized only by a Software License Agreement. Such license agreements specify the number of systems on which the software is authorized for use, and, among other things, specifically prohibit use or duplication of software or documentation, in whole or in part, except as authorized by the Software License Agreement. Restricted Rights Legend 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 as set forth in the Commercial Computer Software — Restricted Rights clause at FAR 52.227-19. The PMDF mark and all PMDF-based trademarks and logos are trademarks or registered AlphaMate is a registered trademark of Motorola, Inc. trademarks of Sun Microsystems, Inc. in the United States and other countries and are used under license. ALL-IN-1, Alpha AXP, AXP, Bookreader, DEC, DECnet, HP, I64, IA64, Integrity, MAILbus, cc:Mail is a trademark of cc:Mail, Inc., a wholly-owned subsidiary of Lotus MailWorks, Message Router, MicroVAX, OpenVMS, Pathworks, PSI, RMS, TeamLinks, Development Corporation. Lotus Notes is a registered trademark of Lotus TOPS-20, Tru64, TruCluster, ULTRIX, VAX, VAX Notes, VMScluster, VMS, and WPS- Development Corporation. PLUS are registered trademarks of Hewlett-Packard Company. AS/400, CICS, IBM, Office Vision, OS/2, PROFS, and VTAM are registered trademarks RC2 and RC4 are registered trademarks of RSA Data Security, Inc. of International Business Machines Corporation. CMS, DISOSS, OfficeVision/VM, OfficeVision/400, OV/VM, and TSO are trademarks of International Business Machines Corporation. dexNET is a registered trademark of Fujitsu Imaging Systems of America, Inc. Ethernet is a registered trademark of Xerox Corporation. FaxBox is a registered trademark of DCE Communications Group Limited. GIF and ‘‘Graphics Interchange Format’’ are trademarks of CompuServe, Incorporated. InterConnections is a trademark of InterConnections, Inc. InterDrive is a registered trademark of FTP Software, Inc. LANmanager and Microsoft are registered trademarks of Microsoft Corporation. Memo is a trade mark of Verimation ApS. MHS, Netware, and Novell are registered trademarks of Novell, Inc. LaserJet and PCL are registered trademarks of Hewlett-Packard Company. PGP and Pretty Good Privacy are registered trademarks of Pretty Good Privacy, Inc. Jnet is a registered trademark of Wingra, Inc. Attachmate is a registered trademark and PathWay is a trademark of Attachmate Pine and Pico are trademarks of the University of Washington, used by Corporation. permission. PostScript is a registered trademark of Adobe Systems Incorporated. Solaris, Sun, and SunOS are trademarks of Sun Microsystems, Inc. SPARC is a trademark of SPARC International, Inc. TCPware and MultiNet are registered trademarks of Process Software. UNIX is a registered trademark of UNIX System Laboratories, Inc. TIFF is a trademark of Aldus Corporation. Gold-Mail is a trademark of Data Processing Design, Inc. Copyright (c) 1990-2000 Sleepycat Software. All rights reserved. libedit/editline is Copyright (c) 1992, 1993, The Regents of the University of California. All rights reserved. Contents PREFACE xlvii Volume I CHAPTER 1 STRUCTURE AND OVERVIEW 1–1 1.1 THE STRUCTURE OF PMDF 1–1 1.2 THE PMDF CONFIGURATION FILE: CHANNELS AND REWRITE RULES 1–4 1.2.1 Channels 1–6 1.2.2 Domain Rewriting Rules 1–7 1.3 ENABLING PMDF TO RECEIVE MESSAGES 1–7 1.4 PROCESSING JOBS 1–7 1.4.1 Immediate Message Submission Jobs 1–8 1.4.2 Manually Starting an Immediate Message Submission Job 1–8 1.4.3 The Periodic Message Delivery Retry Job 1–9 1.4.3.1 Adjusting Periodic Delivery Retry Job Frequency • 1–10 1.4.3.2 Clean Up Tasks Performed by the Periodic Delivery Job • 1–11 1.4.4 Returning Undeliverable Messages 1–11 1.4.4.1 Adjusting Return Job Frequency • 1–12 1.4.4.2 Clean Up Tasks Performed by the Return Job • 1–13 1.4.5 Managing Processing Job Execution on OpenVMS 1–14 1.4.6 Running Processing Jobs Under a Username Other than SYSTEM on OpenVMS 1–15 1.5 STORAGE OF MESSAGE FILES ON DISK 1–15 1.5.1 Channel Queue Formats 1–16 1.5.2 Message File Structure 1–17 1.6 OTHER IMPORTANT FILES 1–18 1.7 INSTALLATION ENVIRONMENT: LOGICALS (OpenVMS), TAILOR FILE (UNIX), REGISTRY (NT) 1–21 1.8 COMPLIANCE WITH STANDARDS 1–22 CHAPTER 2 THE CONFIGURATION FILE: DOMAIN REWRITE RULES & THE CHANNEL/HOST TABLE 2–1 2.1 STRUCTURE OF THE CONFIGURATION FILE 2–1 2.1.1 Blank Lines in the Configuration File 2–2 2.1.2 Comments in the Configuration File 2–2 2.1.3 Continuation Lines in the Configuration File 2–2 2.1.4 Including Other Files in the Configuration File 2–2 2.2 DOMAIN REWRITING RULES 2–3 iii Contents 2.2.1 The Purpose of Domain Rewriting Rules 2–3 2.2.2 Location and Format of Domain Rewriting Rules 2–3 2.2.3 Application of Domain Rewriting Rules to Addresses 2–4 2.2.3.1 Extraction of the First Host/domain Specification • 2–5 2.2.3.2 Scanning the Rewrite Rules • 2–6 2.2.3.3 Applying the Rewrite Rule Template • 2–8 2.2.3.4 Finishing the Rewriting Process • 2–8 2.2.3.5 Rewrite Rule Failure • 2–9 2.2.3.6 Syntax Checks After Rewriting • 2–9 2.2.3.7 Handling of Domain Literals • 2–9 2.2.4 Patterns and Tags 2–10 2.2.4.1 A Rule to Match Percent Hacks • 2–12 2.2.4.2 A Rule to Match Bang-style (UUCP) Addresses • 2–12 2.2.4.3 A Rule to Match Any Address • 2–12 2.2.4.4 Tagged Rewrite Rule Sets • 2–12 2.2.5 Templates 2–13 2.2.5.1 Ordinary Rewriting Templates, A@B or A%B@C • 2–14 2.2.5.2 Repeated Rewritings Template, A%B • 2–14 2.2.5.3 Specified Route Rewriting Templates, A@B@C or A@B@C@D • 2–14 2.2.5.4 Case Sensitivity in Rewrite Rule Templates • 2–15 2.2.6 Template Substitutions and Rewrite Rule Control Sequences 2–15 2.2.6.1 Username and Subaddress Substitution, $U, $0U, $1U • 2–17 2.2.6.2 Host/domain and IP Literal Substitutions, $D, $H, $nD, $nH, $L • 2–17 2.2.6.3 Literal Character Substitutions, $$, $%, $@ • 2–18 2.2.6.4 LDAP Query URL Substitutions, $]...[ • 2–18 2.2.6.5 General Database Substitutions, $(...) • 2–19 2.2.6.6 Apply Specified Mapping, ${...} • 2–19 2.2.6.7 Customer-supplied Routine Substitutions, $[...] • 2–20 2.2.6.8 Single Field Substitutions, $&, $!, $*, $# • 2–21 2.2.6.9 Unique String Substitutions • 2–21 2.2.6.10 Source Channel-specific Rewrite Rules, $M, $N • 2–22 2.2.6.11 Destination Channel-specific Rewrite Rules, $C, $Q • 2–23 2.2.6.12 Direction and Location-specific Rewrites, $B, $E, $F, $R • 2–23 2.2.6.13 Host Location-specific Rewrites, $A, $P, $S, $X • 2–24 2.2.6.14 Changing the Current Tag Value, $T • 2–24 2.2.6.15 Controlling Error Messages Associated with Rewriting, $? • 2–25 2.2.7 Rewrite Rules Example 2–26 2.2.8 Testing Domain Rewriting Rules 2–27 2.2.9 Handling Large Numbers of Rewrite Rules 2–28 2.2.10 Using Rewrites to Illegal Addresses 2–30 2.2.11 Other Address Manipulations 2–31 2.3 THE CHANNEL/HOST TABLE 2–31 2.3.1 Overview 2–31 2.3.2 Channel Definitions: the Channel/host Table 2–32 2.3.2.1 First Line: Channel Name and Keywords • 2–32 2.3.2.2 Second Line: System Name and Local Host Alias • 2–32 2.3.2.3 Additional Lines: Systems Reachable via the Channel • 2–33 iv Contents 2.3.3 Envelope vs. Header Addresses: Channel-level Name Translations 2–34 2.3.4 Channel Table Keywords 2–35 2.3.4.1 Address Types and Conventions (822, 733, uucp, header_822, header_733, header_uucp) • 2–59 2.3.4.2 Address Interpretation (bangoverpercent, nobangoverpercent) • 2–60 2.3.4.3 Routing Information in Addresses (exproute, noexproute, improute, noimproute) • 2–60 2.3.4.4 Short Circuiting Rewriting of Routing Addresses (routelocal) • 2–61 2.3.4.5 Address Rewriting Upon Message Dequeue (connectalias, connectcanonical) • 2–61 2.3.4.6 Channel-specific Rewrite Rules (rules, norules) • 2–62 2.3.4.7 Channel Directionality (master, slave, bidirectional) • 2–62 2.3.4.8 Channel Operation Type (submit) • 2–62 2.3.4.9 Channel Service Periodicity (immediate, immnonurgent, immnormal, immurgent, periodic, period) • 2–62 2.3.4.10 Message Size Affecting Priority (urgentblocklimit,