Applications that only speak SMTP keep sending
The nightly ERP export, the monitoring server that predates everyone on the team and the alarm panel in the server room all send mail the same way: open SMTP, sign in, send. Sendman gives each of them a login of its own and a policy that says what it may do.
Every application gets a login of its own
Issue a vault credential for each application instead of sharing one mailbox password. When an application is retired, or its password ends up in a config file on a share, you delete or change that one credential, and every other sender keeps working.
AUTH LOGIN334 VXNlcm5hbWU6ZXJwLWV4cG9ydA==334 UGFzc3dvcmQ6••••••••235 Authentication successful. Let's send some emails!MAIL FROM:<invoices@contoso.com>250 2.1.0 Sender OK
What changes for an application, and what does not
Each application sends as its own address
A policy per application names the sender it may use and the recipients it may reach. The ERP sends invoices to customers, the monitoring server sends alerts to your own domain, and neither can send as the other.
No OAuth to build into an old application
Applications keep signing in with LOGIN or PLAIN, and Sendman reaches Exchange Online without SMTP AUTH. The move to OAuth that the retirement of Basic Authentication asks of SMTP AUTH clients does not reach them.
What an application should know before it sends
Messages can be up to 25 MB, or less if your backend sets a lower limit. PIPELINING and CHUNKING are not offered, and when Sendman refuses a sender or a recipient, the reply says which check stopped it.
Questions about applications
01Can 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.
02Which 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.
03How 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.