Using message processing rules

A message processing rule (hereinafter also referred to as a "rule") is a set of parameters and actions applied by the program to messages that meet specific criteria. For a rule to be applied to a message, the addresses of the sender and recipient must be specified in the rule settings.

By default, the program contains the following preset message processing rules:

• AllowList processes messages from the global allowlist.
• DenyList processes messages from the global denylist.
• Default processes messages according to the settings predefined by Kaspersky.

  The AllowList and DenyList rules are disabled by default.

When Kaspersky Secure Mail Gateway processes an email message, it applies rules in accordance with their priority, that is, in the order of occurrence in the rule table, top to bottom. If the combination of sender-recipient addresses does not match, the program moves on to the next rule. As soon as it finds the sender-recipient pair of addresses in any rule, the program applies the processing settings configured in that rule to the message, and the search for a match is finished.

If none of the rules contains the "sender - recipient" pair of addresses, the message is processed in accordance with the preset settings of the Default rule.

If the message has a DKIM signature, it can be damaged by processing rules that modify the subject or body of the message, delete attachments, treat detected malicious objects, or add email disclaimers to the body of the message.

For each rule, you can configure your own email message processing criteria and select an action that is applied to the messages. If multiple program modules are triggered and they have different response actions configured, the most strict action will be performed ( Delete message → Reject → Delete attachment → Skip ).

The Reject action is recommended only if Kaspersky Secure Mail Gateway is directly integrated into the mail infrastructure, that is, if it functions as an edge gateway. If the program is integrated behind a third-party edge gateway, that is, it functions as an interior gateway, applying the Reject action will result in the edge gateway generating non-delivery notifications (DSN, Delivery status notification). Sending such notifications to non-existent email addresses may degrade the reputation of the edge gateway on the Internet.