Managing exceptions
From GWAVA4
Contents |
Introduction
For every e-mail policy, there are often specific business reasons for altering that policy. You might normally have Attachment Filename filtering active, with an *.EXE filter and a Block service enabled. But a user in your organization may have a client (myclient@thatcompany.com) regularly e-mailing him/her with an EXE file.
Exceptions permit this distinction. When the message fires the *.EXE event, GWAVA checks to see if there are any exceptions entered (for myclient@thatcompany.com, for example). If so, the services (Block in this example) are not activated.
Source Exceptions and Destination Exceptions
You can enter both Source Exceptions and Destination Exceptions. The only difference between them is a Source Exception checks the address pattern against the originating address (the sender), while the Destination Exception checks the address pattern against the destination address(s) [the recipient(s)]
Exception Format
Like filters, exceptions can be either an address (joe@good.com), a wild card (*@good.com), or a regular expression. For more information on this, see Data input types.
How Exceptions Are Applied
Exceptions can apply at either the overall Event level or at the discrete filter level.
For example, the exception can be assigned at the Attachment Filename filtering level, in which case it will apply to all Attachment Filename filters (including ones added after the exception is created). Granting an exception at this level should be done with care, because often it permits unforeseen violations of your e-mail policy. Overall event exceptions may be assigned and viewed at the Exceptions interface discussed below.
Alternatively, for many events you can apply the exception at the discrete filter level. In this case, it might apply only to the *.EXE filter, not to other Attachment filename filters. For discrete filters, you can assign exceptions at either the Filter interface or the Exceptions interface discussed below.
Not all events currently expose a discrete filter exception, because for these events such a distinction makes little sense. Among these:
- Antivirus (would you want an exception for a specific virus?)
- Antispam
- Oversize
Filter Interface
From any filter interface, such as Attachment filename filtering, Fingerprinting, etc., you can conveniently view what exceptions are assigned to the discrete filter and add and remove these exceptions.
To add an exception, select either Source Exceptions or Dest. Exceptions using the scroll arrows (
or 
). Click the Edit button (
). Type the desired address for your exception, then click Add (
). Repeat process to add additional exceptions. Click OK (
) when finished. Save changes.
- TIP: It is easier to use the Filter Interface to add/view/edit address patterns when you wish to add or view multiple patterns to a specific discrete filter. For example, adding multiple addresses to the *.EXE attachment filename filter, or simply checking which addresses have been assigned as an exception to the Microsoft Word Fingerprint filter. On the other hand, if you wish to view what exceptions a specific user or pattern have been assigned ("So what does joe@mycompany.com have exceptions for? Fingerprinting? *.EXE? Oversized?"), the Exceptions interface is probably the more appropriate location to go.
Exceptions Interface
You can view, add, and remove address patterns from the Exceptions interfaces. The exception interface displays all currently active address patterns regardless of which event or discrete filter they are assigned to. It is a "user-centric" interface.
Here is an example of the Source Exceptions page, with three address patterns already added. The Destination Exceptions page functions in exactly the same manner.
You can see that there are exceptions for two specific mailbox addresses, as well as a wild card exceptions for an entire domain.
- NOTE: As you make changes to your configuration, the disk icon
in the upper right corner of the page will become active and the words SAVE CHANGES will appear. Do not forget to click the icon to save your changes before moving to another page, or your changes will be lost.
Viewing the exceptions assigned to the address pattern
Simply click on the folder icon (
) next to the address pattern, and the first level of a tree will be displayed:
]
Note the following:
- The exceptions are all attached to the trusted@source.com address, and will apply to mail coming from that address.
- This address has been completely excluded from the AntiSpam event.
- Some events have folder icons (
) next to them. This means that you can assign exceptions at either the overall event level, or at discrete filter levels.
- The check box (
) next to Attachment name is fully filled out. This means that trusted@source.com is excluded from all Attachment filename filtering events.
- The check box (
) next to Fingerprinting is not fully filled out. This means that one or more exceptions have been assigned at a discrete filter level. We will see these in a minute.
- The other events have unchecked check boxes (
), so the exception does not apply at any level of these events.
- You may click on any of the check boxes to edit the exception.
In this example, if I click on the folder icon next to Fingerprinting, the specific discrete filters that have been assigned exceptions will be displayed:
The PPD and EXE check boxes are selected, so trusted@source.com will be able to send messages with PhotoShop and Executable attachments. Notice that none of the other filters are checked off.
Contrast this with clicking on the folder icon next to Attachment name:
Because the parent check box has been activated, all child filters (including future ones that might be added later) are all part of the exception.
Adding a new address pattern
To add a new exception, type the address into the field shown and click Add Address. You may add wild card patterns or regular expressions as well.
Then, click on the folder icon () next to the address pattern, and select the events to which the exception applies. You can drill down one level deeper to assign specific discrete filter exceptions.
Deleting an address pattern
To remove an address pattern, simply click on the red X (
) next to the appropriate entry.
