Difference between revisions of "Source Address Exception"
(→Level 1) |
(→Level 2) |
||
| (2 intermediate revisions by one user not shown) | |||
| Line 5: | Line 5: | ||
user@domain.com | user@domain.com | ||
| − | The address exception should exactly match the source address listed on the message. Source Exceptions also recognize wildcards, and, though it is not recommended, entire domains may also be specified. (i.e. *@domain.com) However, if a simple wildcard is specified, such as *msn.com, then any message with 'msn.com' included in the address will be matched with the exception and will pass the selected | + | The address exception should exactly match the source address listed on the message. Source Exceptions also recognize wildcards, and, though it is not recommended, entire domains may also be specified. (i.e. *@domain.com) However, if a simple wildcard is specified, such as *msn.com, then any message with 'msn.com' included in the address will be matched with the exception and will pass the selected events. |
After adding the exception, make sure you select the events to apply the exception to, then save the change by clicking the colored disk to make the exception active. | After adding the exception, make sure you select the events to apply the exception to, then save the change by clicking the colored disk to make the exception active. | ||
== Level 2 == | == Level 2 == | ||
| − | GWAVA is designed to avoid needing exceptions. When using the Signature spam engine, there should | + | GWAVA is designed to avoid needing exceptions. When using the Signature spam engine, there should be no reason to create exceptions on a regular basis, as caught mail will be due to a setting in one of the other filters. If mail is caught incorrectly by the oversized message, fingerprint, subject or body filters, etc...the offending engine should be adjusted. Adjust the interface settings if exceptions are created regularly; the exception list should be used sparingly, when no other option applies. |
| − | be no reason to create exceptions on a regular basis, as caught mail will be due to a setting in | + | |
| − | one of the other filters. If mail is caught incorrectly by the oversized message, fingerprint, subject | + | |
| − | or body filters,etc...the offending engine should be adjusted. Adjust the interface settings if exceptions | + | |
| − | are created regularly;the exception list should be used sparingly, when no other option applies. | + | |
| − | GWAVA provides the option to create exceptions to the event interfaces, to allow specific messages | + | GWAVA provides the option to create exceptions to the event interfaces, to allow specific messages or addresses to pass filters that would otherwise have blocked them. An exception in GWAVA consists of two main parts: the identifying item and the event interface(s) it is exempted from. Until you have specified both, the exception will not be valid and cannot be saved. |
| − | or addresses to pass filters that would otherwise have blocked them. An exception in GWAVA | + | |
| − | consists of two main parts: the identifying item and the event interface(s) it is exempted from. | + | |
| − | Until you have specified both, the exception will not be valid and cannot be saved. | + | |
The different exception pages are essentially the same, though their function and syntax vary. | The different exception pages are essentially the same, though their function and syntax vary. | ||
Make sure you use the appropriate exception for each situation. | Make sure you use the appropriate exception for each situation. | ||
| − | The exception menu items which have folders are expandable to allow the selection of specific filters | + | The exception menu items which have folders are expandable to allow the selection of specific filters inside each event interface. For example, this allows the creation of an exception from specific file types from the fingerprinting system, instead of the entire event filter, though the entire filter may also be selected. |
| − | inside each event interface. For example, this allows the creation of an exception from specific file | + | |
| − | types from the fingerprinting system, instead of the entire event filter, though the entire filter | + | |
| − | may also be selected. | + | |
| − | If an expandable event interface does not have any filters, it will show a “No items found” notification. | + | If an expandable event interface does not have any filters, it will show a “No items found” notification. Since each exception adds time, though negligible, to the scanning process, only add necessary exceptions to the system. |
| − | Since each exception adds time, though negligible, to the scanning process, only add necessary | + | |
| − | exceptions to the system | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Latest revision as of 21:23, 11 March 2014
[edit] Level 1
The Source (From:) Exceptions are based on the 'From:' address listed for the message. The majority of exceptions are created here, as it is the easiest exception to correctly create. Source exceptions are used to allow an outside address to pass by a specific filter or filters. These exceptions are specified in the following syntax:
user@domain.com
The address exception should exactly match the source address listed on the message. Source Exceptions also recognize wildcards, and, though it is not recommended, entire domains may also be specified. (i.e. *@domain.com) However, if a simple wildcard is specified, such as *msn.com, then any message with 'msn.com' included in the address will be matched with the exception and will pass the selected events. After adding the exception, make sure you select the events to apply the exception to, then save the change by clicking the colored disk to make the exception active.
[edit] Level 2
GWAVA is designed to avoid needing exceptions. When using the Signature spam engine, there should be no reason to create exceptions on a regular basis, as caught mail will be due to a setting in one of the other filters. If mail is caught incorrectly by the oversized message, fingerprint, subject or body filters, etc...the offending engine should be adjusted. Adjust the interface settings if exceptions are created regularly; the exception list should be used sparingly, when no other option applies.
GWAVA provides the option to create exceptions to the event interfaces, to allow specific messages or addresses to pass filters that would otherwise have blocked them. An exception in GWAVA consists of two main parts: the identifying item and the event interface(s) it is exempted from. Until you have specified both, the exception will not be valid and cannot be saved.
The different exception pages are essentially the same, though their function and syntax vary. Make sure you use the appropriate exception for each situation.
The exception menu items which have folders are expandable to allow the selection of specific filters inside each event interface. For example, this allows the creation of an exception from specific file types from the fingerprinting system, instead of the entire event filter, though the entire filter may also be selected.
If an expandable event interface does not have any filters, it will show a “No items found” notification. Since each exception adds time, though negligible, to the scanning process, only add necessary exceptions to the system.
