3 ezmlm-send \- distribute a message to a mailing list
14 reads a mail message and
15 sends it to the mailing list stored in
21 records a copy of the message in the
29 adds the subject, author and time stamp of the message to the index, kept with
30 the message in a subdirectory of
32 The subject is processed to make reply-subject entries identical to
34 message subject entries.
35 The subject index is used for the archive retrieval functions of
39 to create a subject index from a preexisting archive.
41 Subject and author lines are decoded if they are encoded per rfc2047. When
42 split lines are unfolded, the number of escape sequences for
43 iso-2022-* character sets is minimized. For instance, two
44 consequtive toascii sequences are reduced.
45 This processing is done for the character set specified in
47 The result of this process is the same for a given subject, irrespective
50 At the beginning of the message,
54 field with the contents of
55 .IR dir\fB/mailinglist .
56 It rejects the message if there is already a
64 will assume that the format is correct and
65 create a ``List-ID:'' header by placing the contents after the
70 prints all the new fields listed in
71 .IR dir\fB/headeradd .
72 Any tags, ``<#h#>'', ``<#l#>'', or ``<#n#>'' found in these headers
73 are replaced by the list host name, list local name, and message number,
77 then prints an appropriate
82 deletes any incoming fields with names listed in
83 .IR dir\fB/headerremove .
86 removes MIME parts specified in
88 before archiving and distribution of the message.
91 .I dir\fB/text/trailer
94 adds the trailer to simple text/plain messages in the same encoding as used for
95 the the message. However, if the encoding is ``base64'' it is not safe
96 to do this and the header is suppressed.
97 For composite MIME messages, the trailer is added as a separate
98 part, with the character set and encoding specified in
100 The trailer is not added to multipart/alternative messages.
101 Any tags, ``<#h#>'', ``<#l#>'', or ``<#n#>'' found in
102 .I dir\fB/text/trailer
103 are replaced by the list host name, list local name, and message number,
110 will prefix the subject line with the first line of this
111 file. A space will be added to separate
113 from the subject text.
115 is ignored for sublists. If
117 contains a ``#'', the last ``#'' will be replaced by the message number.
118 Any prefix starting with text of a
119 reply indicator (``Re:'', ``Re[n]:'', etc) will cause problems.
121 rfc2047 encoded. Rfc2047 Iso-2022-* encoded prefixes
125 The prefix feature and especially the message number feature
126 modify the message in violation
127 with Internet mail standards. The features have been implemented by popular
128 demand. Use at your own peril.
131 is ignored as of ezmlm-idx-0.32. Use
133 with substitution to achieve the same goal.
136 .I dir\fB/qmqpservers
138 .B ezmlm-send will use
143 does not distribute bounce messages:
144 if the environment variable
146 is set, and is either empty or
153 No longer supported. Ignored for backwards compatibility.
156 No longer supported. Ignored for backwards compatibility.
158 has to parse the subscriber database.
161 If the list is a sublist, i.e.
165 is required in all messages to the list. This option is used
166 when ezmlm is used to run a sublist of a lists run by a different
170 rather than ``Mailing-List'' to identify messages from the list.
171 Anything after the first colon (if present) in
176 Copy incoming ``Received:'' headers to the outgoing message.
180 Do not copy incoming ``Received:'' headers, except the one added by
181 the (last) listhost, to the outgoing message.
183 cases, especially for sublists,
184 the messages can have a large number of ``Received:''
185 headers. This may lead to bounces for some users due to
186 sendmail ``hopcounts'' set too low somewhere in the mail path. These users can
187 subscribe and receive warning and probe messages, but no list messages, unless
188 the number of ``Received:'' headers is reduced.
190 Pre-list ``Received:'' headers are of little interest to normal list
191 subscribers. ``Received:'' headers are
192 still copied to the archive and available
193 to anyone from there for message tracking purposes.
209 changes its behavior in several ways.
214 and the first line of
217 .IR parent\fB@\fIparenthost ,
222 .IR parent\fB...@\fIparenthost .
226 demands that the message already have a
238 uses the incoming message number for the outgoing message, if the list
239 is not archived and the incoming SENDER has the correct format.
240 This allows you to refer bounce warning recipients to the main list for
241 archive retrieval of the missed messages. If the sublist archives
242 message, it is assumed that missed messages will be retrieved from the sublist
248 for each message. If the sublist is archived, use of incoming message number
249 for archive storage would be a security risk. In this case, the local sublist
250 message number is used.
252 In general, the use of a prefix is discouraged. It wastes subject line space,
253 creates trouble when MUAs add non-standard reply indicators. However, many
254 users expect it not because it is useful, but because they are used to it.
258 switch prevents posts from being set to SENDER. Rather than just copying
259 out subscriber address files,
261 has to parse them to look for SENDER. This makes it less efficient. Also,
262 it is useful for the SENDER to see the post to know that it has made it
263 to the list, and it's context to other subscribers, i.e. where it came
264 within the traffic of messages on the list.
266 Avoiding SENDER as a recipient is useful in small lists, such as small
267 teams with varying members, where ezmlm serves mainly as an efficient tool
268 to keep the team connected without administrator intervention. Here the
269 overhead of subscriber list parsing is negligible.
271 If the list is indexed,
273 will keep a message index. rfc2047-encoded subject and from lines will be
279 will eliminate redundant escape sequences from the headers according to
280 the character set specified in this file.
281 Only character sets using escape sequences need this support. Currently,
282 supported are iso-2022-jp*, iso-2022-kr, and iso-2022-cn*. Only iso-2022-jp
283 has been tested extensively.
285 The character set can be suffixed
286 by ``:'' followed by a code. Recognized codes are ``Q''
287 for ``Quoted-Printable'', and ``B'' for ``base64''.
291 this affects the format of the trailer, if a trailer is specified and if the
292 message is a multipart mime message