The default is to send the message for moderation.

-cCmMpPrRsS

Passed on to ezmlm-store(1) and ezmlm-send(1).

-cCrR

Passed on to ezmlm-send(1).

-q file

Execute arbitration programs in file. Lines in file are executed just like in regular .qmail files with the difference that all lines are assumed to be program names. See . Programs are executed by /bin/sh and the message is on stdin of the executed program. The leading ``|'' is optional. Comments and blank lines are allowed. If a program exits 111, delivery is deferred. If it exits 99, the message is sent to the list. If it exits 0, the next line is executed. If it exits with any other exit code, the message is sent for moderation. Subscriber status per moddir1, moddir2, etc, is tested only if all the programs have been executed and the final exit code is 0. Thus, programs can cause moderation (100), posting (99), or defer the decision to the next program and ultimately to subscriber status.

-v

Display version information.

-V

Display version information.

Set up the list with a ezmlm-gate line in dir/editor and touch dir/modpost. Add the moderator(s) (usually the list owner):

ezmlm-sub dir/mod moderator@host

This will via ezmlm-send directly distribute all posts from subscriber addresses and send out the rest for moderation to the moderator(s) via ezmlm-store. To test several subscriber databases, e.g. the list and the list-digest subscribers, add the corresponding list directories to the ezmlm-gate command line.

This can be expanded to include users that post from addresses other than the one they are subscribed as: just create another directory 'addl', and a 'subscribers' subdirectory of it, and add 'addl' to the ezmlm-gate command line. Now just add all problem addresses to the 'addl' address database using ezmlm-sub. The entire point is that post from subscribers of any union of list go through, posts from identified 'aliases' go through and all others go for approval to the list owner. Thus, legitimate users are never rejected and 'aliases' rapidly identified by the owner/moderator and their handling automated one by one, by simply adding them to 'addl'.