300-720 · Question #97
An engineer is tasked with reviewing mail logs to confirm that messages sent from domain abc.com are passing SPF verification and being accepted by the Cisco ESA. The engineer notices that SPF…
The correct answer is B. SPF verification is disabled on the Mail Flow Policy. On Cisco ESA, SPF verification is enabled or disabled at the Mail Flow Policy level (under the listener's Host Access Table). If SPF verification is disabled in the Mail Flow Policy, the appliance will not perform any SPF checks and will not log SPF-related verdicts, exactly…
Question
An engineer is tasked with reviewing mail logs to confirm that messages sent from domain abc.com are passing SPF verification and being accepted by the Cisco ESA. The engineer notices that SPF verification is not being performed and that SPF is not being referenced in the logs for messages sent from domain abc.com. Why is the verification not working properly?
Options
- ASPF verification is disabled in the Recipient Access Table.
- BSPF verification is disabled on the Mail Flow Policy.
- CThe SPF conformance level is set to SIDF compatible on the Mail Flow Policy.
- DAn SPF verification Content Filter has not been created.
How the community answered
(14 responses)- A7% (1)
- B71% (10)
- D21% (3)
Explanation
On Cisco ESA, SPF verification is enabled or disabled at the Mail Flow Policy level (under the listener's Host Access Table). If SPF verification is disabled in the Mail Flow Policy, the appliance will not perform any SPF checks and will not log SPF-related verdicts, exactly matching the symptom described. The Recipient Access Table (A) controls recipient acceptance, not authentication checks. SIDF-compatible mode (C) changes the conformance level but does not disable SPF entirely - it would still appear in logs. An SPF content filter condition (D) requires SPF verification to already be enabled at the policy level before it can act on verdicts.
Topics
Community Discussion
No community discussion yet for this question.