If the marketing message detection feature mislabels legitimate mail as marketing, which action corrects this error?

Question

Options

• ATurn off Marketing Message Detection.
• BWhitelistthe domains that send the mislabeled messages.
• CSend samples of mislabeled legitimate mail to [email protected].
• DSend samples of mislabeled legitimate mail to [email protected].

• B
  5% (1)
• C
  91% (20)
• D
  5% (1)

Explanation

Sending mislabeled legitimate mail to [email protected] trains Cisco IronPort's filtering engine by submitting confirmed false positives - "ham" is the industry term for legitimate (non-spam) email, so this address is specifically designed to receive misclassified good mail and improve detection accuracy.

Why the distractors are wrong:

• A is too blunt - disabling the feature entirely sacrifices all marketing detection just to avoid occasional errors, rather than refining the system.
• B (whitelisting domains) bypasses detection for those senders permanently, which is a workaround, not a fix - it also creates a security gap if those domains are ever compromised.
• D ([email protected]) is the wrong submission address - this endpoint is for reporting missed marketing/spam that was not caught (false negatives), the opposite problem.

Memory tip: Think "ham vs. spam" - ham@ = "this is ham (legitimate), not spam, please learn from it." If you got spam that slipped through, you'd report to the spam/adds address; if good mail got wrongly flagged, you send it to ham@.

No community discussion yet for this question.