The sections below help you compare your Postini features to the email security features in Google Apps. Keep in mind that the new features in Google Apps operate differently than those in Postini. Some Postini settings don't have an exact equivalent to the new features, so you will want to re-examine your business requirements and ensure that your new configuration still meets your needs. Note also that org structures in the Google Admin console may differ from Postini, so you may need to refactor your settings because of the different structure as well as the new org inheritance rules in Google Apps (see Create an organizational structure).

For more details and instructions on transferring your Postini settings to the Google Admin console, see Using the Postini Settings Output page. The Settings Output page can be accessed from the Transition tab in the Postini Administration Console. It displays details about the settings that you configured for each of your Postini organizations.

For instructions on completing your transition to Google Apps, see the Transition Guide.

Spam notifications and reports

Postini names: Quarantine Summary Reports / Message Center
Google Apps Equivalent: Gmail Spam folder

New functionality in Google Apps:

Gmail Spam folder - Users can easily access their Spam folder from the left-navigation menu in Gmail. Clicking the Spam folder displays all messages that have been blocked by spam filtering.

Reporting spam in Gmail - Users can mark messages as spam in Gmail by clicking the Report spam button. This provides specific information to Google filters about a user's mail preferences, and Google customizes the filters accordingly.

Marking messages as Not spam - Users can mark a message as Not spam, and the message is automatically moved to their Inbox. Similar to clicking the Report spam button, this also provides information to Google filters about a user's mail preferences.

Why messages are marked as Spam - If a user clicks the Spam label and opens one of the messages, that user will see a message at the top with a brief explanation about why that particular message was marked as Spam. For more details, see Why messages are marked as Spam.

Differences in functionality:

Auto-purge - Spam is automatically purged from the Postini quarantine after 14 days, while spam is auto-purged from the Gmail Spam folder after 30 days.

Postini functionality not included in Google Apps:

Quarantine redirect - Administrators are no longer able to centralize and view all messages blocked by spam filtering into a single repository (for example, with the Postini quarantine redirect).

Disabling user access to the Spam folder - There is no option to disable users' access to view messages that have been blocked as spam.

Content filters

Postini name: Content Manager
Google Apps equivalent: Content compliance / Objectionable content

New functionality in Google Apps:

Set up content policies for inbound, outbound, and/or internal mail - With Content compliance and Objectionable content, you can set up policies for inbound, outbound, and/or internal mail (sending/receiving within the set of domains associated with your organization). With Postini Content Manager, you can set up policies for inbound and outbound messages only, but not for messages sent and received internally.

Notify others (bcc) when a message matches a content policy - You can BCC an administrator or alternate recipient when messages match a Content compliance or Objectionable content policy.

Add custom text to a message subject or header when a message matches a content policy- Optionally, you can enter a string to prepend to the subject and/or an extra header when messages match a policy.

Create a unique custom rejection message for each individual policy - When messages match a content policy, you can choose to have the messages rejected before reaching the intended recipient. With this feature, you also have the option to enter customized text for the rejection notice.

Messages are checked against all existing Content compliance / Objectionable content policies - In Google Apps, messages are checked against all existing Content compliance / Objectionable content policies. For Postini, a message bypasses remaining policies after matching a previous policy.

Match against Sender/Recipient header address vs. Sender/Recipient SMTP envelope address (Content compliance only) - Postini Content Manager filters can only match against the sender/recipient header address, while Content compliance filters in Google Apps can also match against the SMTP envelope address. Headers are what's visible in an email client (for example, Gmail, Outlook, or Lotus Notes), while the envelope addresses are what mail servers use to route messages. Normally, both of these values are the same, but sometimes this isn't the case. Being able to differentiate between headers and envelope addresses provides you with a more powerful tool to manage email.

Postini functionality not included in Google Apps:

Bypassing spam filtering
There is no option to allow messages that match a Content compliance or Objectionable content policy to bypass spam filtering.

Option to quarantine or blackhole
In Postini, you can create a content rule to bounce, blackhole, or quarantine messages that match a filter. In Google Apps, you can only set up a filter to reject (which is the same as the bounce disposition in Postini).

Attachment filters

Postini name: Attachment Manager
Google Apps equivalent: Attachment compliance

New functionality in Google Apps:

Set up attachment policies for inbound, outbound, and/or internal mail - With Attachment compliance, you can set up policies for inbound, outbound, and/or internal mail (sending/receiving within the set of domains associated with your organization). With Postini Attachment Manager, you can set up policies for inbound and outbound messages only, but not for messages sent and received internally.

Strip attachments from messages that match a policy - With Attachment compliance, you can set up policies to have all attachments stripped from messages when those messages match the policy, while allowing the remainder of the message through to intended recipient(s). (Note: When attachments are stripped from a message, all attachments are stripped. You cannot strip selected attachments.)

Notify others (bcc) when a message matches an attachment policy - You can BCC an administrator or alternate recipient when messages match an attachment policy.

