When a message is sent to a moderated mailing list, the Date: header of that message is set by the email program of the person sending the message.
However, if the message is approved at a later date, it is often best to have the Date: header of the message reflect the date when the message was sent by ListManager, rather than the authored date.
This setting sets the default for moderated messages to automatically rewrite moderated date headers.
You can still choose to rewrite (or not) the date headers of individual moderated messages by using Mailings:
Need Approval: Edit Mailing: Schedule.
This option determines whether helpful information is inserted into the headers of the messages ListManager sends.
These header lines tell people how to subscribe, unsubscribe, get help and contact the owner of the mailing list.
These header lines are now an official Internet standard. ListManager complies with the standard document, titled The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields and available at
http://www.isi.edu/in-notes/rfc2369.txt
A number of email programs recognize the headers and assist users in subscribing, unsubscribing, or obtaining help. As of November 1, 1997, Claris Emailer, Qualcomm Eudora and Pegasus Mail directly support or plan to directly support these headers. Even when a mail program does not directly support the headers, they are still useful. Most email programs allow the user to optionally view all headers, and thus they can see this additional, helpful information.
If you decide to include the List-Help headers, these three header will be added to your outgoing mail:
List-Subscribe: <mailto:subscribe-list1@yourcompany.com>
List-Owner: <mailto:owner-list1@yourcompany.com>
X-List-Host: kuno.yourcompany.com
Note: Most email programs do not show the mail headers, so for most lists, it makes sense to include the headers, as they do no harm.
If you choose to not include the List-Help headers, only the List-Unsubscribe header will be included. This header is included by default, because it is the most useful header. If you want to remove the List-Unsubscribe header, specify it as a header to be removed. See Utilities: List Settings: Sending to Your List: Header Rewrites.
Unlike other settings in Email Submitted Content, any changes you make to Add List Help Headers will also appear in mailings created through the ListManager web interface.
Note: If headers or footers are defined at multiple levels, i.e. server, site, or list, eachheader/footer will be added; one will not overwrite the other.
Rewrite Message ID Header
This option informs ListManager to leave the Message-ID header alone and instead use X-Lyris-Message-Id for that purpose.
The Message-ID syntax is rewritten by ListManager to put the recipient email address in it, for easier human reading of permanent failures.
Some users object to ListManager rewriting the Message-ID to be unique for each member, so this option allows you to disable this feature.
Unlike other settings in Email Submitted Content, any changes you make to Rewrite Message ID Header will also appear in mailings created through the ListManager web interface.
Append to SMTP Header
The message header is the part of the message that describes who the message is from, who it is addressed to, how the message should be displayed, and so forth. ListManager creates the correct header for your message automatically.
The optional text you specify will be appended to the end of the message header. A message header text has the form of Key: Value.
If you would like ListManager to include a Precedence: Bulk header, you must include it here.
If you want to add text to the header that is not a standard email header, you should prefix your key name with X- so that it does not interfere with normal operation of electronic mail. For example:
X-Legal: Contents Copyright 1997 Example Corp Ltd.
Unlike other settings in Email Submitted Content, any changes you make to Append to SMTP Header will also appear in mailings created through the ListManager web interface.
NOTE: If headers or footers are defined at multiple levels, i.e. server, site, or list, eachheader/footer will be added; one will not overwrite the other.