PMDF provides a combined mail and list server, referred to in
this document as a "mail server". Mail servers are used to
distribute files via e-mail and allow users to subscribe or
unsubscribe from mailing lists. If your system manager has
configured a mail server at your site, then you can query the
server via e-mail to determine what files and mailing lists are
available.
1 – Using Servers
Commands directed to a mail server take the form of a mail
message addressed to
mailserv@mail-server-host
where MAIL-SERVER-HOST is the host name of the machine running
the mail server. You need to obtain this name from your system
manager. The text of the message contains mail server commands,
one command per line.
For example, suppose the address of a mail server is
mailserv@example.com. To obtain a help message from the server
as well as a list of the available files and mailing lists, you
would send a message much like the one shown below.
Example 1 Sending Commands to a Mail Server
$ MAIL
MAIL> SEND
To: in%"mailserv@example.com"
Subj:
Enter your message below. Press CTRL/Z when complete, CTRL/C to quit:
HELP
INDEX
LISTS
<CTRL/Z>
MAIL> EXIT
$
After a short while, you will receive back three messages from
the mail server: the first message in response to the HELP
command, the second in response to the INDEX command, and
the third in response to the LISTS command. If your command
specifications are in error, then the mail server will send you
an error notification.
Typically, mail from the mail server will have a reply address
which differs from the address you use to send commands to
it. This is intentional and is done to prevent potential mail
loops. One consequence of this is that you cannot direct further
commands to the server by replying to messages from it. You must
always initiate a new message with the send command; you cannot
use the reply command.
A brief description of the available commands is given in the
table below; complete descriptions are described under the
"Commands" subtopic. Lines beginning with an exclamation point,
!, are interpreted as comment lines.
Table 2 Summary of Mail and List Server Commands
Command Description
CONFIRM Confirm a command from a previous message
DIRECTORY Obtain directory listing of available files
DIRECTORY/LIST Obtain directory listing of available mailing
lists
ENCODING Set default file transmission encoding
END Terminate processing, accept no additional
commands
EXIT (see END) Same as END
FINISH (see Same as END
END)
HELP Retrieve the server-specific help information
INDEX Retrieve the index of available files
LISTS Retrieve the index of available mailing lists
MAXIMUM Set maximum message size; large messages will be
divided into several messages, each smaller than
this size
MODE Set the default file reading mode
PURGE/LIST Purge comment lines (such as unsubscribed
addresses) from the membership list
QUIT (see END) Same as END
SEND Retrieve the specified files
SEND/LIST Retrieve the membership list for a given mailing
list
SEND/LIST/COMMENTRetrieve the membership list for a given mailing
(see SEND/LIST) list, including members' RFC 822 comment fields
SEND/LIST/NOCOMMERetrieve the membership list for a given mailing
(see SEND/LIST) list, stripping members' RFC 822 comment fields
STOP (see END) Same as END
SUBSCRIBE Subscribe to a mailing list
UNSUBSCRIBE Unsubscribe from a mailing list
2 – Commands
Note that while there is a fair amount of commonality amongst
the commands accepted by many of the different mail servers,
differences also exist. Do not expect PMDF mail server commands
to work with other mail servers and do not expect other mail
server commands to work with PMDF mail servers. When you are
unsure of what sort of mail server you are dealing with, the
first order of business should be obtaining help information for
that server. Often this can be done by sending the command HELP
to the server.
2.1 – CONFIRM
Confirm a command from a previous message.
Syntax
CONFIRM cookie
2.1.1 – Parameters
cookie
Required cookie string to confirm the command.
2.1.2 – Description
The CONFIRM command is used to confirm for MAILSERV the execution
of a command from a previous message.
That is, for security your system administrators might have
configured MAILSERV to require confirmation of certain commands.
If you receive a message from MAILSERV saying that you need to
send a
CONFIRM cookie-string
message back to MAILSERV in order for it to perform some
particular command you previously requested, then if you want
that command executed you must send back exactly
CONFIRM cookie-string
where COOKIE-STRING is the exact string MAILSERV tells you to
send for that command.
Note that you should send a new message back to MAILSERV
containing the required CONFIRM command, rather than simply
resending or bouncing MAILSERV's own message back to MAILSERV (to
ensure that you hear about any errors in processing your CONFIRM
command).
Note that if you receive a message from MAILSERV talking about
confirming a command that you did not send yourself, then that
might mean that someone is attempting masquerade as you in
e-mail and you might want to take this up with your system
administrators.
2.1.3 – Error messages
%MAILSERV-F-NOCOOKIE, There is no confirmation-
pending command labelled
There was no command corresponding to such a cookie string
awaiting confirmation. Check that you entered the cookie
correctly.
2.2 – DIRECTORY
Obtain a directory listing of the available files.
Syntax
DIRECTORY [file-spec]
2.2.1 – Parameters
file-spec
Optional file name specification indicating which files to obtain
a directory listing of. All OpenVMS file and directory wild cards
are supported. A directory specification can be used; no device
name or root directory specification is allowed.
2.2.2 – Description
The DIRECTORY command provides a directory listing of the
available files. The listing is returned to you as a mail
message.
The file-spec parameter is optional and, if omitted, defaults
to "*". If you are unsure of what to use, omit the parameter and
send simply the command
DIRECTORY
This will provide you with a list of the files and directories
in the top-level directory of the mail server. You can then
this information to refine your queries; e.g., investigate the
contents of an intriguing directory,
DIRECTORY [GAMES...]
2.2.3 – Error messages
%MAILSERV-W-NOFILES, no files found
The supplied file specification does not match any available
files.
%MAILSERV-F-NOFILESERV, file service is not enabled
The mail server is not configured to operate as a file server.
%MAILSERV-W-WRITEERR, file writing error
An error occurred while the server was producing your directory
listing. Try resending the command at a later time.
2.2.4 /LIST
Obtain a listing of the available mailing lists.
Syntax
DIRECTORY/LIST [list-spec]
2.2.4.1 – Parameters
list-spec
Optional mailing list specification indicating which mailing
lists to obtain a listing of. OpenVMS wild cards are supported.
2.2.4.2 – Description
The DIRECTORY command provides a listing of the available mailing
lists.
The list-spec parameter is optional and, if omitted, defaults to
"*". Generally, there is no need to use this parameter unless you
are interested in a specific mailing list. For instance, if you
merely want to know if there is a mailing list about zeugmes, you
might use the command
DIRECTORY/LIST *ZEUGME*
This will provide you with the names of any mailing lists which
contain the phrase "zeugme" in them. Note that just because a
mailing list is available does not necessarily mean that you can
subscribe to it. The site might have established restrictions
governing who can or cannot subscribe to some or all mailing
lists.
2.2.4.3 – Error messages
%MAILSERV-W-NOLISTS, no lists found
The supplied mailing list specification does not match any
available mailing lists.
%MAILSERV-F-NOMAILLIST, mailing lists are not enabled
The mail server is not configured to operate as a list server.
%MAILSERV-W-WRITEERR, file writing error
An error occurred while the server was producing your listing
of mailing lists. Try resending the command at a later time.
2.3 – ENCODING
Specify the file encoding to use.
Syntax
ENCODING encoding
2.3.1 – Parameters
encoding
Required parameter specifying the file encoding to use. The
available encodings are: 8BIT, 7BIT, BASE32, BASE64, CBASE64
(gzip compressed BASE64), BASE85, BINHEX (encoding only, not
the BINHEX file format), BTOA, HEXADECIMAL, PATHWORKS, QUOTED_
PRINTABLE, UUENCODE, and CUUENCODE (gzip compressed UUENCODE).
2.3.2 – Description
Binary files cannot be transmitted directly as electronic mail;
they must first be encoded into a "printable" format. This,
of course, means that they must be decoded upon receipt. The
ENCODING command is used to specify the encoding to be applied
to files requested with the SEND command. When selecting an
encoding, be sure to select an encoding which you can decode.
If your mail is handled by PMDF, then you can decode any of the
encodings offered by PMDF mail servers.
The encoding specified with the ENCODING command applies to
all subsequent SEND commands in the same message. It can be
overridden with a subsequent ENCODING command or, on a per
command, basis with the SEND command's /ENCODING qualifier. And,
of course, encodings established in previous messages sent to
the server have no effect on subsequent messages which you might
send.
The BASE64 and QUOTED_PRINTABLE encodings are described in RFC
2045 (MIME, Part One). The HEXADECIMAL encoding is a simple
hexadecimal encoding of the data. The data is encoded in 8 bit
byte order. Each 8 bit byte is represented with two characters;
the first character describes the high four bits and the second
describes the low four bits. The UUENCODE encoding is compatible
with the popular UUENCODE and UUDECODE utilities.
BASE64 is usually the best encoding to use: it is most likely
to survive any mangling that might occur as the mail message
works its way through the networks to you (e.g., line wrapping,
character set translation, space stripping, etc.).
2.3.3 – Examples
The commands,
ENCODING BASE64
MODE BLOCK
SEND [.GIF]BOATS*.GIF
SEND/MODE=TEXT [GIF]INDEX.TXT
set the default encoding to BASE64 and the default file
reading mode to BLOCK. Any files matching the specification
[GIF]BOATS*.GIF will be sent using these defaults. However, the
file [GIF]INDEX.TXT will be sent as an ordinary text file owing
to the use of the /MODE=TEXT qualifier.
2.3.4 – Error messages
%MAILSERV-W-INSFPRM, missing command parameters
You failed to supply the name of the encoding to use. Resend
the command with a valid encoding name specified.
%MAILSERV-W-IVKEYW, unrecognized keyword - check validity and spelling
You specified an unknown encoding. Resend the command with a
valid encoding name specified.
2.4 – END
Terminates command processing.
Syntax
END
2.4.1 – Description
The END command and its synonyms EXIT, FINISH, QUIT, and STOP all
cause MAILSERV command processing to be terminated. The remainder
of the message is discarded without any additional processing.
2.5 – HELP
Obtain help on using the mail server.
Syntax
HELP
2.5.1 – Description
The HELP command returns a description of the commands recognized
by the mail server.
2.5.2 – Error messages
%MAILSERV-F-HLPNOTAVA, Help for server is presently unavailable
No help information is currently available. This may or may not
be a temporary condition.
%MAILSERV-W-MAXPARM, too many parameters
You supplied a parameter after the HELP command. The HELP
command does not accept any parameters (e.g., does not take
a "topic" parameter).
2.6 – INDEX
Obtain an index of the available files.
Syntax
INDEX
2.6.1 – Description
The INDEX command returns an index describing the files that the
mail server can provide with the SEND command. This description
might not give the names of each and every available file;
for such information use the DIRECTORY command. The index is,
typically, a simple description of some of the available files
and, perhaps, a description of each of the top-level directories.
2.6.2 – Error messages
%MAILSERV-F-INDNOTAVA, Index for server is presently unavailable
No file index information is currently available. This may
or may not be a temporary condition. Try using the DIRECTORY
command in the meantime.
%MAILSERV-W-MAXPARM, too many parameters
You supplied a parameter after the INDEX command. The INDEX
command does not accept any parameters. Resend the command
without any parameters.
2.7 – LISTS
Obtain an index of the available mailing lists.
Syntax
LISTS
2.7.1 – Description
The LISTS command returns an index describing the mailing lists
that the mail server handles. This description might not give
the names of each and every available mailing list; for such
information use the DIRECTORY/LIST command. The index is, more
often than not, a simple description of the mailing lists handled
by the server. It might also describe any policies associated
with the lists (e.g., who can subscribe, how to post to the list,
etc.).
2.7.2 – Error messages
%MAILSERV-F-LSTNOTAVA, Index of lists is presently unavailable
No mailing list index information is currently available.
This may or may not be a temporary condition. Try using the
DIRECTORY/LIST command in the meantime.
%MAILSERV-F-NOMAILLIST, mailing lists are not enabled
The mail server is not configured to operate as a list server.
%MAILSERV-W-MAXPARM, too many parameters
You supplied a parameter after the LISTS command. The LISTS
command does not accept any parameters. Resend the command
without specifying any parameter.
2.8 – MAXIMUM
Set the maximum message size; larger messages will be split into
several smaller messages.
Syntax
MAXIMUM size-units size-value
2.8.1 – Parameters
size-units
Required parameter specifying the units in which the size-value
is expressed. The possible units are BYTES, BLOCKS, and LINES.
size-value
Required parameter specifying the limiting value. This must be an
integer value which exceeds zero.
2.8.2 – Description
Many gateways impose a limit on the maximum size message they
will process. Because the mail server is often called upon
to transmit large files it frequently can run afoul of such
limitations.
The MAXIMUM command provides a way around such limitations. When
a maximum size is set, messages larger than that size will be
fragmented (split) into multiple messages, each message no larger
than the specified maximum size. The fragmentation scheme is
compliant with the message/partial type described in RFC 2046
(MIME, Part Two).
The possible values for size-units are:
BYTES size-value specifies the maximum number of bytes allowed
in a single message. This value includes the initial
header attached to the message. (Note that the header
can increase in size through the addition of header lines
during routing.)
BLOCKS size-value specifies the maximum number of "blocks" of
bytes allowed in a single message. The size of a block
is a PMDF configuration option controlled by the system
manager with the PMDF BLOCK_SIZE option; its default value
is 1024 bytes. As with BYTES, this value includes the
initial header attached to the message.
LINES size-value specifies the maximum number of lines allowed
in a single message. This limit is independent of the
number of bytes or blocks. It is necessary to have an
independent limit because some gateways limit message size
based on both line count as well as overall size.
The limits specified with the MAXIMUM command apply to all
subsequent SEND commands in the same message. The imposed limits
can be overridden with a subsequent MAXIMUM command. And, of
course, limits you imposed in previous messages sent to the
server have no effect on subsequent messages which you might
send.
Both line count and byte size limits can be simultaneously
imposed. For instance, the two commands:
MAXIMUM BYTES 10000
MAXIMUM LINES 1000
Will result in messages larger than either 10,000 bytes or 1,000
lines being automatically fragmented into smaller messages, each
containing fewer than 10,000 bytes and 1,000 lines.
See the SEND command description for further information on the
usage of this command.
2.8.3 – Error messages
%MAILSERV-W-IVKEYW, unrecognized keyword -
check validity and spelling
You specified an unknown unit specification. Resend the command
specifying a legal value for the size-units parameter.
%MAILSERV-W-NUMBER, invalid numeric value - supply an integer
An invalid numeric value was supplied for the size-value
parameter. Resend the command specifying a positive integer
value.
%MAILSERV-W-POSITIVE, invalid numeric value - supply a positive integer
An invalid numeric value was supplied for the size-value
parameter. Resend the command specifying a positive integer
value.
%MAILSERV-W-INSFPRM, missing command parameters
You failed to specify one or both of the required parameters.
Resend the command specifying both the size-units and size-
value parameters.
2.9 – MODE
Set the file reading mode.
Syntax
MODE mode
2.9.1 – Parameters
mode
Required parameter specifying the file reading mode in which
files are to be accessed. There are four supported modes: TEXT,
BLOCK, RECORD, and RECORD-ATTRIBUTE.
2.9.2 – Description
Under OpenVMS, files can be read (accessed) in a variety of
ways. The MODE command controls the method used to read the
files the mail server returns. Note that default modes apply
automatically to various sorts of files; this command provides a
way to override these defaults.
The possible values for mode are:
TEXT Read files as ordinary text files. In TEXT mode,
files are read as a sequence of records and sent
as ordinary text. TEXT mode is the default for
files when no other mode has been set.
BLOCK Read files as raw binary data. Any record
boundary information, including carriage returns,
line feeds, line length counts, and indexing
information for indexed files simply becomes
part of the data. The resulting data typically
can only be used on the computer system it is
intended for. (Note that this not necessarily
restricted to OpenVMS; it is possible to store
files intended for other systems as VMS files.)
This is the recommend mode to use for binary
files.
RECORD Read files as a series of records. No record
boundaries of any kind appear in the output data.
This mode is appropriate for fixed length records
or records that are internally self-delimiting.
RECORD- Read files as a series of records. If the record
ATTRIBUTE attributes of the file indicate that boundaries
should be placed between the records (i.e.,
some form of carriage control is requested), a
boundary delimiter will be placed between each
record. This character is normally a line feed.
The reading mode specified with the MODE command applies to
all subsequent SEND commands in the same message. It can be
overridden with a subsequent MODE command or, on a per command,
basis with the SEND command's /MODE qualifier. And, of course,
reading modes established in previous messages sent to the server
have no effect on subsequent messages which you might send.
See the SEND command description for further information on the
usage of this command.
2.9.3 – Examples
The commands,
MODE BLOCK
ENCODING BASE64
SEND [.GIF]BOATS*.GIF
SEND/MODE=TEXT [GIF]INDEX.TXT
set the default reading mode to BLOCK and the default file
encoding to BASE64. Any files matching the specification
[GIF]BOATS*.GIF will be sent using these defaults. However,
the file [GIF]INDEX.TXT will be sent as an ordinary text file
owing to the use of the /MODE=TEXT qualifier.
2.9.4 – Error messages
%MAILSERV-W-IVKEYW, unrecognized keyword -
check validity and spelling
You specified an unknown mode. Resend the command specifying a
legal value for the mode parameter.
%MAILSERV-W-INSFPRM, missing command parameters
You failed to specify the mode parameter. Resend the command
specifying a legal value for the mode parameter.
2.10 – PURGE
2.10.1 /LIST
Remove comment lines from a mailing list file.
Syntax
PURGE/LIST list-name
2.10.1.1 – Parameters
list-name
Required parameter specifying the name of the list from which
comment lines are to be removed. Wildcards are not allowed.
2.10.1.2 – Description
Mailing list files can contain comment lines. In particular,
unsubscribed addresses are normally indicated via comment lines
in the file. The PURGE/LIST command causes such comment lines
to be removed, which can be useful to "clean up" the mailing
list file for a list which has undergone a great many changes in
membership.
2.10.1.3 – Examples
The commands,
PURGE/LIST fads-list
SEND/LIST fads-list
causes the fads-list mailing list membership file to have
comment lines removed from the file, and then a copy of the
file is requested.
2.10.1.4 – Error messages
%MAILSERV-W-CANTDELETE, cannot delete old mailing list file
An error occurred while trying to delete the old mailing list
file. Try again later; the postmaster in charge of the mail
server has been notified.
%MAILSERV-W-CANTUPDATE, cannot update mailing list file
An error occurred while trying to update the mailing list file.
Try again later; the postmaster in charge of the mail server
has been notified.
%MAILSERV-W-FLK, file currently locked by another user
The specified mailing list file is not currently accessible.
Try again later.
%MAILSERV-W-INSFPRM, missing command parameters
You failed to specify the list-name parameter. Resend the
command specifying a legal value for the list-name parameter.
%MAILSERV-W-LNF, mailing list not found
The mailing list you specified does not exist. Resend the
command specifying the name of a valid mailing list. You can
use the DIRECTORY/LIST command to obtain a listing of the valid
mailing list names.
%MAILSERV-W-LSTCREERR, unable to create new mailing list
The mailing list specified by the list-name parameter does not
exist and could not be created. Check to make sure that you
specified the correct list name.
%MAILSERV-F-NOMAILLIST, Mailing lists are not enabled
The mail server is not configured to operate as a list server.
%MAILSERV-W-PRV, insufficient privilege or file protection violation
You are not allowed to purge this mailing list. The MAILSERV_
ACCESS mapping can be used to change the default behavior of
the MAILSERV PURGE/LIST command. Please refer to the Mail and
list server section of the PMDF System Manager's Guide.
2.11 – SEND
Retrieve one or more files from the server.
Syntax
SEND file-spec extension
Qualifiers Defaults
/ENCODING=encoding None
/MODE=mode /MODE=TEXT
2.11.1 – Parameters
name
Required parameter specifying the file or files to send. This
parameter can include a directory specification, but must include
a file name. OpenVMS wild cards are allowed in both the directory
and file specification.
extension
Optional parameter which can be used to specify the extension of
the file to be sent.
2.11.2 – Description
The SEND command sends the requested files back to you via
electronic mail. Wild cards can be used in the file-spec
parameter to specify multiple files. Each file is sent as a
separate message.
The optional extension parameter is supplied for compatibility
with BITNET's LISTSERV file servers. When supplied, a period
followed by the value of this parameter will be appended to the
value of the file-spec parameter to form the actual file name to
use. For instance, the command
SEND NEWTAGS DESCRIPT
is interpreted as a request for the file NEWTAGS.DESCRIPT and is
equivalent to the command
SEND NEWTAGS.DESCRIPT
Large files can automatically be split into multiple smaller
files prior to transmission; see the description of the MAXIMUM
command for specific details. When the MAXIMUM command is used,
it must be specified prior to the SEND command; e.g.,
MAXIMUM BYTES 10000
MAXIMUM LINES 1000
SEND [BOOK]CHAPTER*.TXT
Files can be read in a variety of ways; this can be controlled
with the MODE command or the /MODE qualifier. Files containing
non-text information must be encoded in some way; the ENCODING
command or the /ENCODING qualifier control the encoding used.
When using the MODE and ENCODING commands, be sure to specify
them before the SEND command requiring their use.
Use the DIRECTORY and INDEX commands to obtain information on
available files which can be obtained with the SEND command.
2.11.3 – Qualifiers
2.11.3.1 /ENCODING
/ENCODING=encoding
The /ENCODING qualifier specifies the encoding to use for this
particular file. It does not establish any default for future
SEND commands, but it overrides any default set with the ENCODING
command for this particular SEND command. The value is required
and must be one of the values the ENCODING command accepts.
2.11.3.2 /MODE
/MODE=mode
The /MODE qualifier specifies the mode to use for this particular
file. It does not establish any sort of default for future SEND
commands, but it overrides any default set with the MODE command
for this particular SEND command. The value is required and must
be one of the values the MODE command accepts.
2.11.4 – Examples
1.$ MAIL
MAIL> SEND
To: in%"mailserv@example.com"
Subj:
Enter your message below. Press CTRL/Z when complete, or CTRL/C to quit:
SEND [FONTS]README.TXT
<CTRL/Z>
MAIL> EXIT
$
In this example, a simple request with a single command is sent
to the mail server mailserv@example.com. This single command
requests that the file [FONTS]README.TXT be sent.
2.$ MAIL
MAIL> SEND
To: in%"mailserv@example.com"
Subj:
Enter your message below. Press CTRL/Z when complete, or CTRL/C to quit:
MAXIMUM BYTES 10240
SEND/MODE=BLOCK/ENCODING=BASE64 [FONTS]ADOBE35.PFB-Z
<CTRL/Z>
MAIL> EXIT
$
In this example, a large binary file is being requested. The
/MODE and /ENCODING qualifiers are used to request that the
file be interpreted as raw binary data and sent in an encoded
format. The MAXIMUM command is used to fragment the encoded
file into several small messages, each no larger than 10K
(10,240 bytes).
2.11.5 – Error messages
%MAILSERV-W-FLK, file currently locked by another user
One or more of the requested files is not currently accessible.
Try again later.
%MAILSERV-W-INSFPRM, missing command parameters
You failed to supply the name of the files to send. You must
supply a file specification. Resend the command with a file
specification.
%MAILSERV-W-IVKEYW, unrecognized keyword - check validity and spelling
You specified an unknown encoding or reading mode. Resend
the command using a legal encoding or reading mode with the
/ENCODING or /MODE qualifier.
%MAILSERV-W-NOFILES, no files found
Supplied file specification does not match any available files.
Use the DIRECTORY command to obtain a listing of the available
files.
%MAILSERV-F-NOFILESERV, file service is not enabled
The mail server is not configured to operate as a file server.
%MAILSERV-W-PRV, insufficient privilege or file protection violation
You are not allowed access to one or more of the requested
files.
%MAILSERV-W-VALREQ, missing qualifier or keyword value
You failed to supply a value with the /ENCODING or /MODE
qualifier. Resend the command with a value specification.
Return a list of the current subscribers to a particular mailing
list.
Syntax
SEND/LIST list-name
Qualifiers Defaults
/COMMENTS See text
2.11.5.1 – Parameters
list-name
Required parameter specifying the name of the list whose
subscribers are to be returned. Wild cards are not allowed.
2.11.5.2 – Description
The SEND/LIST command responds with a message containing a list
of the current subscribers to a given mailing list.
2.11.5.3 – Qualifiers
2.11.5.3.1 /COMMENTS
/COMMENTS
/NOCOMMENTS
When /COMMENTS is specified, comment fields associated with each
subscribed address will also be returned. Specify /NOCOMMENTS
to have these fields stripped from the listing sent to you.
The default behavior can vary from list to list. Generally the
default behavior is to include the comments.
Note that in RFC 822 addresses, comments are completely
superfluous and it should be possible to strip any or all
comments from an address without breaking the address. However,
there are known to be mailers which stupidly put critical
information into comment fields with the expectation that the
comments will not be stripped or altered. Addresses for such
mailers can be rendered unreplyable by removing the comment
fields from them.
2.11.5.4 – Error messages
%MAILSERV-W-INSFPRM, missing command parameters
You failed to specify the mailing list name. Resend the command
specifying the name of the mailing list whose membership list
you want to obtain.
%MAILSERV-W-LNF, list not found
The mailing list you specified does not exist. Resend the
command specifying the name of a valid mailing list. You can
use the DIRECTORY/LIST command to obtain a listing of the valid
mailing list names.
%MAILSERV-F-NOMAILLIST, mailing lists are not enabled
The mail server is not configured to operate as a list server.
%MAILSERV-W-PRV, insufficient privilege or file protection violation
You are not allowed to retrieve the list of subscribers to this
mailing list. The MAILSERV_ACCESS mapping can be used to change
the default behavior of the MAILSERV SEND/LIST command. Please
refer to the Mail and list server section in the PMDF System
Manager's manual.
%MAILSERV-W-WRITEERR, file writing error
An error occurred while the mail server was writing the message
to you. Try resending this command at a later time.
2.12 – SUBSCRIBE
Subscribe to a mailing list.
Syntax
SUBSCRIBE list-name [[personal-name] address]
2.12.1 – Parameters
list-name
Required parameter specifying the name of the mailing list to
subscribe to. Wild cards are not allowed.
personal-name
Optional parameter specifying the personal name for the address
to subscribe to the mailing list. If this parameter is omitted,
no personal name information will be included in the subscribed
address.
address
Optional parameter specifying the fully-qualified address to
subscribe to the mailing list. If no address is specified, the
From: address from the requesting message will be used.
2.12.2 – Description
The SUBSCRIBE command adds either your address or a specified
address to the specified mailing list. A response message
reporting the success or failure of the subscription request will
be returned. If the file PMDF_MAILSERV_MAIL_DIR:list-name.TXT
exists, it will be sent to you.
Use the UNSUBSCRIBE command to subsequently unsubscribe from a
mailing list; use the DIRECTORY/LIST or LISTS command to obtain
information on available mailing lists.
Note that some mail servers can impose restrictions as to who may
or may not subscribe to a given list.
2.12.3 – Examples
1.SUBSCRIBE LOCAL-NEWS
This example shows the command to SUBSCRIBE oneself to the list
LOCAL-NEWS.
2.SUBSCRIBE LOCAL-NEWS "John Doe" <jdoe+local-news@example.com>
This example shows the user jdoe@example.com subscribing the
address "John Doe" <jdoe+local-news@example.com> to the list
LOCAL-NEWS. That is, this example shows a subscription request
using a more formal address format, one that includes an RFC
822 personal name as well as the actual address, and where
the address includes a subaddress; see for more details about
subaddresses.
2.12.4 – Error messages
%MAILSERV-W-
ALREADYSUB, address is already subscribed to the mailing list
You are already subscribed to the mailing list. If you used
the optional address parameter, then the specified address is
already subscribed. Check to make sure that you specified the
correct mailing list name or address or both.
%MAILSERV-W-CANTDELETE, cannot delete old mailing list file
An error occurred while trying to delete the old mailing list
file. Try again later; the postmaster in charge of the mail
server has been notified.
%MAILSERV-W-CANTUPDATE, cannot update mailing list file
An error occurred while trying to update the mailing list. Try
again later; the postmaster in charge of the mail server has
been notified.
%MAILSERV-W-ILLADDRESS, illegal address
You specified an illegal or invalid address for the optional
address parameter. Resend the command either omitting the
address entirely or specifying a valid address.
%MAILSERV-W-INSFPRM, missing command parameters
You failed to supply the name of the mailing list to subscribe
to. Resend the command with a list name specification.
%MAILSERV-W-LNF, list not found
The mailing list you specified does not exist. Resend the
command specifying the name of a valid mailing list. You can
use the DIRECTORY/LIST command to obtain a listing of the valid
mailing list names.
%MAILSERV-W-LSTCREERR, unable to create new mailing list
The mailing list specified by the list-name parameter does not
exist and could not be created. Check to make sure that you
specified the correct list name.
%MAILSERV-W-LSTLOCKED, mailing list currently locked by another user
The mailing list is currently locked; you cannot subscribe to
it at this time. Try resending the command again later.
%MAILSERV-F-NOMAILLIST, mailing lists are not enabled
The mail server is not configured to operate as a list server.
%MAILSERV-W-PRV, insufficient privilege or file protection violation
You are not allowed to subscribe to this mailing list.
2.13 – UNSUBSCRIBE
Unsubscribe from a mailing list.
Syntax
UNSUBSCRIBE list-name [address]
2.13.1 – Parameters
list-name
Required parameter specifying the name of the mailing list to
unsubscribe from Wild cards are not allowed.
address
Optional parameter specifying the address to remove from the
mailing list. If no address is specified, the From: address from
the requesting message will be used.
2.13.2 – Description
The UNSUBSCRIBE command removes either your address or the
address you specify from the specified mailing list. A response
message reporting the success or failure of the unsubscribe
request will be returned.
Typically, the use of the optional address parameter is
restricted.
2.13.3 – Error messages
%MAILSERV-W-CANTDELETE, cannot delete old mailing list file
An error occurred while trying to delete the old mailing list
file. Try again later; the postmaster in charge of the mail
server has been notified.
%MAILSERV-W-CANTUPDATE, cannot update mailing list file
An error occurred while trying to update the mailing list. Try
again later; the postmaster in charge of the mail server has
been notified.
%MAILSERV-W-ILLADDRESS, illegal address
You specified an illegal or invalid address for the optional
address parameter. Resend the command either omitting the
address entirely or specifying a valid address.
%MAILSERV-W-INSFPRM, missing command parameters
You failed to supply the name of the mailing list to
unsubscribe from. Resend the command with a list name
specification.
MAILSERV-W-LNF, mailing list not found
The mailing list you specified does not exist. Resend the
command specifying the name of a valid mailing list. You can
use the DIRECTORY/LIST command to obtain a listing of the valid
mailing list names.
%MAILSERV-W-LSTCREERR, unable to create new mailing list
The mailing list specified by the list-name parameter does not
exist and could not be created. Check to make sure that you
specified the correct list name.
%MAILSERV-W-LSTLOCKED, mailing list currently locked by another user
The mailing list is currently locked; you cannot unsubscribe
from it at this time. Try again later.
%MAILSERV-F-NOMAILLIST, mailing lists are not enabled
The mail server is not configured to operate as a list server.
%MAILSERV-W-NOSUCHADR, no such address subscribed to the mailing list
You are not subscribed to the specified mailing list. If you
used the optional address parameter, then the specified address
is not subscribed. Check to make sure that you specified the
correct mailing list name or address or both.
%MAILSERV-W-PRV, insufficient privilege or file protection violation
You are not allowed to unsubscribe from this mailing list or
unsubscribe addresses other than your own from the list.