How outbound content manager works, Content filter limitations, About message dispositions – Google Message Security for Google Apps Administration Guide User Manual
Page 205

Content Manager
205
Content Manager does not scan attachments that are:
•
ZIP or other types of compressed files
•
Microsoft 2007 Office documents
•
Over 100 MB
•
PDF files
How Outbound Content Manager Works
Outbound Content Manager filters the messages that your users send to
recipients outside your network. You create outbound content filters in the same
way you create inbound content filters, except that the User Quarantine and
Blackhole dispositions are not available.
Note:
•
If a user forwards a message to someone outside your network, Outbound
Content Manager scans it. The user who forwarded the message is
considered the sender.
Content Filter Limitations
You can create approximately 40 to 60 custom content filters per organization in
your organization hierarchy, depending on the number and complexity of the rules
you specify for the filters. This limit applies to the overall number of filters you
create for both Inbound Content Manager and Outbound Content Manager.
The value you specify for a rule—that is, the text for which you want to scan
messages—must be in ISO 8859-1 (Latin) character encoding.
Important:
If you use regular expressions to specify filter values, additional
limitations apply. For details, see “About Using Regular Expressions” on
page 218.
About Message Dispositions
For each content filter or compliance policy that you set up in Content Manager,
you must specify a message disposition. A disposition tells Content Manager what
action to take on a messages it captures. For example, Content Manager can
send the message to the user’s or an administrator’s quarantine in Message
Center, delete (blackhole) it, or return it to the sender (bounce it). It can also send
a copy of the message to an administrator’s quarantine, but let the message
through to its intended recipient.
For details about the dispositions you can use, see “Message Dispositions” on
page 248.