PMDF System Manager's Guide
PMDF-REF-6.0

Previous | Contents

Preface

Purpose of this Manual

This manual describes the structure, configuration, and use of PMDF. The intended audience is system managers who wish to become familiar with how PMDF operates. In particular, this document describes many customizable parts of PMDF that can be altered to adapt PMDF to a particular environment. The reader is assumed to be quite familiar with networking concepts and the operating system on which PMDF is to be installed.

This manual does not provide a description of PMDF suitable for end users; end users should refer to the appropriate edition of the PMDF User's Guide .

Overview of this Manual

This guide is a long and technical document. If you are new to PMDF, you should skim the entire document, skipping the discussion in Part 3 of those PMDF layered products which you will not be installing, as well as the channels described in Chapters 17 --27 for which you do not have any use. Once you are somewhat familiar with PMDF you can then perform the installation described in the appropriate edition of the PMDF Installation Guide , referring back to this manual as needed.

PMDF is a large and complex package capable of being configured to meet almost any task. If your site is typical of most, the initial configuration generated by the configuration utilities will suffice to get you up and running in a minimal amount of time. After you have an initial configuration, study it and use it as an example as you read the following chapters. As you become comfortable with PMDF, you will find that you want to make changes here and there, modify the behavior of some channels, or even add additional channels to your configuration. Or perhaps you will want to set up some databases, or implement a centralized naming system. By all means do so.¹ PMDF, as you will find, has quite a few knobs and switches which you can manipulate and more often than not you'll discover that there are not one but several means of dealing with a given issue. If anything, PMDF is too flexible.

This manual consists of three volumes, together comprising forty-two chapters:

Suggested starting points in this manual

PMDF includes a spectrum of features; the precise features of interest will vary greatly from site to site. A first reading of this manual might focus on a careful reading of Chapter 1 and Chapter 33 , and then skimming Section 2.2 (omitting Section 2.2.6 on first reading), Section 2.3.1 , Section 2.3.2 , Section 2.4 , Section 3.1 , the beginning of Chapter 5 , Chapter 8 , the beginning of Chapter 9 (for OpenVMS sites) or Chapter 10 (for UNIX sites), the beginning of Chapter 11 , if using POP or IMAP then Chapter 13 , any channels discussed in Chapter 17 through Chapter 27 which you will be using (with particular attention to Chapter 23 discussing TCP/IP channels which are one of the most important sorts of channels for most sites), and Section 32.1 .

Mail user agents

This manual focuses on PMDF's function as a Message Transfer Agent (MTA), to provide a uniform message distribution network that can be interfaced to multiple user interfaces (Mail User Agents, or MUA's). For further information on user interfaces, see documentation for that user agent, or the appropriate edition of the PMDF User's Guide . For instance:
On OpenVMS systems, PMDF uses the standard VMS MAIL facility as its primary user interface. PMDF also supplies a VMS MAIL-compatible user interface of its own, PMDF MAIL. PMDF MAIL is an extension of VMS MAIL which better understands network messaging (e.g., supports RFC 822 and MIME) and uses the same message store as VMS MAIL. PMDF Pine, a port of the popular UNIX mail user agent Pine to OpenVMS, is also supplied as part of PMDF for OpenVMS and also uses the same message store as VMS MAIL. Information on PMDF MAIL and the OpenVMS-specific implementation details of PMDF Pine may be found in the OpenVMS Edition of the PMDF User's Guide . PMDF also supports Gold-Mail. The optional layered product PMDF-MR provides transparent support for MAILbus agents such as ALL-IN-1 and A1MAIL.

On UNIX systems, PMDF can use as its mail user interface any such interface which normally submits its messages using sendmail or SMTP. For convenience, the PMDF distribution includes a copy of one such mail user interface for UNIX, the University of Washington's Pine.

Availability

PMDF software products are marketed directly to end users in North America, and either directly or through distributors in other parts of the world depending upon the location of the end user. Contact Innosoft for ordering information, to include referral to an authorized distributor where applicable:

Credits

PMDF was originally developed by Ira Winston of the Department of Computer and Information Science at the University of Pennsylvania, Ned Freed of the Department of Mathematics at Oklahoma State University, Mark Vasoll of the Department of Computer and Information Sciences at Oklahoma State University, and Kevin Carosso of the Space and Communications Group of Hughes Aircraft. Further development of PMDF is now being coordinated by Innosoft International, Inc. Contributors include Todd Aven, who contributed the MAKE facility used to build PMDF; Scott Ballew, who developed PMDF's logging facility; Goran Bengtson, who developed an SMTP over X.25 channel; Dennis Boylan, who developed the original UUCP channel programs; John Carosso, who developed much of the early BITNET support; Gerson Cohen, who developed the original support for ANJE; Mike Iglesias, who provided numerous command files and other enhancements; Warwick Jackson, who developed several channel programs; Matts Kallioniemi, who provided many enhancements; Pekka Kytolaakso, who provided enhancements to BSMTP for BITNET channels; Marc Shannon, who provided enhancements to the Jnet channel; Robert Smart, who provided numerous enhancements to the PMDF interface to VMS MAIL; Larry Snodgrass, who contributed to the BITNET documentation; Klaus Steinberger, who enhanced generation of PMDF configuration information from BITNET NAMES files; Robert Stodola, who implemented the original MX record lookup support for the CMU-Tek TCP/IP channel; Don Stokes, who enhanced the DEC/Shell UUCP channel to support DECUS UUCP; Mike Sullenberger, who provided additional command file enhancements; Bob Tinkelman, who provided additional command file enhancements; Gregg Wonderly, who developed the CTLSMB detached process symbiont and provided many enhancements as well; and Craig Watkins who provided the low level IXO interaction routines for the pager channels.

The development of PMDF would not have been possible without the enthusiastic support of the PMDF user community, and the developers of PMDF would like to thank the many users of PMDF (both the contributors listed above as well as others too numerous to list here) for their help and suggestions that have helped to make PMDF a better product.

Note

¹ There are, of course, some problems best left alone or for which what seems the obvious solution is not really a good one. When in doubt just ask.

Previous | Next | Contents