FileDNA Relay
CADR that reaches into the inbox, and puts the clean file back.
FileDNA Relay connects to Gmail, Microsoft Graph, and similar mail and collaboration platforms, pulls out each attachment, runs it through FileDNA CADR on whichever engine you’re already running — Desktop, Server, or Cloud — and replaces the original with a clean, reconstructed file. No forwarding rule, no separate scanning inbox, no manual download.
How It Works
Relay runs as a lightweight connector between the mailbox and whichever FileDNA engine you point it at.
1
Connect
Relay authenticates to Gmail, Microsoft Graph, or a similar mail API using the platform’s own OAuth flow — no credentials stored outside what the provider requires.
2
Pull the attachment
When a new message with an attachment arrives, Relay pulls the file out of the mailbox through the provider’s API, without altering the original message.
3
Run CADR
The attachment is handed to whichever FileDNA engine you’ve configured — Desktop, Server, or Cloud — and processed the same way any other file is: disassembled, analyzed, and reconstructed.
4
Put it back
The clean, reconstructed file replaces the original attachment in place, so the recipient opens the same message with a verified-safe version of what was sent.
Key Capabilities
Built to sit between mail platforms and whichever FileDNA engine you’re already running.
Works with the engine you already have
Relay doesn’t do its own analysis — it hands the file to FileDNA Desktop, Server, or Cloud, whichever is already part of your deployment.
Native to the platform’s own API
Built against Gmail and Microsoft Graph’s own attachment and webhook APIs, not a bolted-on mail gateway or MX record change.
In place, not in a separate queue
The clean file replaces the original attachment directly — recipients don’t get a second email, a portal link, or a quarantine notice to work around.
Same verdict, same audit trail
Every attachment gets the same structured verdict and audit log as a file processed anywhere else in the FileDNA line.
Who It’s For
Security teams who want file-content protection on email without standing up a separate mail gateway or changing MX records.
Google Workspace and Microsoft 365 teams that want CADR applied natively through the platform’s own attachment API.
Organizations already running FileDNA Desktop, Server, or Cloud who want to extend the same engine to inbound email attachments.
Relay is a connector, not an engine of its own — it depends on FileDNA Desktop, Server, or Cloud to actually process a file. Pick whichever of the three you’re already running, and Relay routes attachments to it.