Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?




Hierarchy Level


Configure UTM antispam features. 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.

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.


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

In the default UTM profile, the antispam type is configured as SBL instead of none. This configuration enables SBL. However, to use this feature, you must enable the SBL server using the [edit security utm default-configuration anti-spam sbl sbl-default-server] command.



Configure antispam feature.


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


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


Antispam filtering allows you to use both a third-party server-based spam block list (SBL) and to optionally create your own local allowlists and blocklists for filtering against e-mail messages.


Defines tracing operations for UTM antispam features.


Antispam type.

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 9.5.

The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.