Archive Messages
Determines whether messages sent through this list will be available in the list's message archives. Archiving is necessary to read and search messages posted through ListManager through the Discussion Forum Interface, RSS or NNTP. Digest and index editions of the list's postings also depend on there being archives for at least one day.
Not saving archives conserves disk space.
If you want your users to be able to receive digest or index editions, but do not want to keep archives, set the Save Archives setting to "Yes..." and set the Archive Days setting to "1" in Utilities: List Settings: Automatic Maintenance: Purging Archives.
Note: Changing the Save Archives setting from "Yes" to "No" will REMOVE already existing archives (gathered until that moment) once the scheduled task "Remove Archives" is activated (usually overnight, but settings may vary). There is no way to retrieve lost archives after the "Remove Archives" task executes; archives will be deleted permanently.
Recipient Logging Level
Transaction logs are created at the individual recipient level. Set the desired level of detail for the transaction logs from the drop-down menu. The choices are:
The default setting is "All errors." Creating a full log can hinder performance, as these logs can become large files, particularly for large lists with many members.
If the Bounce handling setting in Utilities: Administration: Server: Server Settings: Automatic Maintenance: Error Mail is set to "Yes, process all bounce reports in memory (faster)", then the following message will be visible below the recipient logging level:
Note: the server setting for Bounce Handling is set to process bounces in memory. Therefore, bounce information will not be available in the recipient logs.
The bounce handling link will take you to the Utilities: Administration: Server: Server Settings: Automatic Maintenance: Error Mail page, where the setting can be adjusted if necessary.
Enable This List as a Child List
This setting determines if this mailing list will accept messages submitted directly from another mailing list.
This option is used to create parent/child mailing lists, where sending mail to a parent list automatically sends to a child mailing list.
A typical scenario for setting up parent/child list is if you have multiple announcement lists and they are related in this way. For example, these lists could be in a parent/child relationship:
sports-announcements
soccer-announcements
tennis-announcements
If lists are set up in a parent-child relationship, messages you send to "sports-announcements" can be sent to members of "soccer-announcements" and "tennis-announcements" automatically. Or, you may just want to send to "tennis-announcements" and not to any other list.
Here are the instructions for setting up a parent/child list. Please follow these directions carefully, as the relationship is a little difficult to grasp:
1. First, create your parent and child lists as you would create any ordinary lists (you will later establish the parent-child relation between them). You should not use message wrapping in any list that will act as a parent, as these header/footers will be reproduced when the messages are posted to the children.
2. For each child list, go to Utilities: List Settings: Basic Information: Enable Features, and set Enable This List as a Child List to Yes.
3. For each child list, go to Utilities: List Settings: Discussion Group Features: Message Rejection Rules: Same Message Rules and set Allow Duplicate Posting to No, Duplicate Postings Should Be Rejected.
4. For each child list, go to Utilities: List Settings: Discussion Group Features: Message Rejection Rules: Same Message Rules and set Allow Cross-Posting to Yes, Cross-Posted Messages Will be Allowed.
5. For each child list, go to Utilities: List Settings: Discussion Group Features: Message Rejection Rules: Same Message Rules and set Cross-Posting and Duplicates to Make Sure that Multiple Copies of Cross-Postings are Removed.
6. For each child list, go to Utilities: List Settings: Basic Information: Enable Features and set Archive Messages to Yes, save and archive messages sent on this mailing list.
7. Decide who should be able to post to your mailing lists and make them a member of all the lists (parents and children) that their message should be distributable to. A person has to be a member of the parent and all its children in order for the message to be distributed. You should also set the security permissions for this person so that their post goes through the security tests you decide. For instance, you may want to allow any post from the person to automatically be approved, in which case making this member a list admin on the lists is best.
8. In each list that is to serve as a parent list, subscribe the child list's posting address as a member of the parent list. For example, you would create two members in "sports-announcements", with the email addresses "soccer-announcements@yourserver.com" and "tennis-announcements@yourserver.com". Child lists can also act as parents to other lists, so you can nest the parent/child relationship as deeply as you like.
If you have configured the lists to reject cross-posted duplicates, you will prevent members of multiple child lists from getting many copies when a message is sent via the parent list.
Default Segment
Select the default segment mailings should go to when administrators create new mailings through the administrative interface. By default, mailings will go to the entire list.
Some administrators may wish to specify a segment with administrators only as a safety measure so that if the sender neglects to specify the correct segment the mailing does not go to the entire list.
Sending to segments is a pro level feature. If you would like to send to segments, please contact your account representative at sales@lyris.com.
Default Recency Limit
ListManager allows you to exclude those who have received a certain amount of mail recently from receiving more mailings. By default, ListManager will send to everyone regardless of how much mail they have received recently.
Setting a recency limit for the list allows you to prevent recipients from mailings if they have received the amount of mail you specify here from any list on the server. In other words, mailings from any list "count" towards the tally of mailings to a particular address.
For example, if joe@example.com received four messages in the past week from list_a, and there is a recency limit on list_b to purge recipients who have received more than three mailings in the past seven days, joe@example.com will not receive the mailing to list_b, even though the messages joe@example.com received were from a different list.
By default, no recency limit is set. To set or edit your recency limit, click
This limit may be overridden on the recipientstab when creating mailings.
Default with Open Tracking
This option determines whether the list will provide open tracking by default or not. This is enabled by default for marketing list types, for other list types it can be set here to "yes" or "no".
Note that this feature is for reporting of email opens; if this is set to "no", it will appear as though there were no opens, which is most likely not a realistic number.
Opens cannot be tracked for recipients who cannot see HTML; however, if a clickthrough is registered for a recipient for whom there has been no opens, an open is registered for that recipient.
Default with HTML Detection
This option determines whether the list will detect HTML by default or not, that is, whether or not recipients can read and/or send HTML. This is enabled by default for marketing list types, for other list types it can be set here to "yes" or "no".
This is a reporting feature, and if set to "no", it will appear as though no recipients can detect HTML, which may not be a realistic number.
Warn Sender if No Recipients Found
ListManager can inform the administrator sending a mailing that no recipients were found, and thus no mailing sent. It is possible that no mailing may be sent if it is queued for a segment without recipients, or to a segment or list that has already received an identical message and thus duplicate messages for these recipients have been automatically purged.
When set to "yes", this option informs the sender via email if a mailing was not sent because no recipients were found to receive the message. Set to "no" if you do not want senders to be informed.