Section: User Commands (1)
Return to Main Contents
ezmlm-request - Process subject line and body ezmlm commands
processes ezmlm commands in the subject line or message body.
enables these uses to send the message to
with the complete command address line in the subject field,
or with commands and arguments separated by white
uses the text to construct a ezmlm command message to the list.
If the subject does not start with a letter,
instead uses the first body line that starts with a letter. Processing
terminates if a line with a hyphen in the first position is encountered.
All commands are expected to be in ezmlm command address format or formatted
command [list@listhost [user@userhost]]
when invoked with the
switch and a configuration file (see below), ignores the subject and processes
the first body line (per rules above) in conjunction with the configuration
file. It also services the
commands. This can be used
to construct a global list interface, similar to that used by some other
mailing list managers.
Messages at the
are restricted to the local list. When
is invoked with the
switch, command messages are limited to lists in
or at the local host.
Invalid requests for an existing ezmlm list will
lead to a ``help'' message from
to determine how many lines of the original message to copy into the
outgoing message. If this file is empty or not present, a value of
is presumed, meaning that only the header is copied.
- -f config
Function as a global interface to ezmlm lists in accordance with
This file consists of lines starting in the first position
with ``list@host:listdir:description''. Lines that are blank or start
with ``#'' are ignored. ``listdir''
and ``description'' are optional. If only ``list@host'' is given, the list
is used to restrict commands (see below), but not listed. To allow the list
to be shown by a ``list'' command, use ``list@host:''. To specify only
the list name and description, use ``list@host::description''.
If ``listdir'' is
command attempts to determine if the user is a subscriber of the list.
this will work only if the user running
has read access to the lists subscriber database.
If ``listhost'' is not specified,
will use the ``listhost'' from the first
entry matching ``listlocal''. If ``listhost'' is specified, but not found
it is set to the contents of
Place an invocation of
anywhere before the
Alternatively, set up
with an invocation of
Make a link from
to this file.
For the global interface, place
/path/ezmlm-request -f config dir
into a file.
to this file. The latter allows
to handle its own bounces as well as to reply to messages to e.g.
with headers to keep or
with headers to be stripped (copy from a list),
with the appropriate texts.
with the appropriate contents.
Mail to ``user-ezmlm@listhost'' will now be answered by
Any command not recognized by
is assumed to be valid, as long as it consists of only letters, numbers,
hyphen, underscore, period, and ``+''. This allows
to correctly handle commands added by the list owner.
A number of commands are recognized by
but not processed. Instead they are mapped to
without arguments. These
also handles a number of aliases for ezmlm commands. Since
only passes on requests to the list, local restrictions apply.
For commands that have aliases, accepted aliases are listed:
unsub, signoff, remove.
recipients, showdist, review, rev, who.
Some commands are handled differently when used without arguments:
Treated like ``which''.
Treated like ``lists''.
places stricter requirements on addresses than rfc822. Thus, some addresses
that are rfc822-compliant cannot be used as
command arguments. If you fix this,
please send a patch to firstname.lastname@example.org. I think qmail has the same
uses NUL as a line terminator internally. Thus, if will fail if NUL is found
within the line it tries to interpret as a command. It is harmless, other than
that the remainder of the line will be ignored.
command does not differentiate between a list for which the command is not
available, a list for which the subscriber db is not accessible, and a list
for which the address is not a subscriber. This should be considered a feature.
when used as a global interface and receiving multipart messages assumes that
the first line of the fist part is the command. Further, it assumes that the
first line starting``--'' is the first MIME boundary. This is virtually
always true, but it is easy to construct legal messages that do not fit these
in the global interface role
will fail if this first part or the entire message is base64 encoded.
- RECOGNIZED COMMANDS
- SEE ALSO
This document was created by
using the manual pages.
Time: 18:00:51 GMT, June 16, 2008