This determines whether messages sent through this list are available in the list's message archives. Archiving is necessary to read and search messages posted through Aurea List Manager 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

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:

• No logs: This creates no transaction log for recipient information. This is the default setting.
• Non SMTP errors: This shows error information, but does not include SMTP information.
• All errors: This displays detailed information about all errors, including the errors which may have occurred when communicating with the mail server (SMTP errors). Given sufficient server resources, this setting is recommended.
• Errors and Successes: This displays detailed information about every transaction, creating a full log for both errors and non-errors. This option may consume significant server space, since it logs information for each recipient.

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 is 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 takes you to the Utilities: Administration: Server: Server Settings: Automatic Maintenance: Error Mail page, where the setting can be adjusted if necessary.

This setting determines if this mailing list accepts 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:

1. Create your parent and child lists as you normally create any ordinary lists, later we can then establish the parent-child relation between them.

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 need to create two members in sports-announcement, 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 are preventing members of multiple child lists from getting many copies when a message is sent via the parent list.

This selects the default segment mailings should go to when administrators create new mailings through the administrative interface. By default, mailings 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 want to be able to send to segments, contact your account executive. If you do not know who your account executive is, or for other queries, contact us through our website.

You can enable DomainKeys at the list level, and specify whether this setting acts in conjunction with the site level setting or independent of it. For more information, see Domainkeys FAQ and Setting Up and Using DomainKeys

Use the site setting for this list:

Uses DomainKeys, or not, depending on the Yes or No setting you chose in the Utilities > Administration > Sites > New/Edit Site > DomainKeys tab (this is, the site level setting).

Use the site setting for this list, but do not add Sender Header if signing. Uses the settings you chose in the DomainKeys tab, but does not include a sender heading regardless of site/domain matching

Yes, enable for this list: Uses DomainKeys regardless of the Yes or No setting you chose in the Utilities > Administration > Sites > New/Edit Site > DomainKeys tab (i.e., the site level setting).

Yes, enable for this list, but do not add Sender Header if signing Uses DomainKeys regardless of the Yes or No setting you chose in the Utilities > Administration > Sites > New/Edit Site > DomainKeys tab. Does not include a sender heading regardless of site/domain matching (see the note below)

No, disable for this list : Does not use DomainKeys regardless of the Yes or No setting you chose in the Utilities > Administration > Sites > New/Edit Site > DomainKeys tab.

There are three list-level DKIM/DomainKeys settings:

• DKIM signing
• DomainKey signing
• Third Party DomainKey signing

For more information, see Setting Up and Using DomainKeys and Domainkeys FAQ

Aurea List Manager allows you to exclude those who have received a certain amount of mail recently from receiving more mailings. By default, Aurea List Manager sends 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 does 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 Edit Recency. You are taken to Utilities > List Settings > Basic Information > Choose Recency. To remove a previously set recency setting, click Clear Recency.

This limit may be overridden on the Recipients tab when creating mailings.

This option determines whether the list is going to 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

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.

This option determines whether the list is going to 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 appears as though no recipients can detect HTML, which may not be a realistic number.

Aurea List Manager 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.