Difference between revisions of "Spam reporting"

Revision as of 21:21, 12 March 2014

The spam report service provides a convenient method for your users to report spam directly from the messages they receive, and/or allows you to maintain a queue of messages passed through the system for administrative reporting.

After enabling this service, messages will be retained for a short number of days to allow reporting of spam that has bypassed the spam filter.

Generating a report link will place a short message with a clickable link into all inbound messages so that users can self-manage reporting of spam that comes in. When a user clicks this link, they will be directed to the gwava quarantine and will need to log in to confirm their permission to process the report.

You can adjust the threshold for the size of messages that could be considered spam to reduce system overheads.

If you wish to customize the report information, you may do so. It is important that both the text and HTML versions of the overridden report are filled in, as each message may have any combination of text/html or no message body.

The HTML portion must be defined as full HTML. The following example is how you would define a two line report, including special characters:

Press the link to report this message as spam
<A HREF="$(release_url)">Click here & release</A>

Spam Message Queue

The spam report message queue maintains a copy of all recent messages that were not considered to be spam, and that conform to the queue storage criteria.

When a user reports a spam message has been let through, the search tool can be used to lookup the message and then reported with the provided buttons in the resulting list.

It is very important that only spam is reported. Reporting regular mail as spam can cause your spam scanning to become innacurate and start catching regular mail based on your feedback.