Note: The contents of dir/modpost do not affect the location of the message moderation queue.

If SENDER is a moderator, the request is sent to that moderator only.

The moderation request includes cookies for message rejection and acceptance. The moderator can take either action by replying to the appropriate address. For moderator convenience, the accept address is given in the ``Reply-To:'' header, and the reject address in the ``From:'' header.

If the list is set up with remote administration and the sender is not a moderator, the ``Cc:'' header will contain a confirmation address to add the sender to the ``allow'' database. This allows the moderator to both approve the post and add the sender to the list of accepted posters by replying to ``all''.

The (default) subject of all message moderation requests is MODERATE for listname@host.

Once the request has been successfully sent to the moderators, ezmlm-store sets the owner-execute bit of the message in dir/mod/pending/. Messages without this bit set are the result of incomplete executions of ezmlm-store and are ignored.

At the beginning of the message, ezmlm-store prints a new Mailing-List field with the contents of dir/mailinglist. It rejects the message if there is already a Mailing-List field.

ezmlm-store does not distribute bounce messages: if the environment variable SENDER is set, and is either empty or #@[], ezmlm-store rejects the message.

-b

(Default.) With the moderation request, send both headers and body of the message to be moderated.

-B

With the moderation request, send header, but not body of the message to be moderated. This may be useful if moderation is used to allow one or a few poorly connected addresses to post, and posts are very large (e.g. when the list is used as a distribution channel of e.g. catalogs).

-cCrR

Passed on to ezmlm-send(1) in case this program is executed. This happens only if dir/modpost does not exist.

-m

(Default.) The post is sent as a MIME enclosure.

-M

The post is appended to the message.

-s

The contents of dir/modpost with the default dir/mod/ are used as the base directory for self-approving users, whereas dir/mod/ is used as the base directory for the moderators to whom approval requests for other posts are sent.

-S

(Default.) The contents of dir/modpost with the default dir/mod/ are used as the base directory for the moderators for all moderator functions.

-p

(Default.) Anyone can post. Posts that are not from a moderator are sent out to all moderators for approval. Posts that are from a moderator are sent only to that moderator.

-P

Only moderators can post. Those posts are sent to the posting moderator for approval. Posts from other addresses are bounced. This can be used to relatively securely restrict posts to messages originating from a given set of addresses.

-v

Display ezmlm-manage version information.

-V

Display ezmlm-manage version information.

Normally (no switches), posts from moderators are sent for approval only to the sending moderator, whereas posts from other addresses are sent to all moderators. Thus, you can set up an announcement list by adding all potential posters as moderators. However, you may also want to allow others to post, as long as the posts are approved. This would be default ezmlm-store function.

To make the set of ``approved posters'' who approve their own posts, different from the set of addresses that approve posts from other users, use the -s switch. Add a directory name to dir/modpost. This directory is the base directory of the ``approved posters'' database. Add the moderators for other posts to dir/mod/ using ezmlm-sub(1).