ezmlm-gate(1) ezmlm-gate(1) NNAAMMEE ezmlm-gate - Gate posts depending on message SENDER SSYYNNOOPPSSIISS eezzmmllmm--ggaattee [[--ccCCmmMMppPPrrRRssSSvvVV]] [[--qq ffiillee]] _d_i_r _[_m_o_d_d_i_r_1_] _[_m_o_d_d_i_r_2 _._._._] DDEESSCCRRIIPPTTIIOONN eezzmmllmm--ggaattee checks if SENDER is in it least one of the subscriber 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 eezzmmllmm--sseenndd to the list in _d_i_r. If not, the message is sent for moderation via eezzmmllmm--ssttoorree. The default is to send the message for moderation. OOPPTTIIOONNSS --ccCCmmMMppPPrrRRssSS Passed on to ezmlm-store(1) and ezmlm-send(1). --ccCCrrRR Passed on to ezmlm-send(1). --qq _f_i_l_e Execute arbitration programs in _f_i_l_e. Lines in _f_i_l_e are exe- cuted just like in regular _._q_m_a_i_l files with the difference that all lines are assumed to be program names. See ddoott--qqmmaaiill((55)). 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 _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. --vv Display version information. --VV Display version information. UUSSAAGGEE eezzmmllmm--ggaattee 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 eezzmmllmm--ssttoorree((11)). For other arbitration such as SPAM protec- tion, use the --qq option. For instance, invoking eezzmmllmm--rreejjeecctt((11)) here would cause failing messages to be sent for moderation rather that being rejected. Set up the list with a eezzmmllmm--ggaattee line in _d_i_r//eeddiittoorr and touch _d_i_r//mmoodd-- ppoosstt. Add the moderator(s) (usually the list owner): eezzmmllmm--ssuubb _d_i_r//mmoodd moderator@host This will via eezzmmllmm--sseenndd directly distribute all posts from subscriber addresses and send out the rest for moderation to the moderator(s) via eezzmmllmm--ssttoorree. To test several subscriber databases, e.g. the list and the list-digest subscribers, add the corresponding list directories to the eezzmmllmm--ggaattee 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 eezzmmllmm--ggaattee command line. Now just add all problem addresses to the ’addl’ address database using eezzmmllmm--ssuubb. 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 identi- fied by the owner/moderator and their handling automated one by one, by simply adding them to ’addl’. SSEEEE AALLSSOO dot-qmail(5), ezmlm(5), ezmlm-issubn(1), ezmlm-reject(1), ezmlm- send(1), ezmlm-store(1) ezmlm-gate(1)