VStream Antispam includes a flexible mechanism that allows the user to define exactly which emails should be scanned for spam and which should be considered safe, by specifying the protocol, and the source and destination IP addresses.
VStream Antispam processes policy rules in the order they appear in the Antispam Policy table, so that rule 1 is applied before rule 2, and so on. This enables you to define exceptions to rules, by placing the exceptions higher up in the Rules table.
For example, if you want to scan all outgoing SMTP traffic, except traffic from a specific IP address, you can create a rule scanning all outgoing SMTP traffic and move the rule down in the Antispam Policy table. Then create a rule passing SMTP traffic from the desired IP address and move this rule to a higher location in the Antispam Policy table than the first rule. In the figure below, the general rule is rule number 2, and the exception is rule number 1.

The UTM-1 appliance will process rule 1 first, passing outgoing SMTP traffic from the specified IP address, and only then it will process rule 2, scanning all outgoing SMTP traffic.
The following rule types exist:
VStream Antispam Rule Types
Rule |
Description |
|---|---|
Pass |
This rule type enables you to specify that VStream Antispam should allow all emails matching the rule, without scanning the emails. |
Scan |
This rule type enables you to specify that VStream Antispam should scan all emails matching the rule. |
Reject |
This rule type enables you to specify that VStream Antispam should reject all emails matching the rule, without scanning the emails. |