Bad Address Suppression

SimpleMH’s Bad Address Suppression feature suppresses sends to email address / ListID combinations that have been identified as bad due to any of the following:

1. A bounce_bad_address event, which occurs when GreenArrow Engine determines that any email address is bad due to bounce(s).
2. An scomp event, which occurs when a subscriber clicks on their ISP’s equivalent to the “This is spam” button, and a valid feedback loop registration is in place.
3. An engine_unsub event, which occurs when a subscriber clicks on a SimpleMH unsubscribe link, or a List-Unsubscribe header is used to unsubscribe.

Bad address suppression is ListID specific, meaning if each Mail Class is given its own ListID, each will maintain its own, separate list of which addresses to suppress sends to. If all Mail Classes use the same ListID, then they’ll share a common list of addresses to suppress sends to.

This feature can be enabled and disabled by editing the $BAD_ADDRESS_REMOVE value in the simplemh-config file.

If the feature is enabled, messages intended for suppressed addresses will be rewritten to be delivered to a special domain that will accept and discard all emails. The configuration directive simplemh_bad_address_dev_null_domain defines this special domain, and the default value for this directive is as follows:

general {
  simplemh_bad_address_dev_null_domain badaddress.discardallmail.drh.net
}

If the address [email protected] is subject to Bad Address Suppression, and the simplemh_bad_address_dev_null_domain directive is defined as above, the address will be rewritten as

[email protected]

so as to make sure that [email protected] does not receive this email.

With this coniguration in place and set as described above, any deliveries to the domain badaddress.discardallmail.drh.net can be easily seen in statistics for the send and considered to have been suppressed.