Outbound Mail Protection

INKY's Outbound Mail Protection (OMP) detects sensitive information in outgoing email and applies policy-driven actions before messages leave your organization.

Written By Matt Sywulak

Last updated 4 months ago

How It Works

When users send email, INKY intercepts and analyzes it for sensitive content like credit cards, Social Security numbers, medical records, or custom patterns. If detected, OMP triggers workflow actions based on your rules.

Flow: User sends email → INKY analyzes → Rule matches → Action triggers → Approval required or encryption applied → Message delivers

Key Actions

  • Self-Approval - Sender confirms they meant to send sensitive data

  • Other Approval - Manager or designated approver reviews before delivery

  • Encrypt - Automatically encrypts message and sends via secure portal

What OMP Detects

  • Financial: Credit cards, bank accounts, SWIFT codes, routing numbers

  • Identity: Driver's licenses, Social Security numbers, passport numbers

  • Medical: ICD-10 codes, health information

  • IT: IP addresses, certificates, private keys

  • Cryptocurrency: Bitcoin and other wallet addresses

  • Custom patterns: Define your own detection rules

Approver Relationships

OMP uses flexible sender-to-approver mapping:

  • Specific email addresses

  • M365 groups

  • Entire domains

  • Registered domains (includes subdomains)

  • Default fallback approvers

If no approver matches, the sender becomes their own approver.

User Experience

For Senders: Email Assistant notification explains why approval is needed, who's reviewing it, and current status.

For Approvers: Email Assistant provides approve/deny links directly in the notification. Full message details available in Workflow Portal.