\n

ShazaMail

ShazaMail Security Architecture

Security is layered across SMTP acceptance, durable processing, malware scanning, HTML sanitization, session authorization, and database access controls.

Product documentation last reviewed: 2026-09-28

Receive-only SMTP reduces the abuse surface

ShazaMail is designed to receive mail for validated active inboxes and does not provide a public outbound SMTP relay. The Haraka gateway validates recipients before accepting a message. This matters because a disposable-mail service that also relays arbitrary outbound mail would create a substantially larger spam and reputation risk. Receive-only operation is a deliberate architectural boundary, not just a user-interface restriction.

Accepted messages are durably queued before processing

After SMTP DATA is accepted, the gateway writes the message into a durable local spool before returning the queue result. A separate worker then handles malware scanning, MIME parsing, Safe View processing, and persistence. Decoupling SMTP acceptance from heavier processing helps prevent transient downstream delays from turning every inbound connection into a long-running synchronous workflow.

Safe View reduces browser exposure to untrusted email HTML

The mail worker sanitizes incoming HTML and applies a privacy shield before the content is rendered. Scripts, iframes, forms, embedded objects, event handlers, and unsafe URI schemes are removed or neutralized. Tracking beacons are stripped and ordinary remote images are blocked behind placeholders. These controls reduce exposure, but users should still treat unexpected links, attachments, and credential requests as potentially unsafe.

Authorization continues after mail delivery

Temporary inboxes are protected by high-entropy guest-session tokens stored as HttpOnly cookies, while account-owned data is protected through authenticated access and database Row Level Security. Developer access uses scoped API keys that are hashed at rest and verified before each request. Security boundaries are therefore applied at SMTP ingress, message processing, API access, browser sessions, and database reads rather than relying on one perimeter control.

Common questions

Is ShazaMail an open mail relay?

No. The production mail design is receive-only and validates recipients rather than relaying arbitrary outbound mail.

Does Safe View make every email safe?

No security control can guarantee that. Safe View reduces specific browser and tracking risks and surfaces technical signals, but users still need to evaluate suspicious content.

How are anonymous inboxes protected?

Guest inbox access uses an unguessable session token delivered through an HttpOnly cookie, while database policies prevent arbitrary anonymous reads.