Create or edit an Inform

Informs are applied to content rules using the Generate an Inform action in the What to Do? section of the rule. You must create an Inform before you can apply it to a content rule.

To create or modify an Inform:

1. Navigate to Policy > Policy References > Informs. The Manage Informs page is displayed.
2. Click New to create an Inform. To edit an existing Inform, select an entry from the list and click Edit.

3. Edit the Overview panel and provide the Inform with a Name or any Notes you want to include to describe it. For example, you might include a note describing how the Inform or its configuration form part of a policy. Click Save.

4. In the Inform Content panel, configure details about the content of the Inform message:

   1. Set the From address. This is the email address which is displayed as the "From:" address in the Inform. When setting the From address, select from the following options:

      Administrator: Sends an Inform from the Gateway Administrator email address.

      Server: Sends an Inform from the Gateway email address. This is the default email account.

      This email address: Sends an Inform from an email address that you specify.

   2. Enter an appropriate Subject. This text appears in the subject line of the Inform.

   3. Enter your Inform text. This text appears in the body of the Inform. You can use Plain Format or HTML Format.

      Tokens you can use

      Token	Description
      %ADMIN%	The administrator account email address used by the Policy Engine.
      %AREANAME%	The name of the message area containing the message.
      %DATE%	The date the original message was sent.
      %DETECTED%	Items detected by the What To Look For? clauses in invoked content rules.
      %LOCALDATE%	The date the original message was sent, shown in the Gateway's local timezone.
      %MANAGE_MESSAGE%	A manage message link that can be added to a Plain Format inform message. This token is only applicable to Secure Email Gateway and Secure Exchange Gateway. For example, this token should not be used in informs if Secure Email Gateway and Secure Web Gateway are peered.
      %MODIFIED%	Content rules that triggered, and hence modified the message.
      %POLICY%	A list of the content rules invoked on the message.
      %PRIMARYTHREATS%	The threat type and name detected in a message. The values are separated by a colon, for example, VIRUS:EICAR.
      %RCPTS%	A list of the recipients. (This is a concatenated list of all the "Recipient" responses.)
      %RECOGNISED%	A list of the Gateway format managers that recognized formats in the message (such as SMTP, text, HTML).
      %REMOVEDNAMES%	A list of the names of any removed attachments.
      %RESPONSES%	The values of all the response tokens.
      %SENDER%	The email address of the sender of the original message.
      %SERVER%	The Gateway server email address.
      %SUBJECT%	The subject of the original message.
      %UNIQUEID%	The Mail ID: a unique ID the Gateway assigns to a message.

      To add the Manage Message link that allows the Inform recipient to release a message directly from a message area, use the %MANAGE_MESSAGE% token (in Plain Format) or use the Create Manage Message link button (in HTML Format). See the Manage messages using Informs section below for more information.

   4. Select from the following Mail Policy Options:

      Do not include either the original or modified message: Sends an Inform only. The recipient does not receive the message that triggered the content rule.

      Include original message: Sends an Inform, including the original message that triggered the content rule.

      Include modified message: Sends an Inform, including any modifications made by the Gateway during message processing. For example, the Gateway might have added an annotation, removed an attachment, or cleaned a virus.

      Include textual analysis results: Sends an Inform, including the results of any specified text analysis which the Gateway attaches as a separate HTML file to the Inform.

5. Click Save.
6. Apply the configuration. Any group changes should be applied to each Gateway in a peer group.

See also...

• What To Do? actions

• Tokens in Content Rules and Policy References

• System Logs