On-premise SMTP with OAuth 2.0 for sending outbound emails
Sending emails via SMTP is a common practice for any organization. Outbound emails are sent from devices like multifunction printers, scanners, and application servers interacting with users online. Recent policy changes to Microsoft Exchange Online and Google Workspace require organizations to use OAuth 2.0 instead of SMTP authentication for email delivery. OAuth 2.0 offers enhanced security and is, therefore, a preferred protocol.
On the one hand, using OAuth offers a secure authentication mechanism; on the other hand, many legacy applications and devices cannot use it because they cannot talk OAuth. Many companies use Xeams to bridge this gap.
The following diagram shows a flow diagram.
Benefits of using Xeams
Xeams offers an on-premise version of sending outbound emails using two mechanisms.
- SMTP - with or without authentication
- RESTful API - allowing application servers and mobile apps to send emails quickly
Additionally, every outbound email can:
- Go through a smart host like Microsoft Exchange Online or Google Workspace that requires OAuth 2.0
- Send emails directly to the final destination
- A DKIM signature can be added to every outbound email