Table of Contents

Enum SensitiveContentScannerKind

Namespace
MailFathom.Application.SensitiveContent
Assembly
MailFathom.Application.dll

Names one of the two scanners a deployment can switch on independently.

public enum SensitiveContentScannerKind

Fields

Pii = 1

Personal data beyond the fixed-format identifiers, which needs a language model to recognize.

Secrets = 0

Credentials, tokens, keys, and other machine secrets that identify themselves by their own format.

Remarks

The two are separated by how precise they are rather than by preference. A provider-prefixed token, a PEM block, or a connection string identifies itself, so Secrets is close to exact. Personal data in a mailbox is the opposite: every message carries a name, an address, and a signature block, so Pii applied the same way would redact most of a corpus. An operator handling regulated correspondence wants both; the ordinary one wants secrets alone and would switch a single combined switch off entirely rather than accept the second.

The member names are the configuration keys under the SensitiveContent section, so a validation message and an operator's file spell a scanner the same way without a translation table between them.