Add custom text to a message subject or header when a message matches an attachment policy - Optionally, you can enter a string to prepend to the subject and/or an extra header when messages match a policy.

Reject messages based on file name - You can add a string to an Attachment compliance policy that will look for a match on any part of an attachment file name. The expression need not match the entire name, and case is ignored.

Create a unique custom rejection message for each individual policy - When messages match an attachment policy, you can choose to have the messages rejected before reaching the intended recipient. With this feature, you also have the option to enter customized text for the rejection notice.

Create lists of approved senders for each individual policy - With Attachment compliance, you can create or reuse lists of Approved senders which can exclusively bypass individual attachment policies.

Messages are checked against all existing Attachment compliance policies in Google Apps - Messages are checked against all existing Attachment compliance policies in Google Apps, whereas in Postini a message bypasses remaining policies after matching a previous policy.

Postini functionality not included in Google Apps:

Binary scanning - There is no binary scanning in Gmail, so it is possible for a sender to circumvent an Attachment compliance policy by changing the name of the file extension.

Scanning inside compressed files - Gmail scans the filenames of files inside archives, including encrypted archives and nested non-encrypted archives. However, the inner archives of an encrypted archive cannot be scanned.

Rejection of executable files - Executable files sent to Gmail recipients are currently always rejected, regardless of the attachment policy. With Postini, you can set up an Attachment Manager filter to quarantine these messages so that users can view the messages in the Message Center.

Approved senders - by sender address

Postini name: Approved Senders (located in the Senders List settings)
Google Apps equivalent: Approved senders (located in the Spam settings)

New functionality in Google Apps:

Create and reuse multiple Approved sender lists - You can create and reuse multiple Approved Sender lists and assign a name for each list (can also be used in Attachment compliance).

Sender authentication - In Postini, Approved Sender addresses that were spoofed were allowed to bypass Postini spam filtering. In Google Apps, messages sent by Approved Sender addresses will only bypass Gmail spam filtering if they pass either a DKIM or SPF verification check or are verified as being sent from Google Apps. (You have the option to allow some or all addresses to be unverified -- for example, to allow mail from sites that do not support verification).

No character limits - There are no character limits for approved senders in Google Apps.

Differences in functionality:

Spam filtering -- Gmail spam filtering is more lenient on messages from addresses in the user's contacts.

Approved senders - by IP address

Postini name: IP Passthrough and Inbound Content Manager rule
Google Apps equivalent: Approved senders

New functionality in Google Apps:

One text field for configuring approved senders - You can set up approved senders from one text field in the Google Admin console, while Postini requires a combination of an IP Passthrough rule and a custom Inbound Content Manager rule.

IP ranges using CIDR Notation - In the Google Admin console, you can add IP ranges using CIDR notation.

Differences in functionality:

Global setting in Google Apps - Approved senders by IP address is a global setting in Google Apps. In Postini, it is applied at the email config org levels.

Blocked senders - by sender address

Postini name: Blocked Senders (located in the Senders List settings)
Google Apps equivalent: Blocked senders

New functionality in Google Apps:

No character limits - There are no character limits for approved senders in Google Apps.

Add a domain to a Blocked Sender list while excluding specific addresses from that domain - In Google Apps, you can add a domain to a Blocked Senders list while excluding specific addresses from this domain. For example, you can block the domain hotmail.com, while allowing messages from meghan@hotmail.com.

Differences in functionality:

Blocked senders are rejected in Google Apps - Messages that match a Postini blocked sender rule are quarantined while messages that match a Google Apps blocked sender rule are rejected.

Postini functionality not included in Google Apps:

User level blocked senders
In Google Apps, administrators cannot create user level blocked senders. (Users need to set up blocked senders using a custom filter in Gmail.) However, repeatedly marking messages in Gmail from a particular sender as spam will have the effect of future messages going to spam.

Blocked senders - by IP address

Postini name: Connection Manager IP Block
Google Apps equivalent: Custom Content compliance rule

New functionality in Google Apps:

Setting can be applied at the user organization level - In Google Apps, you can set up blocked senders by IP address at the organization level.

Differences in functionality:

Content compliance rule - In Google Apps, an IP Blacklist is achieved by setting up a custom Content compliance rule that targets the IP in the header or raw message. In Postini, it is applied by adding the IP to a Connection Manager Block list.

Postini functionality not included in Google Apps:

Expiration dates - In Google Apps, you cannot set up expiration dates for approved senders.

Compliance footers

Postini name: Compliance Footer
Google Apps equivalent: Append footer setting

New functionality in Google Apps:

Google Apps provides the following new functionality for compliance footers:

• Rich text editor toolbar
• Multiple footers can be added to a single message
• No character limits
• The footer is added prior to DKIM signing, so it will not break DKIM signatures.
• A duplicate footer is not inserted when messages are sent to groups
• Exclude compliance footers from messages sent to internal recipients