6.7 Creating HAM and SPAM Reporting Policy

IMPORTANT:This section only applies to SMG on Ubuntu.

These policies allow users to report messages that are good that were quarantined (ham) and bad messages that were allowed through (spam).

6.7.1 Spam Reporting

To enable Spam Reporting, which adds a link to the recipient message so they can report spam that had gotten through the system to the spam scanning corpus.

  1. On the workbench, add an Anti-Spam filter and enable Invert node logic, finally connect it to the Spam Reporting Service.

  2. Inverting the node logic is important because that allows non-Spam message to pass. The Anti-Spam filter checks the message against the spam corpus to determine if it is spam or not. Without inverting the node logic we would already believe the message to be spam and there would be no reason to report it.

  3. Anti-Spam Filter > Spam Reporting

  4. Invert node logic: Is this known Spam? No > Attach Spam Reporting link. If not inverter this will not put a spam link on if the message is known spam.

  5. When a user clicks on the link, they will be taken to a web page and told: Thank you for reporting the spam message, and the training corpus will be updated with the message. If they wait beyond the storage duration, they will be thanked, so as not to confuse them, and the message will not be able to be sent to the training corpus.

6.7.2 Ham Reporting

The opposite of Spam Reporting.

  1. On the workbench, add an Anti-Spam filter, and connect it to the Ham Reporting Service.

  2. This can be used with a Junk Folder. For example, on a smaller site without a quarantine for all users the Anti-Spam filter can be connected to a Add Header Line Service, to add a Junk Flag header that the mail client can have rules enabled for, a Message Tag to added a Spam header, and the Ham Reporting Service. If the user finds a non-spam message in their junk folder they can use the Ham Reporting link to report the false negative.