Skip to main content

SMTP RELAY FOR MICROSOFT 365

Say goodnight
to your last
Exchange Server.

Sendman is an SMTP relay for Microsoft 365 that lets printers, scanners and applications keep the logins they have, while you decide who may send as whom.

Request preview

Private preview now open.

Microsoft Partner of the Year, winner or finalist nine times; Security MSSP of the Year, finalist three times
Session 7b2e5d19 · 198.51.100.24 Abridged
[ 198.51.100.24 connected on port 465, TLS ]
220 ESMTP Service readyFrom the backend
EHLO mfp-3f-canon.contoso.local
250-SIZE 26214400
250 AUTH LOGIN PLAIN NTLM
AUTH LOGIN
[ user name and password ]
235 Authentication successful. Let's send some emails!
MAIL FROM:<scan@contoso.com>
250 2.1.0 Sender OKFrom the backend
RCPT TO:<accounting@contoso.com>
250 2.1.5 Recipient OKFrom the backend
RCPT TO:<anyone@gmail.com>
550 5.7.1 Recipient not authorized, your account is not permitted to send to this address
DATA
[ message sent ]
250 2.6.0 Queued mail for deliveryFrom the backend

Sendman is built for every printer, scanner and application that only speaks plain SMTP. It authenticates them against Microsoft Entra ID or its own credential vault, fences them in by IP address and sender policy, and hands the mail to Exchange Online or the transport service you already use. The last on-premises Exchange Server has nothing left to do.

THE PROBLEM

The server that only exists for the printers

In almost every organization there is one Exchange Server left. Nobody reads mail on it. It is still running because a scanner, a nightly ERP export and an alarm panel need to send, and the only thing any of them knows how to do is open a port and authenticate.

THE WORKAROUNDS

Four dead ends

Everyone has tried at least one of these. None holds up.

  1. 01

    Keep the Exchange Server running

    You are patching a mail server so a scanner can email a PDF. Every Exchange advisory is now your weekend.

    Dead end: The server stays
  2. 02

    Open an unauthenticated internal relay

    Anything that can reach the connector can send as anyone in your domain. No identity, no sender control, nothing to audit afterwards.

    Dead end: Control is gone
  3. 03

    Put one mailbox password on 200 devices

    It cannot be rotated without visiting every device, and a copy of it is on a sticker in the copy room.

    Dead end: Control is gone
  4. 04

    Point everything at a bulk sending service

    Delivery works. Nothing on the way checks who is sending as whom, or to whom, and the shared API key is as good as a domain-wide send permission.

    Dead end: Control is gone
  5. 05 · The way out

    All four are the same trade. You either keep a mail server alive for the sake of the devices, or you give up control over who is allowed to send as whom. Sendman is the option that refuses the trade.

    Way out: Server gone, control kept

Follow one session from connection to delivery

Sendman sits in the SMTP conversation itself, not beside it. There are five moments where it decides something. Pick one and watch which part of the exchange it governs.

Session 4f9c1a02 · 198.51.100.24
[ connection accepted from 198.51.100.24 on port 587 ]
[ 198.51.100.16 – 198.51.100.31 is on the allow list ]
220 ESMTP Service readyFrom the backend
EHLO mfp-3f-canon.contoso.local
[ backend greeting and extensions ]
250-SIZE 26214400
250 STARTTLS
STARTTLS
220 TLS go ahead
EHLO mfp-3f-canon.contoso.local
[ backend greeting and extensions ]
250-SIZE 26214400
250 AUTH LOGIN PLAIN NTLM
AUTH LOGIN
334 VXNlcm5hbWU6
c3ZjLXNjYW5AY29udG9zby5jb20=
334 UGFzc3dvcmQ6
[ password, base64 ]
235 Authentication successful. Let's send some emails!
MAIL FROM:<scan@contoso.com>
250 2.1.0 Sender OKFrom the backend
RCPT TO:<accounting@contoso.com>
250 2.1.5 Recipient OKFrom the backend
RCPT TO:<anyone@gmail.com>
550 5.7.1 Recipient not authorized, your account is not permitted to send to this address
DATA
354 Start mail input; end with <CRLF>.<CRLF>From the backend
250 2.6.0 Queued mail for deliveryFrom the backend
QUIT
221 2.0.0 Service closing transmission channelFrom the backend
TRY IT

Change who is knocking and watch three policies decide

This is the real evaluation order, running live: the allow list, then the policies that apply to this identity and this address, then the sender, then every recipient on its own. Change any of the four and watch what the relay answers.

Who is connecting
Connecting from
MAIL FROM
RCPT TO
Evaluation
connect220 ESMTP Service readyFrom the backend
auth235 Authentication successful. Let's send some emails!
policypriority 10 applies
mail from250 2.1.0 Sender OKFrom the backend
rcpt to250 2.1.5 Recipient OKFrom the backend
data250 2.6.0 Queued mail for deliveryFrom the backend
Why

