Close Direct Send and keep the scanners sending
Direct Send lets anyone on the internet drop mail into your tenant as one of your users, and attackers use it for phishing. Exchange Online can reject it with one setting. The scanners that quietly relied on it move to Sendman first.
MAIL FROM:<ceo@contoso.com>250 2.1.0 Sender OKRCPT TO:<accounting@contoso.com>550 5.7.68 TenantInboundAttribution; Direct Send not allowed for this organization from unauthorized sources
Mail over a connector still gets in
Direct Send is mail sent anonymously to your tenant's MX endpoint with one of your own domains as the sender. The only thing telling your scanner apart from anyone else on the internet is the address it claims to have.
RejectDirectSend in the organization config turns that mail away. Mail that arrives over an inbound connector you set up, matched by IP address or certificate, still gets in, and that is the path Sendman delivers on.
Sendman adds a sign-in and a sender rule
Microsoft's answer for legitimate senders is a partner connector that trusts your office's public IP address, and anything behind that address can then send as anyone in your domain. With Sendman in front, the scanner signs in or sends from an address range you allow, and it may send as scan@contoso.com but not as your CEO.
MAIL FROM:<ceo@contoso.com>550 5.7.60 Sender address rejected: not authorized. No cookies no email.MAIL FROM:<scan@contoso.com>250 2.1.0 Sender OK
Move the scanners, then switch it on
- Find the sendersFind the sendersRun the message trace for mail received without a connector, and write down every copier and service it shows. Our post has the commands.
- Move them to SendmanMove them to SendmanGive each one a sign-in or an allowed address range, a policy for its sender, and Sendman's hostname.
- Switch on the rejectionSwitch on the rejectionSet RejectDirectSend and watch for 5.7.68 bounces for a few days.
Questions about Direct Send
01Does 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.
02What 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.
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.