What Sendman keeps, and who may change it
Sendman keeps no mailbox and no copy of a message. It keeps your configuration, encrypted wherever it holds a secret, and the addresses, user names and outcomes of each session go to the operator's logs. This page is the short version for a security review.
What Sendman stores, and how
Everything Sendman writes down, and what protects it.
| What | Where | Protection |
|---|---|---|
| Allow list, policies, backend settings | Storage isolated to your tenant | Secrets encrypted before they are written |
| Vault passwords | The credential vault | Encrypted with AES-256-GCM, compared in constant time, never shown again |
| Backend password and certificate | The backend settings | Encrypted with AES-256-GCM, write-only in the portal |
| Session details | glueckkanja's operation logs and metrics | Addresses, user names and outcomes of each session, never the message |
| Messages | Nowhere | Passed through unchanged, no queue, no copy |
What Sendman does in your Entra ID
No app registration, no consent
For an Entra ID account, Sendman validates the user name and password against Microsoft Entra ID, with no app registration, no consent and nothing to change in your tenant.
Multi-factor authentication and Conditional Access
Multi-factor authentication and Conditional Access do not stand in the way, even with strict policies, and the device never sees a prompt.
Vault credentials stay out of your directory
A device with a Sendman credential never touches your directory at all.
Viewers see every rule, admins change them
Configured in the Platform Portal
Credentials, policies, the allow list and the backend are configured in the Platform Portal.
Two roles, checked on every request
Viewers see every rule and change none; admins change configuration. The service checks the role on every request, not only on the screen.
Every entry says who made it
Every allow-list entry, policy and credential records who created it, and every policy records who last changed it.
What a session leaves behind
Event log
Every authentication failure and policy violation, filterable by user, address, sender and recipient, with the rule that rejected it named in the entry.
Metrics
Authentications, deliveries and session times, searchable in the portal and ready to alert on.
- On the roadmap
A capture window for one device
Sniff Mode will show what a device presents: the source address, the user name it offers, the sender it claims.
glueckkanja runs the relay for you
A configuration outage delays mail, it does not lose it
If Sendman cannot read its configuration, it refuses new connections with a temporary
421reply, and a device that behaves holds the message and tries again. On port 465, where TLS comes first, the connection closes without a reply.One relay per customer
Sendman runs on glueckkanja's SaaS platform, one relay per customer. Updates, restarts and certificate renewals are ours, and glueckkanja is ISO 27001 certified.
Questions about data and security
01Does Sendman store our email?
No. It proxies the SMTP session and forwards it as it arrives. There is no mailbox, no queue, no spool and no archive, and the message itself is passed through unchanged, headers included. Sendman keeps your configuration; the addresses, user names and outcomes of each session go to the operator's logs, never the message.
02Where does our configuration live, and who can see it?
In storage isolated to your tenant. Credentials are encrypted before they are written. Access to the portal comes from your platform tenant, viewers see every rule and change none, admins change configuration, and every allow-list entry, policy and credential records who created it.
03How do we find out what a device is actually sending?
Every authentication failure and policy violation lands in the searchable event log, with the rule that rejected it named in the entry, and the reply the device receives tells you which gate refused it. Sniff Mode, a capture window that shows exactly what a device presents, its source address, the username it offers and the sender it claims, is on the roadmap.
04What happens if Sendman cannot reach its configuration?
The mail is delayed, not lost. New connections get a temporary “service not available” reply that tells a well-behaved sender to hold the message and retry; on port 465, where TLS comes first, the connection closes without a reply.