Policy 10 is scoped to svc-scan@contoso.com from 198.51.100.24. scan@contoso.com matches its allowed senders and accounting@contoso.com matches its allowed receivers, so Sendman opens its own session to the backend and hands the message over unchanged.

The policies being evaluated

Global allow list: 198.51.100.16 – 198.51.100.31, 192.0.2.128 – 192.0.2.143

Priority 10Entra ID

svc-scan@contoso.com, from headquarters

senders: scan@contoso\.com
receivers: .*@contoso\.com

Priority 20Sendman vault

mfp-3f, from anywhere on the allow list

senders: .*@contoso\.com
receivers: .*@contoso\.com

Priority 30anonymous allowed

Any device at headquarters, no sign-in

senders: noreply@contoso\.com
receivers: .*@contoso\.com

Policies are selected by scope, then reduced to the lowest priority number that applies. Policies that tie on priority are tried side by side, and a recipient is accepted only when one of them allows both the sender and that recipient. A sender from one policy never combines with a recipient from another.

WHAT IT DOES

Sendman does Exchange's last job and lets you decide who sends as whom

What each part of the relay does for your devices, with a page of its own for the details.

AT A GLANCE

Specifications

The names and numbers an admin asks for before the first test mail.

Connectivity

Ports
465 with implicit TLS and 587 with STARTTLS over the internet, 25 only through LNC, the Sendman tunnel
Certificate
Renewed without a restart
Allow list
IPv4 address ranges, up to 16,384 addresses each

Authentication

Mechanisms
LOGIN, PLAIN, NTLM
Identity sources
Microsoft Entra ID for LOGIN and PLAIN (including hybrid DOMAIN\user logins), Sendman credential vault for LOGIN, PLAIN and NTLM
Vault encryption
AES-256-GCM
TLS before login
Required on every port except 25; a login without it gets 538 5.7.11

Policies

Scope
Username, IP range, or both
Priorities
Lowest number wins; on a tie, one policy must allow both the sender and the recipient
Sender and recipient rules
Regular expressions, enforced at MAIL FROM and every RCPT TO
Anonymous relay
Per policy, bound to an IP range

Delivery

Backends
Exchange Online (no SMTP AUTH), or SMTP transport services such as Amazon SES, SendGrid, Mandrill, Brevo
Message size
Up to 25 MB per message (your backend may allow less)
Handling
Passed through unchanged, no queue, no copy kept

Operations

Configuration
Platform Portal, live on the next connection
Roles
Viewer, admin
Audit trail
Who created every entry, who last changed each policy
Event log
Authentication failures and policy violations, searchable, with the rule that refused each one
Telemetry
Authentications, deliveries and session times, searchable in the portal, ready to alert on
Certification
glueckkanja is ISO 27001 certified
WHAT MICROSOFT CHANGES

Microsoft is closing three paths your scanners use today

What each change means for a device that sends to Microsoft 365, and what Sendman does about it. Each page links Microsoft's dates and sources.

Three steps to switch off the last Exchange Server

Sendman takes over the one job that kept the server alive, without touching the devices that depend on it.
  • Point Sendman at your backend
    Point Sendman at your backend
    Choose Exchange Online or the SMTP transport service you already send through, and enter what it needs. One form in the portal, and no redeployment when it changes.
  • Let the devices in, and say what they may do
    Let the devices in, and say what they may do
    Add the ranges they connect from, issue vault credentials to the devices that should not carry a directory identity, then write the policies for who may send as what, and to whom.
  • Repoint DNS, retire the server
    Repoint DNS, retire the server
    Point the hostname your devices send to at Sendman instead of the Exchange Server. For a device that sends with TLS on port 465 or 587, that is all it takes – the device itself is not touched. Devices that only speak plain SMTP on port 25 send through LNC, the Sendman tunnel, and the Exchange Server has nothing left to do.
GOOD TO KNOW

The questions that come up first

What admins ask before the first test mail goes through.

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.

02Do 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.

03What 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.

04Which 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.

05What 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.

06Can 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.

07How 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.

Also from glueckkanja

  • Network access by certificate without a RADIUS server to run

    Often a RADIUS server still guards the Wi-Fi next to the last Exchange Server, and RADIUSaaS lets it go the same way.

    Go to RADIUSaaS
  • A certificate authority that blocks the device you disable

    SCEPman issues and revokes certificates for devices managed in Microsoft Intune and Jamf, in your own Azure tenant or as a managed service.

    Go to SCEPman

Request a Sendman preview, or talk to the team.

The Sendman team
The Sendman team