Skip to main content
DELIVERY

Sendman hands the mail to the backend you choose

Exchange Online or another SMTP transport service. The message passes through unchanged, with no queue and no copy, and switching the backend is a setting in the portal.

  • Exchange Online without SMTP AUTH
  • SMTP transport services such as Amazon SES, SendGrid, Mandrill, Brevo
  • Switching is a setting

From the device through Sendman to your backend

Sendman decides who may send what, and your backend delivers the message.

Your devices

Copiers, the ERP export, the alarm panel

Sendman

Allow list, sign-in, sender and recipient policies

Your backend

Exchange Online or your SMTP transport service

One relay, the backend you choose

  • Exchange Online without SMTP AUTH

    Sendman delivers into Exchange Online through an inbound connector in your tenant, the path Microsoft documents for relays, and does not use SMTP AUTH. The retirement of Basic Authentication for SMTP AUTH does not touch that path, and mail over a connector still gets in after you reject Direct Send.

  • Your SMTP transport service

    Enter the service's server, port and login in the portal. Sendman signs in to it with AUTH LOGIN, or with no login where the service accepts that. A service that only accepts another login mechanism cannot be the backend.

  • Encrypted to the backend wherever it supports it

    When the backend offers STARTTLS, Sendman uses it and validates the backend's certificate, whatever the device did on its own first hop.

  • Changing the backend touches no device

    The backend is one form in the portal. Change it, and the next connection goes the new way, while the devices keep their hostname and their login.

The message passes through unchanged

Sendman reads the envelope, not the message. The message is passed through as it arrives, headers included, with no mailbox, no queue, no spool and no copy kept.

  • SPF, DKIM and DMARC belong to the domain you send from and to the backend that delivers, so whatever you set up there keeps working.
  • A refusal from Exchange Online or the transport service reaches the device as the backend wrote it.
Sendman → Exchange OnlineDATA
DATA354 Start mail input; end with <CRLF>.<CRLF>[ message passed through unchanged, headers included ].250 2.6.0 Queued mail for delivery

Questions about delivery

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.

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

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

Request a preview and send the first message through your own backend.