Platforms

All 16.0 and following


Abstract

Determines what action(s) to take when LISTSERV receives spam complaints through AOL feedback loops.


Example

z/VM:

SPAM_FEEDBACK_ACTION = 'DELETE SERVEDROP'

Unix:

SPAM_FEEDBACK_ACTION="DELETE SERVEDROP"

export SPAM_FEEDBACK_ACTION

Windows:

SPAM_FEEDBACK_ACTION=DELETE SERVEDROP


Details

SPAM_FEEDBACK_ACTION determines how LISTSERV should handle spam complaints arriving through AOL Feedback Loops. By default, when a spam complaint is received through an AOL Feedback Loop, LISTSERV will:

        1. Immediately delete the AOL 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 AOL user.
        3. Log a SPAM_COMPLAINT record to the list's change log, if one has been defined. You can use this information to remove the AOL user from Dynamic Query Lists, if you have any such lists that may contain AOL users.
        4. Serve the AOL user off with the DROP option, which prevents the user from accidentally re-subscribing to the list.

This default behavior is equivalent to DELETE SERVEDROP.

Possible configuration options, include (all space-separated actions are taken in turn):

        • DELETE: The AOL user is deleted from all LISTSERV lists.
        • SERVEOFF: The AOL user is served off.
        • SERVEDROP: The AOL user is served off with the DROP option.
        • NONE: No action is taken other than logging an entry to the list's change log (if defined).
        • LOGALL: An advanced option for customers operating multiple LISTSERV instances, which collects a central copy of all spam reports and forces them to be logged on that instance even if the reports are for another instance.


Default Value

DELETE SERVEDROP


See Also

SPAM_FEEDBACK_PROBE