Error messages
Microsoft 365 SMTP errors from copiers, scanners and apps
When a device or app can't send through smtp.office365.com, the reply it shows says why. Find yours below: what it means, and where the fix is.
| Message | What it means |
|---|---|
535 5.7.139 Authentication unsuccessful, SmtpClientAuthentication is disabled for the Tenant (or Mailbox) | SMTP AUTH is off for the organization or for that mailbox. Fix 535 5.7.139 |
535 5.7.139 Authentication unsuccessful, basic authentication is disabled | Signing in with a password is blocked for SMTP. Fix: password sign-in blocked |
535 5.7.3 Authentication unsuccessful | Microsoft 365 refused the sign-in. Fix 535 5.7.3 |
5.7.57 Client not authenticated to send mail, or Client was not authenticated to send anonymous mail during MAIL FROM | The device reached smtp.office365.com without a sign-in Microsoft accepted, or without one at all. Fix 5.7.57 |
5.7.60 SMTP; Client does not have permissions to send as this sender | The From address isn't the mailbox the device signs in as. Fix: Send As |
5.7.64 TenantAttribution; Relay Access Denied | A connector no longer recognises the device: its IP address or certificate changed. Fix: update the connector |
Authentication with the destination has failed. (Ricoh) | The mail server (or scan folder) refused the Ricoh's user name or password. Ricoh's fix |
Two more from Microsoft's troubleshooting article
535 5.7.139 Authentication unsuccessful, federated STS service was unreachable. and 535 5.7.139 Authentication unsuccessful, the federated STS URL does not support HTTPS. come from organizations that sign in through their own federation servers. What they mean.
Source: Microsoft Learn, Fix issues with printers, scanners, and LOB apps that send email using Microsoft 365 (read October 30, 2026)
Every page
- 535 5.7.139: SMTP AUTH is switched off for the organization or the mailbox, or basic authentication is blocked.
- 535 5.7.3: Microsoft 365 refused the sign-in. Microsoft lists four things to check.
- 530 5.7.57: The device reached smtp.office365.com without a sign-in that Microsoft accepted.
- Ricoh: destination failed: A Ricoh's sign-in to the mail server (or a scan folder) was refused.
- Scan to email not working: A step-by-step check for copiers and scanners that send through Microsoft 365.
- smtp.office365.com not working: Every cause Microsoft documents, from SMTP AUTH settings to TLS and ports.
- Enable SMTP AUTH: Microsoft's steps in the admin center and in PowerShell, and when it won't help.
- Scan to email with Microsoft 365 after December 2026: every route Microsoft offers, step by step.
If the device can't sign in with OAuth
CopierBridge gives the device its own username and password on port 587 or 465 and sends each message from your own Microsoft 365 mailbox, signed in with Microsoft's OAuth and permission to send only. The one Microsoft 365 setting it needs is Authenticated SMTP on that mailbox. $9 a device a month, the first device free for 14 days. Start free or see pricing.
Keep copiers and apps sending after December 2026
$9 a device a month. Your first device is free for 14 days.
Sign in with your Microsoft 365 work account, connect the mailbox your devices send as, and add your first device.