3 ezmlm \- format of ezmlm directory
9 stores information about an
18 manipulate the subscriber list stored under
21 handles administrative requests automatically;
23 sends a message to all subscribers listed in
27 is a directory containing the subscriber list.
29 allows automatic subscription if
33 The list is hashed into 53 files, named
38 A nonexistent file is treated as an empty file.
40 Each file contains a series of addresses.
41 An address can be any string of non-NUL characters up to 400 bytes long.
42 Each address is preceded by the letter T and followed by a NUL.
45 when an address is added to or removed from the mailing list,
46 the relevant file is recreated under a temporary name
49 and then moved into place.
56 to create confirmation numbers.
57 Anyone who can guess the contents of
59 can forge subscription requests.
61 does not put much effort into making
64 for better security, you should add some random garbage to
68 is a directory containing messages previously sent to subscribers.
70 archives all new messages if
74 Messages sent to the mailing list are numbered from 1 upwards,
75 whether or not they are archived.
77 is the number of messages sent so far.
81 each subdirectory storing up to 100 messages.
82 Message number 100m+n, with n between 0 and 99, is stored in
83 .IR dir\fB/archive/\fIm\fB/\fIn .
84 For example, message number 15307 is stored in
85 .IR dir\fB/archive/153/07 .
88 will ignore message files without the owner-execute bit set.
90 turns on the owner-execute bit after safely writing the message to disk.
93 is a directory containing bounce messages.
95 stores several types of files here.
96 .SH "DELIVERY INSTRUCTIONS"
98 sets up four files to control mailing list deliveries.
99 Each file is a series of delivery instructions in
104 handles incoming mailing list submissions.
110 to immediately forward each message to all subscribers
115 handles incoming messages for the mailing list's owner.
125 handles incoming bounce messages.
135 handles incoming administrative requests.
146 containing files sent out by
148 in response to administrative requests:
153 This is placed at the top of each response.
156 Explaining how to use
158 This is placed at the bottom of each response.
161 Explaining how to confirm a subscription request.
164 Acknowledging successful subscription.
167 Acknowledging a subscription request for an address already
171 Rejecting a bad subscription confirmation number.
174 Explaining how to confirm an unsubscription request,
175 and explaining how to figure out the subscription address.
178 Acknowledging successful unsubscription.
181 Acknowledging an unsubscription request for an address not
185 Rejecting a bad unsubscription confirmation number.
188 Rejecting a bad archive retrieval request.
191 Pointing out that messages have bounced.
194 Pointing out that a warning message has bounced.
199 has kept a list of bounced message numbers.
202 Separating the bounce message.
207 in any of these files
208 with the name of the subscription address.
215 with the address that the subscriber must reply to.
216 .SH "OUTGOING MESSAGE EDITING"
217 .I dir\fB/headerremove
218 is a list of bad header field names,
221 removes these header fields from all outgoing messages.
224 .I dir\fB/headerremove
227 .BR Return-Receipt-To ,
233 is a list of new header fields.
235 adds these fields to every outgoing message.
242 .I dir\fB/mailinglist
247 field, showing the contents of
248 .IR dir\fB/mailinglist ,
249 in every outgoing message.
255 give the outgoing name of the mailing list.
260 to construct sender addresses for outgoing messages.
266 give the incoming name of the mailing list.
269 to parse incoming envelopes.
278 but sometimes they are different,
280 .I outlocal\fB@\fIouthost
282 .IR inlocal\fB@\fIinhost .
287 this mailing list is a sublist,
288 redistributing messages from a parent mailing list.
291 is the name of the parent list.
292 This affects the behavior of
297 Any program that reads or writes the subscriber list,
298 or adds messages to the archive,
303 is an advisory log of subscription and unsubscription actions.
306 is not protected against system crashes.
307 Log entries may be missing or corrupted if the system goes down.