Enterprise mail services
Explore Microsoft Exchange mail servers, Amazon SES email delivery, and Gmail mailbox integrations, with three practical guides for each.
Reviewed
Enterprise email is more than a mail server. An organization may operate Exchange for employee mailboxes, use Amazon SES for application delivery, and connect a Gmail inbox to a support workflow. These services solve different jobs; connecting one does not mean replacing the others.
This guide groups them into mail servers, email providers, and email solutions. Start with the product your organization already uses. Each has an introductory index and three task guides below.
Choose the right integration boundary
| Category | Example | What it provides | What to check first |
|---|---|---|---|
| Mail servers | Microsoft Exchange Server | Organizational mailboxes, SMTP transport, and administrator-controlled routing | Deployment edition, connector permissions, TLS, and mail administrator approval |
| Email providers | Amazon SES | Managed outbound delivery and inbound receipt processing | AWS Region, verified identities, IAM permissions, sandbox status, and event handling |
| Email solutions | Gmail / Google Workspace | Hosted mailboxes and mailbox APIs | User consent, permitted OAuth scopes, organization policy, and mailbox quotas |
“Enterprise” describes the integration context, not a licensing claim. Gmail also serves personal accounts; open-source mail systems can have commercial support. Exchange Server is not Exchange Online, and SES is not an IMAP mailbox service.
Keep production mail routing intact
Before connecting a service, decide which system remains responsible for receiving mail and which application actions are authorized. Do not replace a mailbox domain’s MX records to test one application feature. Use a dedicated address, a receiving subdomain, or an administrator-approved forwarding route.
MailKite can receive application mail as signed JSON and send through its SDK. It does not automatically authorize access to Exchange, AWS, or Gmail. The walkthroughs below use supported provider tools, explain where MailKite can take over a job, and do not assume unreleased service-specific adapters.
For platform details, consult the official Exchange Server, Amazon SES, and Gmail API documentation. The categorized article cards below are generated from the same catalog as the sidebar and project indexes.
Mail servers
Microsoft Exchange
Exchange Server provides organizational mailboxes and SMTP transport. These guides cover administrator-approved integration with an existing on-premises deployment, not a new server installation or Exchange Online configuration.
Plan an application integration with Exchange Server
Identify an Exchange deployment, choose an approved sending or receiving path, and verify the administrative boundary before changing mail flow.
Send application email through Exchange Server
Use an approved Exchange SMTP submission endpoint with TLS, a dedicated identity, sender permissions, and a controlled delivery test.
Forward an Exchange mailbox to MailKite
Keep an Exchange application mailbox in place and forward approved messages to a verified MailKite address for signed webhook delivery.
Email providers
Amazon SES
Amazon Simple Email Service is managed application email infrastructure. Use its sending API for outbound messages and receipt rules for inbound processing in supported regions; SES does not provide an IMAP mailbox.
Prepare an Amazon SES sending identity
Choose an SES Region, verify a sending domain, check sandbox access, and separate sending authentication from mailbox routing.
Send application email with the Amazon SES SDK
Send a controlled SES message with the AWS JavaScript SDK, least-privilege credentials, and separate acceptance and delivery tracking.
Receive application mail with Amazon SES receipt rules
Route a dedicated receiving subdomain into SES, store raw email in S3, and build a recoverable processing path without replacing employee mail.
Email solutions
Gmail
Gmail is a hosted mailbox solution, available through personal Google accounts and Google Workspace. These guides connect an existing mailbox through OAuth, the Gmail API, and Pub/Sub while leaving mailbox delivery and MX records in place.
Authorize an application to access Gmail
Choose Gmail OAuth scopes, complete user consent, and configure a server-side client without exposing mailbox tokens or changing MX records.
Send email from an existing Gmail mailbox
Send a controlled message through Gmail's API using scoped OAuth and base64url MIME, while keeping mailbox sending separate from application delivery.
Receive Gmail changes with Pub/Sub and mailbox history
Watch a Gmail inbox, process authenticated Pub/Sub notifications, and synchronize mailbox history with cursor recovery and watch renewal.