A FortiMail administrator is investigating a sudden increase in DSNs being delivered to their protected domain. After searching the logs, the administrator identifies that the DSNs were not…

Question

Options

• AFortiGuard IP Reputation
• BSpoofed header detection
• CSpam outbreak protection
• DBounce address tag validation

• A
  4% (1)
• B
  12% (3)
• C
  27% (7)
• D
  58% (15)

Explanation

Bounce Address Tag Validation (BATV) is the correct answer because it directly addresses the "backscatter" scenario described. BATV works by cryptographically tagging the Return-Path (bounce address) of every legitimate outgoing email. When a DSN arrives, FortiMail checks for this tag - if no valid tag exists, the DSN is rejected because no matching outbound email was ever sent, indicating spammers forged the organization's address as the sender.

Why the distractors are wrong:

• A (FortiGuard IP Reputation) blocks email from IPs with bad reputations, but DSNs often originate from legitimate mail servers, so IP reputation checks won't filter them.
• B (Spoofed header detection) targets incoming emails that forge the "From" header to impersonate trusted domains - it doesn't validate whether a bounce corresponds to actual outbound mail.
• C (Spam outbreak protection) uses cloud intelligence to detect new spam campaigns by message fingerprinting - it combats spam delivery, not illegitimate bounce messages.

Memory tip: Think of BATV like a coat-check ticket - your organization "stamps" every email it sends with a secret token. When a bounce comes back, you only accept it if it has your stamp. No stamp = not your coat = reject the DSN.

No community discussion yet for this question.