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

Quarantine Summary & Notifications 167
See “Default Notifications with Tokens” on page 388 for information on
customizing notifications and a list of all tokens.
In a custom notification, why are header fields such as Date, To, From, &
Subject put into the body of a mail message?
The field that contains the custom notification has an extra line break between two
fields or above the first field in the text input field, which contains notification text.
According to the SMTP RFC 2821, section 2.1, there is a (Carriage
Return, Line Feed) character right at the beginning of a new line between the
headers & the body of a message. Remove the extra to resolve the
issue.
To remove the extra tag:
1. In the Administration Console, go to Orgs and Users > Orgs.
2. Click the name of an organization in the organization list.
3. On the Organization Management page, under Organization Settings, click
Notifications.
4. Click the name of the affected notification.
5. Look for a line break at the top of the notification template, or between two of
the header lines near the top of the template.
6. Remove the line break, then click Save Text.
See “Customizing Notifications” on page 383 for information on customizing
notifications and tips for formatting.
Why do my custom notifications get bounced by my mail server?
Your template does not include the Date, To, From, and Subject headers listed in
the default templates. The template headers are used when generating your
notifications. Since the headers are common to all email messages, their absence
causes your mail server to reject your notifications. See “Default Notifications with
Tokens” on page 388 for more details on this.