— Exhibit –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;
}
}
— Exhibit –Click the Exhibit button.
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.
Referring to the exhibit, what is causing this problem?
A.
The wildcard character * cannot be used for the e-mail pattern match.
B.
The protocol-command smtp value sender: needs to be added under custom-objects.
C.
url-pattern is not supported for antispam.
D.
The pattern needs to be preceded by an @ symbol.
Explanation:
Should be B
Because Wildcard, URL pattern are supported.
It should be A
because in the way that is written
You can configure entries on either list by IP address, e-mail address, or domain name. You can use asterisk * orquestion mark ? wildcards on the local lists. You must precede all wildcard URLs with http://. You can only use theasterisk * wildcard character if it is at the beginning of the URL and is followed by a period. You can only use thequestion mark ? wildcard character at the end of the URL. The following wildcard syntax is supported: http://*.juniper.net. The following wildcard syntax is not supported: http://*.
It’s A http://www.juniper.net/techpubs/en_US/nsm2012.2/topics/task/configuration/threat-mitigation-local-list-antispam-configuring-nsm.html