user@host show configuration security utm custom-objects { url-pattern { block-juniper { value *.spammer.com; } } custom-url-category { blacklist { value block-juniper; } } } feature-profile { anti-spam { address-blacklist block-juniper; sbl { profile myprofile { no-sbl-default-server; spam-action block; } } } } utm-policy wildcard-policy { anti-spam { smtp-profile myprofile; } } You added a blacklist to your antispam policy to block any e-mails from the spammer.com domain. However, your users are complaining that they are still receiving spam e-mails from that domain. You run the utm test-string test and confirm that the blacklist is not working. What is causing this problem?

Question

user@host> show configuration security utm custom-objects { url-pattern { block-juniper { value *.spammer.com; } } custom-url-category { blacklist { value block-juniper; } } } feature-profile { anti-spam { address-blacklist block-juniper; sbl { profile myprofile { no-sbl-default-server; spam-action block; } } } } utm-policy wildcard-policy { anti-spam { smtp-profile myprofile; } } You added a blacklist to your antispam policy to block any e-mails from the spammer.com domain. However, your users are complaining that they are still receiving spam e-mails from that domain. You run the utm test-string test and confirm that the blacklist is not working. What is causing this problem?

Accepted Answer

A. The wildcard character * cannot be used for the e-mail pattern match.

Answer

B. The protocol-command smtp value sender: needs to be added under custom-objects.

Answer

C. url-pattern is not supported for antispam.

Answer

D. The pattern needs to be preceded by an @ symbol.

user@host> show configuration security utm custom-objects { url-pattern { block-juniper { value *.spammer.com; } } custom-url-category { blacklist { value block-juniper; } } } feature-profile {…

Question

Options

How the community answered

Community Discussion