The following sections describe the steps necessary to set up the mail server.
4.3.2.1 Setting up the channel
The first step to take in activating the mail server is to add an
appropriate channel entry to your PMDF configuration file. The channel
table entry should have the form:
mailserv logging mailserv-daemonThe
logging keyword can be removed if you don't care about
logging usage of your mail server.
A couple of alias entries also need to be added to the PMDF alias file. They should look like this:
mailserv: mailserv@MAILSERV-DAEMON mailserv-reply: postmaster
The first alias will route mail sent to the mail server on your local
host to the MAILSERV channel. The second alias will route any bounced
messages (the return address of MAILSERV replies is
mailserv-reply@local-host-name unless overridden
by the MAILSERV_REPLY channel option) to the Postmaster. This will
hopefully prevent any mail loops.
An option file can also be specified, if desired. The name of this file
should be mailserv_option stored in the PMDF table
directory, hence usually the file
PMDF_TABLE:mailserv_option. on OpenVMS or
/pmdf/table/mailserv_option on UNIX or
C:\pmdf\table\mailserv_option on NT. The available options
are:
COMMAND_LIMIT (integer >= -1)
This option specifies the maximum number of commands allowed in a single message to the MAILSERV channel. Any commands beyond the limit will not be processed. When a value of -1 is specified, no limit will be imposed. This is the default.LIST_MAPPING_FLAGS (integer)
The new LIST_MAPPING_FLAGS channel option controls the format of the MAILSERV_LISTS mapping table probe. This option takes a bit-encoded value. The default value is 0, meaning that the mapping probe consists simply of the list name. Bit 0 (value 1), if set, prepends the subscribee address and a vertical bar to the mapping probe. Bit 1 (value 2), if set, prepends the address used to send the request to MAILSERV and a vertical bar to the mapping probe.MAILSERV_PERSONAL (string <= 252 characters long)
This option specifies the contents of the personal name field used in From: headers of messages generated by the MAILSERV channel. When specifying a personal name field to use, there is no need to enclose the field in quotes; e.g., it is valid to specifyMAILSERV_PERSONAL=Don't fence me inMAILSERV_REPLY (address <= 252 characters long)
By default, MAILSERV will generate a reply address ofmailserv-reply@local-hostin all messages which it generates.local-hostis here the official local host name of the system running the MAILSERV channel.) This default can be overridden with the MAILSERV_REPLY option which may be used to specify an alternate address. Note that list-specific defaults may also be established via the MAILSERV_LISTS mapping table; see Section 4.3.5 .MAXBLOCKS (integer >= -1)
Specifies the maximum number of blocks of data in a single message back from the server. Any response requiring more blocks will be broken into multiple messages, no single part exceeding this limit. MIME's message/partial mechanism is used to "fragment" the message into multiple messages. When a value of -1 is specified, no limit is imposed. This is the default. Note that the size of a block is controlled with the PMDF BLOCK_SIZE option presented in Section 7.1 . By default, a block is 1024 bytes.MAXLINES (integer >= -1)
Specifies the maximum number of lines of data in a single message back from the server. Any response requiring more lines will be broken into multiple messages, no single part exceeding this limit. MIME's message/partial mechanism is used to "fragment" the message into multiple messages. When a value of -1 is specied, no limit is imposed. This is the default.
4.3.2.2 Directories, logical names, and basic files on OpenVMS
The mail server uses two directories: a file directory (with optional
subdirectories) and a mailing list directory.
On OpenVMS, the file directory is located by the PMDF_MAILSERV_FILES_DIR logical name. This is normally a rooted logical name that points to the top directory of the set of directories containing the files that the mail server can distribute. A command such as one of the following might be used to define the logical name:
$ define/system/translate=conceal pmdf_mailserv_files_dir disk4:[mailserv.files.] $ define/system/translate=conceal pmdf_mailserv_files_dir disk2:[mailserv.] $ define/system/translate=conceal pmdf_mailserv_files_dir disk3:Note that the logical name must either be a rooted reference or a reference to an entire device.
PMDF does not define this logical name itself. It should be defined
during system startup immediately after the PMDF startup procedure has
been run. This definition should not be placed in the PMDF supplied
startup procedure, pmdf_startup.com, as that procedure is
replaced when PMDF is updated and any local changes made to it will be
lost. A convenient place to put these logical definitions is in the
optional site-supplied PMDF_COM:pmdf_site_startup.com file
which, as discussed in the PMDF Installation Guide, OpenVMS Edition , will be executed
automatically, if it exists, by the regular PMDF startup procedure.
The file mailserv_help.sample provided in the PMDF table
directory should be copied to the PMDF_MAILSERV_FILES_DIR directory and
given the name help.txt. This file describes the commands
the mail server understands. It can be modified to include
site-specific information if desired. There is no imposed structure for
the file help.txt.
The file mailserv_index.sample provided in the PMDF table
directory should be revised to reflect the files MAILSERV can provide.
Once revised, it should be copied to the PMDF_MAILSERV_FILES_DIR
directory and given the name index.txt. There is no
imposed structure for the file index.txt.
The second directory is where mailing list files are kept. This directory is located with the PMDF_MAILSERV_MAIL_DIR logical name. This logical name refers to a single directory; it must not be a rooted logical name. A command such as one of the following might be used to define this logical name:
$ define/system pmdf_mailserv_mail_dir disk2:[mailserv.maillist] $ define/system pmdf_mailserv_mail_dir disk1:[maillists] $ define/system pmdf_mailserv_mail_dir disk7:[users.maillists]PMDF does not define this logical name itself. It should be defined during system startup immediately after the PMDF startup procedure has been run. The mailing list services of the mail server will be disabled if this logical name is not defined. Again, this definition should not be placed in the startup procedure supplied by PMDF as that procedure is replaced when PMDF is updated and any changes made to it will be lost.
A file lists.txt should be created and placed in the
PMDF_MAILSERV_MAIL_DIR directory. This file should list the mailing
lists the mail server handles and should give a brief description of
each list. There is no imposed structure for the file
lists.txt; it is simply an ordinary text file.
At this point the mail server should be usable. Try it out by sending some requests to MAILSERV on the local host and seeing what responses you get.
4.3.2.3 Directories and basic files on UNIX
The mail server uses two directories: a file directory (with optional
subdirectories) and a mailing list directory.
On UNIX, the PMDF tailor file option PMDF_MAILSERV_FILES_DIR normally
points to /pmdf/mailserv/files and the PMDF tailor file
option PMDF_MAILSERV_MAIL_DIR normally points to
/pmdf/mailserv/mail. (Note that if you change these tailor
file options, your changes will be lost next time you upgrade PMDF.)
These two directories should be created and set to be owned by the
pmdf account, e.g.,
# mkdir -m755 /pmdf/mailserv # chown pmdf /pmdf/mailserv # mkdir -m755 /pmdf/mailserv/files # chown pmdf /pmdf/mailserv/files # mkdir -m755 /pmdf/mailserv/mail # chown pmdf /pmdf/mailserv/mail
The file mailserv_help.sample provided in the PMDF table
directory should be copied to the PMDF_MAILSERV_FILES_DIR directory and
given the name help.txt. This file describes the commands
the mail server understands. It can be modified to include
site-specific information if desired. There is no imposed structure for
the file help.txt.
The file mailserv_index.sample provided in the PMDF table
directory should be revised to reflect the files MAILSERV can provide.
Once revised, it should be copied to the PMDF_MAILSERV_FILES_DIR
directory and given the name index.txt. There is no
imposed structure for the file index.txt.
A file lists.txt should be created and placed in the
PMDF_MAILSERV_MAIL_DIR directory. This file should list the mailing
lists the mail server handles and should give a brief description of
each list. There is no imposed structure for the file
lists.txt; it is simply an ordinary text file.
At this point the mail server should be usable. Try it out by sending some requests to MAILSERV on the local host and seeing what responses you get.
4.3.2.4 Directories and basic files on NT
The mail server uses two directories: a file directory (with optional
subdirectories) and a mailing list directory.
On NT, the Registry entry PMDF_MAILSERV_FILES_DIR normally points to
C:\pmdf\mailserv\files\ and the Registry entry
PMDF_MAILSERV_MAIL_DIR normally points to
C:\pmdf\mailserv\mail\. These two directories are created
by the PMDF installation procedure.
The file mailserv_help.sample provided in the PMDF table
directory should be copied to the PMDF_MAILSERV_FILES_DIR directory and
given the name help.txt. This file describes the commands
the mail server understands. It can be modified to include
site-specific information if desired. There is no imposed structure for
the file help.txt.
The file mailserv_index.sample provided in the PMDF table
directory should be revised to reflect the files MAILSERV can provide.
Once revised, it should be copied to the PMDF_MAILSERV_FILES_DIR
directory and given the name index.txt. There is no
imposed structure for the file index.txt.
A file lists.txt should be created and placed in the
PMDF_MAILSERV_MAIL_DIR directory. This file should list the mailing
lists the mail server handles and should give a brief description of
each list. There is no imposed structure for the file
lists.txt; it is simply an ordinary text file.
At this point the mail server should be usable. Try it out by sending some requests to MAILSERV on the local host and seeing what responses you get.