User Commands ezmlm-gate(1) NNNNAAAAMMMMEEEE ezmlm-gate - Gate posts depending on message SENDER SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS eeeezzzzmmmmllllmmmm----ggggaaaatttteeee [[[[----ccccCCCCmmmmMMMMppppPPPPrrrrRRRRssssSSSSvvvvVVVV]]]] [[[[----qqqq ffffiiiilllleeee]]]] _d_i_r [_m_o_d_d_i_r_1] [_m_o_d_d_i_r_2 ...] DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN eeeezzzzmmmmllllmmmm----ggggaaaatttteeee checks if SENDER is in it least one of the sub- scriber lists with base directory _m_o_d_d_i_r_1, _m_o_d_d_i_r_2, etc. If it is, the message is posted via eeeezzzzmmmmllllmmmm----sssseeeennnndddd to the list in _d_i_r. If not, the message is sent for moderation via eeeezzzzmmmmllllmmmm---- ssssttttoooorrrreeee. The default is to send the message for moderation. OOOOPPPPTTTTIIIIOOOONNNNSSSS -ccccCCCCmmmmMMMMppppPPPPrrrrRRRRssssSSSS Passed on to ezmlm-store(1) and ezmlm-send(1). -ccccCCCCrrrrRRRR Passed on to ezmlm-send(1). -qqqq _f_i_l_e Execute arbitration programs in _f_i_l_e. Lines in _f_i_l_e are executed just like in regular ._q_m_a_i_l files with the difference that all lines are assumed to be program names. See ddddooootttt----qqqqmmmmaaaaiiiillll((((5555)))). 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 exe- cuted. If it exits with any other exit code, the mes- sage is sent for moderation. Subscriber status per _m_o_d_- _d_i_r_1, _m_o_d_d_i_r_2, 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. -vvvv Display version information. -VVVV Display version information. UUUUSSSSAAAAGGGGEEEE eeeezzzzmmmmllllmmmm----ggggaaaatttteeee is best used if you want to restrict posts to a set of addresses using SENDER checks. Obviously, this is not secure, but it can help quite a bit to keep garbage off the list. For more secure setups, see eeeezzzzmmmmllllmmmm----ssssttttoooorrrreeee((((1111)))). For other arbitration such as SPAM protection, use the -qqqq option. For SunOS 5.11 Last change: 1 User Commands ezmlm-gate(1) instance, invoking eeeezzzzmmmmllllmmmm----rrrreeeejjjjeeeecccctttt((((1111)))) here would cause failing messages to be sent for moderation rather that being rejected. Set up the list with a eeeezzzzmmmmllllmmmm----ggggaaaatttteeee line in _d_i_r////eeeeddddiiiittttoooorrrr and touch _d_i_r////mmmmooooddddppppoooosssstttt. Add the moderator(s) (usually the list owner): eeeezzzzmmmmllllmmmm----ssssuuuubbbb _d_i_r////mmmmoooodddd moderator@host This will via eeeezzzzmmmmllllmmmm----sssseeeennnndddd directly distribute all posts from subscriber addresses and send out the rest for moderation to the moderator(s) via eeeezzzzmmmmllllmmmm----ssssttttoooorrrreeee. To test several sub- scriber databases, e.g. the list and the list-digest sub- scribers, add the corresponding list directories to the eeeezzzzmmmmllllmmmm----ggggaaaatttteeee 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' sub- directory of it, and add 'addl' to the eeeezzzzmmmmllllmmmm----ggggaaaatttteeee command line. Now just add all problem addresses to the 'addl' address database using eeeezzzzmmmmllllmmmm----ssssuuuubbbb. 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'. SSSSEEEEEEEE AAAALLLLSSSSOOOO dot-qmail(5), ezmlm(5), ezmlm-issubn(1), ezmlm-reject(1), ezmlm-send(1), ezmlm-store(1) SunOS 5.11 Last change: 2