What it means
Domino tried to send through Microsoft 365, which refused the message because the connection was not authenticated.
Common causes
- The relay host is set to the authenticated submission endpoint, which needs a sign-in
- No Microsoft 365 connector that recognises the Domino server's IP address or certificate
- The Domino server's public IP address changed
Quick fixes
- In Microsoft 365, create or fix a connector that accepts mail from the Domino server's public IP address or TLS certificate
- Point the Domino relay host at the tenant's MX endpoint rather than the authenticated submission host
- Run
tell router update config after changes, then retry the queued mail
Disclaimer
The errors, causes and fixes on this site are carefully researched, drawing on HCL documentation and 28 years of hands-on Domino and Notes experience. Every environment is different, though, and a solution that works in one may not be right for yours. Exact wording can also vary between Domino and Notes versions.
This information is general guidance only and is provided without warranty of any kind. Always back up your data and test changes on a non-production system first. To the extent permitted by law, Bruinsma Services Pty Ltd accepts no responsibility or liability for any loss, damage, downtime or other consequence arising from use of this information. For advice specific to your environment, please contact me.