The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
If you believe a message was not classified correctly (false positive or false negative), you can reclassify the message. The message will be queued for review by Cisco Talos. Talos may use the feedback to influence future classifications.
Reclassifying only affects the verdict on the selected message(s). It does not indicate any change to future messages from the selected sender or based on the message content. The message will be queued for review by Cisco Talos. Talos may use the feedback to influence future classifications.
If you have a Secure Email Gateway (SEG) in place, you should indicate this on the Policy page. This information will help decrease false positives.
For false positive messages, consider adding a Verdict Override message rule.
If you continue to have this issue, contact Support.
Duplicate entries are a result of Microsoft creating multiple journals for a single email. This can happen for several reasons. For example, mail rules set by the Exchange admin, or mail sent to groups with non-domain users.
Undisclosed recipient indicates the email had no listed recipients. For example, when a BCC (blind carbon copy) is sent to a recipient. Secure Email Threat Defense does not track BCC recipients, but detection and remediation are not impacted.