Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

anti-spam

Syntax

Hierarchy Level

Description

Configures the UTM antispam feature for logical systems. The antispam feature examines transmitted e-mail messages to identify e-mail spam. When the device detects a message deemed to be spam, it blocks the e-mail message or tags the e-mail message header or subject with a preprogrammed string. Antispam filtering uses both a third-party server-based Spam Block List (SBL), and optionally created local allowlists (benign) and blocklists (malicious) for filtering against e-mail messages.

You can also configure the default UTM configuration for antispam feature profile. If you do not configure any option in the antispam feature profile, the values configured in the default UTM configuration are applied. In the default UTM profile, the antispam type is configured as SBL instead of none. This configuration enables the SBL option. However, to use this feature, enable the SBL server using the [edit security utm default-configuration anti-spam sbl sbl-default-server] command.

Note:

A license check for the antispam configuration is performed at the time of commit and provides a warning if a valid license is not installed on the device. Once a valid license is installed on the device then the custom antispam profile or the default antispam profile is able to process the traffic. If a license is expired or is not installed, the antispam service does not process the traffic.

Options

anti-spam

Configures the UTM antispam feature for logical system.

address-blacklist

Enter an address blocklist custom object for local list spam filtering.

address-whitelist

Enter an address allowlist custom object for local list spam filtering.

sbl

Antispam filtering allows you to use both a third-party server-based SBL, and optionally created local allowlists and blocklists for filtering against e-mail messages.

The remaining statements are explained separately. See CLI Explorer.

Required Privilege Level

security—To view this statement in the configuration.

security-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 18.3R1.

Support for configuration in tenant systems introduced in Junos OS Release 19.2R1.