Skip to main content
FAQ

Questions about Sendman

What admins and security reviewers ask before the first test mail, grouped by topic.

Connections and sign-in

01Do we have to register anything in our Entra tenant?

No. Sendman validates device credentials against Microsoft Entra ID with no app registration, no consent and nothing to change in your tenant. Hybrid logins such as CONTOSO\svc-scan work as they are.

02What about multi-factor authentication on those accounts?

Neither gets in the way. A vault credential never touches your directory, so there is nothing to prompt for. Entra ID accounts work as well: multi-factor authentication and Conditional Access do not stand in the way, even with strict policies, and the device never sees a prompt. What an account may send as, and to whom, is not a mailbox permission in Exchange Online but a Sendman policy: sender and recipient rules decide, for vault credentials and Entra ID accounts alike.

03Which login mechanisms does Sendman accept?

LOGIN, PLAIN and NTLM. LOGIN and PLAIN work with Entra ID accounts and with vault credentials, NTLM with vault credentials only.

04Can a device keep the user name it has today?

Yes. A vault credential can carry the name the device already uses, CONTOSO\svc-scan included, and an Entra ID account signs in with its user principal name or, if it is synced from Active Directory, with its domain login.

05Can a printer keep its NTLM login?

Yes, with a vault credential. NTLM works against the Sendman credential vault, not against Entra ID, so the printer gets a vault credential with the user name it already sends, and the password you set there.

06Can every application get its own login?

Yes. Issue one vault credential per application and write a policy for it. Retiring an application, or changing a password that leaked, then touches that one sender only.

07Do devices need OAuth to send through Sendman?

No. Devices sign in to Sendman with LOGIN, PLAIN or NTLM, and Sendman reaches Exchange Online without SMTP AUTH, so there is no OAuth for the device to learn.

08Which devices need LNC?

Only the ones that cannot do TLS. A device that speaks implicit TLS on port 465 or STARTTLS on port 587 reaches Sendman over the internet, and repointing its hostname in DNS is all it takes. A device that only speaks plain SMTP on port 25 needs LNC, the Sendman tunnel: that port is not open to the internet, and every other port refuses a login before TLS. The SMTP settings of each device tell you which side of the line it is on.

09What if a device cannot do TLS at all?

It sends through LNC, the Sendman tunnel, on port 25. That port is not open to the internet, and it is the only one where a device may log in without TLS; identity, IP and policy are enforced there in exactly the same way. From Sendman onwards, the session is encrypted wherever the backend supports it.

Policies

01How do we stop a device from sending as the CEO?

With a sender rule. Every policy names the sender addresses it allows, and a device that claims any other address is refused at MAIL FROM, before the message is sent.

02What happens to a recipient that no policy allows?

Sendman refuses that recipient and carries on. Every recipient is judged on its own, so the message still reaches the recipients that were accepted.

03Can a device send without signing in?

Yes, if a policy allows it. Such a policy needs an address range of at most 16,384 addresses, and its sender and recipient rules apply as they do to everyone else.

04How fast does a policy change take effect?

From the next connection. Sendman reads its configuration fresh for every connection, so there is no restart and no cache to wait out.

Delivery and Exchange Online

01Can we keep Exchange Online as the backend?

Yes. Exchange Online can stay the delivery path, and Sendman adds the sign-in and policy layer your devices need in front of it. The backend can be changed later without touching a single device.

02Is Sendman affected by the retirement of Basic Authentication for SMTP AUTH?

No. Sendman delivers into Exchange Online through an inbound connector, without SMTP AUTH. Your devices keep signing in to Sendman with LOGIN, PLAIN or NTLM.

03Does Sendman keep working once we reject Direct Send?

Yes. Sendman delivers through an inbound connector of your tenant, and mail over a connector still gets in after you switch on RejectDirectSend.

04What happens to SPF, DKIM and DMARC?

They belong to the domain you send from and are handled by the backend that actually delivers, Exchange Online or your SMTP transport service. Sendman does not rewrite your envelope or your headers, so whatever you have set up for that backend keeps working exactly as it does today.

05Does Sendman queue mail when the backend refuses it?

No. There is no queue: Sendman passes each message straight to your backend and hands the backend's reply back to the device. A device that gets a temporary refusal holds the message and tries again.

06How large can a message be?

Up to 25 MB. Sendman tells the device so in its EHLO reply, and when your backend accepts less, its limit wins.

Retiring the last Exchange Server

01Do we still need an Exchange Server for recipient management?

No. Recipients in a hybrid setup are managed with the Exchange Management Tools of Exchange 2019 CU12 and later, and Microsoft advises shutting the last server down. Sendman takes over the other job, the relay.

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.