Automatic maintenance error mail

• Complaint action

This options specifies how ListManager handles complaints, such as when the recipient marks the message as Spam.

Settings:

• Unsubscribe and ban email address across all lists on server

When ListManager receives a complaint, it automatically unsubscribes the email address from all lists on the server and create a ban for that email address.

• Unsubscribe and ban email address across all lists on the site

When ListManager receives a complaint, it automatically unsubscribes the email address from all lists on the site and create a ban for that email address.

• Unsubscribe and ban email address for the list only

When ListManager receives a complaint, it automatically unsubscribes the email address from the list and create a ban for that email address.

• Unsubscribe email address for the list only; do not create ban

When ListManager receives a complaint, it automatically unsubscribes the email address from the list but does not create a ban for that email address.

• Bounce Handling

This option sets whether permanent failures are handled in memory, which may be faster, or if they are saved in the incoming mail database, and processed there.

When a message mailing is sent out to its recipients, some of the receiving mail servers initially accepts the messages but then send a notice back saying the recipient could not receive the message. Aurea List Manager automatically tracks these messages, and determines when an email address has become invalid.

Settings:

• Keep bounce messages to research user issues

Aurea List Manager processes these bounce messages in the incoming mail queue, and this data is available when viewing the attempted mail history for individual members. NOTE  We recommend that you choose this setting; as a result of the new Deliverability feature, this allows you to see information about bounces in member history and view complaints in the Complaints reports.

• Don't keep the bounce message text

Aurea List Manager still processes the error mail, but does not record the reason, making processing these messages faster and more efficient.

• Auto-Hold Users

If set to No, each list may specify whether or not it puts members that bounce too much mail in Utilities: List Settings: Automatic Maintenance: Error Mail: Hold Users. If set to Yes, Hold Users are disabled for every list on the server. You might want to disable holding members if your server is having network connectivity problems. You may set individual members to never be put on hold regardless of delivery problems in Members: View Members: Edit Member: Advanced Settings: Hold User.

• Disable From: Checking

When set to "No" ListManager checks the From: field of incoming mail for spam and error messages using a list of regular expressions. To disable From: checking, set to "Yes".

For example, a message from postmaster@somedomain would normally be blocked, because postmaster@ is an automated address that usually sends delivery errors. However, a real person might use their postmaster@ account to belong a ListManager list and you might want to allow this.

These are the regular expressions ListManager looks for in the From: field, if From: checking is not disabled:

"\\|POST.*MASTER"
"\\|WPUSER"
"\\|$EMD"
"\\|VMMAIL"
"\\|MAIL .*SYSTEM"
"\\|MAISER"
"\\|MAIL.+AGENT"
"\\|MAIL.+DAEMON"
"\\|TCPMAIL"
"\\|BITMAIL"
"\\|MAILMAN"
"\\|^LISTMAN"
"\\|^LISTSERV"
"\\|^MAJORDOMO"
"\\|^LISTPROC"
"\\|^SERVER"
"\\|^LYRIS$"
"\\|^CRENLIST"

• Disable Subject: Checking

When set to No Aurea List Manager checks the Subject: field of incoming mail for spam and error messages using a list of regular expressions. To disable Subject: checking, set to Yes.

For example, Aurea List Manager normally blocks messages with a subject line of Out of Office. Messages with that subject are typically auto-responder members, which inform people that they cannot answer their email in a timely manner. Blocking messages of that type prevents useless messages from going out to the list and prevent mail loops.

These are the regular expressions ListManager looks for in the subject, if subject checking is not disabled:

"DELIVERY.*ERROR"
"\\|DELIVERY.*REPORT"
"\\|DELIVERY.*PROBLEM"
"\\|WARNING.*FROM.*UUCP"
"\\|USER.*UNKNOWN"
"\\|UNDELIV.*MAIL"
"\\|UNDELIV.*MESS"
"\\|PROBLEM.*DELIVER.*MAIL"
"\\|PROBLEM.*DELIVER.*MESS"
"\\|CAN.*DELIV.*MAIL"
"\\|UNABLE.*DELIV.*MAIL"
"\\|UNABLE.*DELIV.*MESS"
"\\|MAIL.*DELIV"
"\\|MESS.*DELIV"
"\\|FAIL.*MAIL"
"\\|FAIL.*MESS"
"\\|MAIL.*FAIL"
"\\|MAIL.*RETURN"
"\\|RETURN.*MAIL"
"\\|MAIL.*ERROR"
"\\|MAIL.*RECEIV"
"\\|MESS.*RECEIV"
"\\|MESS.*DELIV"
"\\|MAIL.*DELIV"
"\\|INTERCEPT.*MAIL"
"\\|WAITING.*MAIL"
"\\|READ.*RECEIPT"
"\\|RECEIPT.*NOTIFIC"
"\\|STATUS.*SIGNAL"
"\\|ERROR.*CONDITION"
"\\|NO.*REQUEST.*FOUND"
"\\|AUTO.*REPLY"
"\\|AUTO.*GENERAT"
"\\|AUTO.*ANSWER"
"\\|WAITING.*MAIL"
"\\|.*ON.*VACATION"
"\\|VIA.*VACATION"
"\\|CONCIERGE.*NOTICE"
"\\|AWAY.*FROM.*MAIL"
"\\|CAN.*ANSWER"
"\\|CAN.*REPLY"
"\\|OUT.*OFFICE"
"\\|MESSAGE.*CONFIRMATION"
"\\|ABWESENHEITSNOTIZ" // german vacation notification
"\\|RECEIPT OF.*MESSAGE"
"\\|OUT.*TOWN"

• Disable First Line Checking

When set to "No" ListManager checks the subject and body of incoming mail for command and unsubscribe requests using a list of regular expressions. To disable first line checking, set to "Yes".

For example, a message sentence starting with "please remove" would normally be blocked, because it looks like an unsubscribe request sent to the list.

These are the regular expressions Aurea List Manager looks for in the first line, if first line checking is enabled:

"^[ \r\n\t]*LOGIN"
"\\|^[ \r\n\t]*LOGON"
"\\|^[ \r\n\t]*DELETE"
"\\|^[ \r\n\t]*UNSUBSCRIBE"
"\\|^[ \r\n\t]*REMOVE"
"\\|^[ \r\n\t]*PLEASE REMOVE"
"\\|^[ \r\n\t]*PLEASE DELETE"
"\\|^[ \r\n\t]*PLEASE UNSUBSCRIBE";