Defining Email Policies > Antispam tab
|
1.
|
From the first Spam scoring more than drop-down list, select a spam threshold.
|
2.
|
From the second Spam scoring more than drop-down list, select an action for that threshold.
|
Message subjects are tagged with a prefix that you've assigned (in the Tag subject prefix box under Existing Rules).
|
|
3.
|
Click Add Rule>> to create a rule based on these parameters.
|
1.
|
|
Take no action. No action is taken on the commercial bulk email detected.
|
|
Tag the message subject. The subject of detected commercial bulk email messages are tagged with "COMMERCIAL:" or a custom tag that you enter.
|
|
Quarantine the message. Commercial bulk email messages are kept in quarantine for up to 30 days. Note that no notifications are sent for this disposition.
|
|
Normal detects email that comes from known commercial bulk email sources.
|
|
High detects email that comes from known commercial bulk email sources or email that contains commercial content.
|
4.
|
Click Submit when you are finished.
|
Notes
If Forcepoint Technical Support has enabled a custom antispam rule for your account, this may override any addresses in allowlist you have configured.
|
|
Apply allowlist matching even if the message has a spoofed email addresses. If the service detects a message is spoofed, allowlist is not applied by default. However, you may wish to allow some messages that are legitimately spoofed, for example a message from an email distribution list that appears to come from a specific person. Select this option if you want to allow spoofed addresses through even if the address appears in your allowlist.
|
|
Do not apply allowlist matching on From: headers. An email message has two addresses associated with it: the envelope sender, and the From: header. The envelope sender is used by mail servers to check where the message originates and where to respond (for example, if there is an error or the message bounces); the From: header is what the message recipient sees. The envelope sender and the From: header often match, but not always. There are a number of legitimate reasons why an envelope sender might not match the From: header, for example if the message comes from a mailing list, or from an organization that has implemented a specific address for bounced messages.
|
The Forward messages option is a limited-availability feature, and may not be available in your account.
|
Defining Email Policies > Antispam tab
|