Joe Scharf
posted this on March 04, 2010 11:57

About the Spam Checker Filter
The Spam Checker filter, located on the Filters section of the Sendgrid website is useful when your web application allows your end users to create content that is then emailed through your SendGrid account. Since emailing user generated content is hard to monitor and can often be abused by spammers, the Spam Checker filter can provide notification when emails are detected that exceed a predefined spam threshold.
Using the Spam Checker Filter
The spam checker filter is enabled by dragging the filter into the right column of enabled filters. Once enabled, you can click on settings to define the Spam Threshold and URL to post spam messages parameters:

Spam Threshold: Emails with a spam score over this value will be considered spam and will not be delivered to the recipient. If the URL to post spam messages is provided we will POST a notification message to this URL (see HTTP POST details below).The default spam threshold is 5.0, but you can set this to any value you wish. We use SpamAssassin to process the spam checks for this filter, so you can base your Spam Threshold setting on values typically used with SpamAssassin
URL to post spam messages (optional): SendGrid will send a HTTP POST request when it detects emails that are considered spam.
HTTP POST details
The HTTP POST request that you receive at the designated URL will contain the following two parameters:
Comments
You need to list the range of valid values for the Spam Threshold for this to be useful.
It would be cool if we could run this test using the API. I'd like to be able to check if a message content is spammy before it is sent. Thanks!
+1 to Chris
+1 to Chris, I too would like to be able to check content for spammy-ness _before_ sending.
Also, it'd be extremely useful if the HTTP POST back to me had my custom fields in it like the event notification does, or at least the message ID of the email that was attempted. That way I could easily track things back to the original message and user.