Google Message Security for Google Apps Administration Guide - Manual (Page 170)

170 Message Security for Google Apps Administration Guide
Where Spam Filtering Is Managed
You manage spam filtering at the following locations:
• Organization level Enable Blatant Spam Blocking for users in the org, and
choose a spam disposition—the method of disposing of filtered spam, for
example, by changing how it’s quarantined, or by not quarantining it at all.
Configure Null Sender Disposition to dispose of messages that do not contain
an SMTP-envelop sender address.
If your service is provisioned with Outbound Services, then you also have the
option to turn on Null Sender Header Tag Validation. For more information on
this feature, see “Configure Null Sender Header Tag Validation” on page 175.
• Default User Define user-level spam settings that will apply to new users
added to the org. This includes enabling spam filtering in the first place,
adjusting how aggressively to filter spam, and filtering specific spam
categories even more aggressively. Making these settings for a Default User
is how you apply a single filtering policy across an organization.
• Specific User You can modify user-level spam settings for an individual user,
as well. But this isn’t recommended if you want to maintain spam filtering
policies across an org.
• Message Center You can optionally allow users to modify their own filter
levels by granting them appropriate User Access permissions to the Message
Center. See “Control What Users Can View and Modify” on page 138.
For more information on these levels of management, see “What Settings Are
Made Where” on page 29.