Microsoft 365 SMTP for legacy printers
Why older printers and multifunction devices struggle with OAuth, what Exchange Online expects, and where a local bridge fits.
Read guideProblem-solving guides
Practical explanations for connecting printers, scanners, multifunction devices, and legacy applications to modern Microsoft 365 mail infrastructure.
Seven starting points
These guides explain the compatibility boundary and the available solution categories. They are not product installation instructions; RelayBridge remains pre-release.
Why older printers and multifunction devices struggle with OAuth, what Exchange Online expects, and where a local bridge fits.
Read guideA practical look at the scan-to-email path when the scanner can speak SMTP but cannot authenticate to Microsoft 365 itself.
Read guideHow SMTP AUTH, OAuth, XOAUTH2, application identity, and scoped Exchange authorization fit together for older software.
Read guideChoose between client submission, connector relay, Direct Send, and High Volume Email by identity, recipients, network path, and volume.
Read guideDiagnose authentication, Send As, relay attribution, throttling, and TLS failures from the complete server response.
Read guideUnderstand static-IP, certificate, CGNAT, failover, and port 25 constraints across distributed sites.
Read guideSeparate STARTTLS mode, TLS versions, cipher suites, certificate trust, device time, and SNI evidence.
Read guideScope
The guides describe current Microsoft 365 behavior and RelayBridge’s intended v1.0 boundaries. Final installation, provisioning, and device-configuration documentation will be published only after the release flow is frozen.
Documentation statusCurrent implementation
RelayBridge accepts SMTP from explicitly configured local devices, queues durably, and delivers directly to Exchange Online using OAuth and TLS.