Error mail
Aurea List Manager by default handles all error mail, including bounces (transient and permanent failures). However, the error mail settings must be correct for your list in order for it to function properly.
By default, Aurea List Manager tries to send a message three times, one initial send, and two retries. If a mail server reports that an address is permanently non-deliverable, Aurea List Manager only attempts to deliver to it once for that mailing. This kind of bounce is a permanent failure. A message that is undeliverable for other reasons (For example, mailbox is full or mail server does not respond) is a transient failure. If an address is undeliverable for the initial send and all the retries, it is considered to have bounced once.
Even if a mail server initially accepts the message and later determines that the user does not exist, Aurea List Manager is going to record that address as having bounced. In this situation, the receiving mail server replies to Aurea List Manager with error mail. This error mail goes to the bounce email address and contains the user’s unique member ID number, so Aurea List Manager can track it back to the particular address unable to accept mail. This kind of bounce does appear in delivery reports, as the mailserver initially reported that it accepted the message. Many large ISPs (For example, AOL) accept all mail and bounce back undeliverables later.
The table below explains the fields available on the Error Mail tab:
| Field Name/Action | Description | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Hold Users |
This option determines whether members who bounce a great deal of mail have their membership automatically
By default, this setting is set to When people's email addresses go bad (for ecample, they change to another Internet Service Provider), each email message sent to their old address bounces back to Aurea List Manager. By default, Aurea List Manager analyzes the failures and determine who is causing them. If a member's email address appears to be invalid for several days in a row (based on your Bounce limit setting), Aurea List Manager automatically disables their membership so that Aurea List Manager no longer sends them mail In most situations, automatic holding of users is a desired feature. In some situations, such as with
internal mailing lists, where email address problems can be temporary (or must be repaired by a email
system administrator) you can disable this feature. ListManager is going to never put a membership on When a user is placed on hold, ListManager can send the user an email message indicating that this has
occurred as well as a copy of the most recent error message Aurea List Manager received from this user. This
notification message, if the user receives it, can be very helpful to the user in determining why their
email was being rejected by their mail system, and allows them to |
||||||||||||
|
Bounce Limit |
This is used to determine the number of consecutive failed deliveries an address may have before being set to Note The failed deliveries may be days, weeks, or months apart, so long as they are consecutive (that is, no successful deliveries between them). A successful delivery resets the count for an address, so addresses with intermittent delivery problems are not removed The default setting is two (2) bounces for announcement and email marketing lists, and five (5) bounces for discussion lists. If set to one (1), addresses that bounce are put on hold after only one permanent delivery failure When analyzing the failed deliveries, Aurea List Manager counts only one bounce per day, per member, so an email
address does not typically go on The lower the number, the more quickly bad email addresses are set to We recommend the following settings:
Note The failed send attempts are recorded in the |
||||||||||||
|
Redirect All Bounces to Email Address |
If blank, Aurea List Manager handles all bounced mail for you. If you do not want Aurea List Manager to handle your bounce mail, specify an email address to where all error mail should go This option is provided for advanced users, and it should be left blank unless you are prepared to handle the bounce mail at another address Any email address you specify here replaces the Mail From: header in your outgoing mail message. Normally, the mail transaction Mail From: address is the error handler of the server, and error mail is defined by Internet standards as going to this address. If you change this setting Aurea List Manager no longer receives error mail and is not going to be able to automatically process bounces, error messages, bad deliveries, etc. Important It is strongly recommended that you do not modify this setting |
||||||||||||
|
Notifying Users of Their Held Status |
When a member bounces too much email, their status can be changed to Aurea List Manager has the capability to send a notification message to people on hold, to tell them about their
status and give them the option of un-holding themselves. A member can unhold themselves by sending email
to If you choose to never notify, the member receives no notification, ever. Thus, they do not have a real opportunity to Although it is possible to inform users that their membership is on hold because of bounces, it is not recommended, since the address is bouncing mail, a hold notification might bounce as well. Notifying users of their held status can greatly slow down the performance of your Aurea List Manager server. |
||||||||||||
|
Notify How Often |
This setting determines the frequency at which Aurea List Manager notifies held members. You can choose to never notify held members, notify them every night, every few days or whatever interval you choose. This setting should be a number lower than that used for Notify for How Many Days, or members can never receive a held notification By default, your list is set to not notify held members. |
||||||||||||
|
Notify for How Many Days |
This setting determines for how many days a member who has been placed on hold should receive a notification message. This setting does not directly correlate with how many notifications the member gets, it only means that the member receives notifications for a specific duration By default, your list is set to never notify held members. Thus, you can determine how many notifications someone gets if you divide the Notify for How Many Days value by the Notify How Often value, and drop the remainder. For example, if your Held Notify Days is set to 11 and your Held Notify Interval is set to two, you divide 11 by two, and drop the remainder. These settings result in five notifications. |