SMTPReady
Buy US$99
Menu

Security review

What access does SMTPReady need?

SMTPReady accepts mail only from local senders you allow and gets Microsoft permission to send from one configured mailbox. It does not need tenant-wide mail access, and Swobu infrastructure is not in the message path.

MAIL PATHYOUR NETWORK
→ MICROSOFT
Swobu infrastructure is not in the mail-content path.
01 · Local senderPrinter / scanner / app

Explicit source CIDR and sender policy. Unknown sources are rejected before queueing.

02 · Customer Windows hostSMTPReady

Message is flushed, atomically stored and committed before SMTP 250.

03 · Customer tenantMicrosoft Graph

Customer-owned Entra identity and mailbox-scoped Exchange Application RBAC.

Where mail, credentials, and permissions go.

Review the data, permission, proof, and revocation for each boundary.

Mail content
Customer host → Microsoft only.SMTPReady-operated infrastructure is not in the content path.
Microsoft identity
Customer-owned certificate.Private key stays in the Windows certificate store; configuration stores metadata/thumbprints.
Mail authorization
Exchange Application RBAC scoped to the relay mailbox.For normal user mailboxes, large-message delivery is enabled by default and requires mailbox-scoped Application Mail.ReadWrite in addition to the send permission; shared mailboxes have this feature disabled automatically. Disable large messages before setup if you do not want the additional role. Messages above the fixed 3 MiB raw-MIME threshold are then rejected at SMTP submission. Provisioning rejects tenant-wide Entra mail app-role assignments.
Scope proof
Positive and negative test.Setup proves the relay mailbox is allowed and a distinct out-of-scope mailbox is denied.
Accepted message
Durably queued before 250.Accepted envelope recipients are sent using hidden Bcc presentation; the original visible To/Cc headers are not preserved. The queue is at-least-once: a crash after Microsoft accepts a message can create a duplicate rather than silent loss.
Operational logs
No bodies, attachments, SMTP passwords, OAuth tokens or private keys.Support bundles exclude the same secret/content classes.
Device access
Explicit local source rules.Domain/Private firewall profiles and sender policy constrain ingress.
License service
Separate from mail security.License validation does not grant Microsoft mail authority.

Prove unauthorized mailboxes are denied.

relay mailbox · expected setup result202 · allowed
unrelated mailbox · expected setup result403 · denied

These are illustrative expected outcomes, not a live tenant transcript. Setup must observe both results for your tenant. If the unrelated mailbox is ever accepted, treat it as a security failure: stop the service and repair the Microsoft scope before resuming delivery.

Stop delivery, revoke Microsoft access, or remove local state.

  1. Stop delivery nowStop the Windows service.
  2. Revoke Microsoft permissionRevoke the scoped Exchange/Entra assignment or credential.
  3. Delete local stateUse the explicit purge uninstall only when you intend irreversible data removal.

Ready to deploy?

Set up one sender safely