SPAM_FEEDBACK_PROBE

This configuration variable defines the domains for which to enable automatic processing of Spam Feedback Loops. Feedback Loop reports are sent automatically by some ISPs, such as AOL and Yahoo!, to organizations that are on their whitelist. Once configured, LISTSERV automatically parses the reports and implements the actions required by the whitelist agreement. This helps preserve whitelist status and reduce the number of spam complaints from subscribers.

There are two steps in configuring automatic feedback loop processing. The first is to define this configuration variable with the space-separated domain names for which to enable Spam Feedback Loops, for example AOL.COM or YAHOO.COM. The second step is to create a LISTSERV list dedicated to feedback loop processing. It can be configured as you wish as long as the special addresses from which the spam reports are sent are authorized to post to the list. Test the list carefully to make sure that archiving is working properly and that the list will not send any replies back. Then add Misc-Options= PROCESS_SPAM_FEEDBACK to the list configuration to activate automatic report processing.

If the message is recognized as a spam report and refers to a message that originated after you set the SPAM_FEEDBACK_PROBE configuration option, LISTSERV will:

1. Immediately delete the user from all LISTSERV lists, on the first spam report. This does not include Dynamic Query Lists, which are managed outside LISTSERV.
2. Not send any notification to the user.
3. Add the user to the spam feedback list with the NOMAIL option to keep a record of who has lodged spam complaints. The subscription date is set to the date of the first complaint and the last activity date is set to the date of the last complaint.
4. Log a SPAM_COMPLAINT record to the list's changelog, if one has been defined. You can use this information to remove the user from Dynamic Query Lists, if you have any such lists.

This ensures that no further mail will be sent to the user and minimizes the risk for further complaints (although experience has shown that people sometimes find old messages in their mailbox days or weeks later, which can lead to a handful of additional spam reports).

This configuration variable is not set by default.