|-c||No longer supported. Ignored for backwards compatibility.|
|-C||No longer supported. Ignored for backwards compatibility. ezmlm-send has to parse the subscriber database.|
|If the list is a sublist, i.e. dir/sublist exists, header is required in all messages to the list. This option is used when ezmlm is used to run a sublist of a lists run by a different mailing list manager that uses header rather than Mailing-List to identify messages from the list. Anything after the first colon (if present) in header is ignored.|
|-r||Copy incoming Received: headers to the outgoing message.|
Do not copy incoming Received: headers, except the one added by
the (last) listhost, to the outgoing message.
cases, especially for sublists,
the messages can have a large number of Received:
headers. This may lead to bounces for some users due to
sendmail hopcounts set too low somewhere in the mail path. These users can
subscribe and receive warning and probe messages, but no list messages, unless
the number of Received: headers is reduced.
Pre-list Received: headers are of little interest to normal list subscribers. Received: headers are still copied to the archive and available to anyone from there for message tracking purposes.
|-v||Display ezmlm-send version information.|
|-V||Display ezmlm-send version information.|
If dir/sublist exists, ezmlm-send changes its behavior in several ways.
First, if SENDER is set, and the first line of dir/sublist has the form parent@parenthost, ezmlm-send insists that SENDER have the form parent...@parenthost.
Second, ezmlm-send demands that the message already have a Mailing-List field.
Third, ezmlm-send does not add its own Mailing-List field.
Fourth, ezmlm-send uses the incoming message number for the outgoing message, if the list is not archived and the incoming SENDER has the correct format. This allows you to refer bounce warning recipients to the main list for archive retrieval of the missed messages. If the sublist archives message, it is assumed that missed messages will be retrieved from the sublist archive.
The list still increments dir/num for each message. If the sublist is archived, use of incoming message number for archive storage would be a security risk. In this case, the local sublist message number is used.
In general, the use of a prefix is discouraged. It wastes subject line space, creates trouble when MUAs add non-standard reply indicators. However, many users expect it not because it is useful, but because they are used to it.
The -C switch prevents posts from being set to SENDER. Rather than just copying out subscriber address files, ezmlm-send has to parse them to look for SENDER. This makes it less efficient. Also, it is useful for the SENDER to see the post to know that it has made it to the list, and its context to other subscribers, i.e. where it came within the traffic of messages on the list.
Avoiding SENDER as a recipient is useful in small lists, such as small teams with varying members, where ezmlm serves mainly as an efficient tool to keep the team connected without administrator intervention. Here the overhead of subscriber list parsing is negligible.
If the list is indexed, ezmlm-send will keep a message index. rfc2047-encoded subject and from lines will be decoded. If dir/charset exists, ezmlm-send will eliminate redundant escape sequences from the headers according to the character set specified in this file. Only character sets using escape sequences need this support. Currently, supported are iso-2022-jp*, iso-2022-kr, and iso-2022-cn*. Only iso-2022-jp has been tested extensively.
The character set can be suffixed by : followed by a code. Recognized codes are Q for Quoted-Printable, and B for base64.
For ezmlm-send, this affects the format of the trailer, if a trailer is specified and if the message is a multipart mime message
Since the MIME parser doesnt decode inner MIME layers of a multipart/* message, mimekeep, mimeremove, and mimereject will be applied to the outer MIME layer only.
ezmlm-get(1), ezmlm-idx(1), ezmlm-manage(1), ezmlm-make(1), ezmlm-sub(1), ezmlm-unsub(1), ezmlm-reject(1), ezmlm(5), qmail-qmqp(1)