Import ezmlm-idx 0.40
[ezmlm] / ezmlm-gate.1
CommitLineData
f8beb284
MW
1.TH ezmlm-gate 1
2.SH NAME
3ezmlm-gate \- Gate posts depending on message SENDER
4.SH SYNOPSIS
5.B ezmlm-gate [-cCmMpPrRsSvV] [-q file]
6.I dir [moddir1] [moddir2 ...]
7.SH DESCRIPTION
8.B ezmlm-gate
9checks if SENDER is in it least one of the subscriber lists
10with base directory
11.IR moddir1 ,
12.IR moddir2 ,
13etc.
14If it is, the message is posted via
15.B ezmlm-send
16to the list in
17.IR dir .
18If not, the message is sent for moderation via
19.BR ezmlm-store .
20
21The default is to send the message for moderation.
22.SH OPTIONS
23.TP
24.B \-cCmMpPrRsS
25Passed on to ezmlm-store(1) and ezmlm-send(1).
26.TP
27.B \-cCrR
28Passed on to ezmlm-send(1).
29.TP
30.B \-q\fI file
31Execute arbitration programs in
32.IR file .
33Lines in
34.I file
35are executed just like in regular
36.IR .qmail
37files with the difference that all lines are assumed to be program
38names. See
39.BR dot-qmail(5) .
40Programs are executed by /bin/sh and the message is on stdin of the
41executed program.
42The leading ``|'' is optional. Comments and blank lines are allowed. If a
43program exits 111, delivery is deferred. If it exits 99, the message is
44sent to the list. If it exits 0, the next line is executed. If it exits
45with any other exit code, the message is sent for moderation. Subscriber
46status per
47.IR moddir1 ,
48.IR moddir2 ,
49etc, is tested only if all the programs have been executed and the final
50exit code is 0. Thus, programs can cause moderation (100), posting (99), or
51defer the decision to the next program and ultimately to subscriber status.
52.TP
53.B \-v
54Display version information.
55.TP
56.B \-V
57Display version information.
58
59.SH USAGE
60.B ezmlm-gate
61is best used if you want to restrict posts to a set of addresses using
62SENDER checks. Obviously, this is not secure, but it
63can help quite a bit to keep
64garbage off the list. For more secure setups, see
65.BR ezmlm-store(1) .
66For other arbitration such as SPAM protection, use the
67.B \-q
68option. For instance, invoking
69.B ezmlm-reject(1)
70here would cause failing messages to be sent for moderation rather that being
71rejected.
72
73Set up the list with a
74.B ezmlm-gate
75line in
76.I dir\fB/editor
77and touch
78.IR dir\fB/modpost .
79Add the moderator(s) (usually the list owner):
80
81.EX
82.B ezmlm-sub
83.I dir\fB/mod
84moderator@host
85.EE
86
87This will via
88.B ezmlm-send
89directly distribute
90all posts from subscriber addresses and send out the rest for moderation
91to the moderator(s) via
92.BR ezmlm-store .
93To test several subscriber databases, e.g. the list and the list-digest
94subscribers, add the corresponding list directories to the
95.B ezmlm-gate
96command line.
97
98This can be expanded to include users that post from addresses other than
99the one they are subscribed as: just create another directory 'addl', and
100a 'subscribers' subdirectory of it, and add 'addl' to the
101.B ezmlm-gate
102command line. Now just add all problem addresses to the 'addl' address
103database using
104.BR ezmlm-sub .
105The entire point is that post from subscribers of any union
106of list go through, posts from identified 'aliases' go through and all
107others go for approval to the list owner. Thus, legitimate users are never
108rejected and 'aliases' rapidly identified by the owner/moderator and
109their handling automated one by one, by simply adding them to 'addl'.
110.SH "SEE ALSO"
111dot-qmail(5),
112ezmlm(5),
113ezmlm-issubn(1),
114ezmlm-reject(1),
115ezmlm-send(1),
116ezmlm-store(1)