Build email into your application

Open the independent mail server guide and its project menu.

Choose a bulk email architecture, handle partial failures, and build recipient-safe delivery with batches, broadcasts, and durable queues.

Build a programmatic newsletter lifecycle with consent records, subscriber preferences, reviewed campaigns, unsubscribe handling, and delivery feedback.

Evaluate cold email platforms and design reply-aware workflows with recipient state, pacing, suppression, and local JavaScript or Python simulations.

Design event-driven email with durable jobs, deduplicated events, scheduled sends, sequence exits, cancellation, and observable recipient outcomes.

PHP 8.1+, Composer, and the PDO SQLite extension.

Python 3.10+; SQLite is included in Python's standard library.

Node.js 22.13+ for the built-in node:sqlite module used here.

Ruby 3.2+ with RubyGems.

A current Go toolchain.

JDK 17+ and Maven. The example uses the JDK HTTP server and Jackson.

.NET 10 SDK and Git. The SDK is referenced from its tested public source revision because the NuGet package is not available.

A current Rust toolchain. Save the receiver as src/main.rs in the inbound project.

Elixir 1.18+ and a compatible Erlang/OTP runtime.

Forward Gmail mail to a signed JSON webhook.

Forward iCloud Mail (Apple Mail) mail to a signed JSON webhook.

Receive and parse inbound email on Amazon SES with receipt rules, S3, SNS and Lambda — then see the same flow on MailKite: one MX record and a signed, decoded JSON webhook.

Set up Brevo's inbound parse webhook to receive email as JSON, then see the same inbound flow on MailKite: one MX record, a signed payload, attachments as links.

Receive and parse inbound email with Cloudflare Email Routing and Email Workers, then see the same flow the MailKite way: one MX record, decoded JSON, signed webhooks.

inbound to app

Set up Mailjet's Parse API to receive and parse inbound email as JSON, then see the same inbound flow the MailKite way: one MX record, a signed payload, attachments as links.

Set up Mandrill inbound email: point an MX at Mandrill, add a route, and parse the mandrill_events payload — then see the same inbound flow the MailKite way.

Set up Postmark Inbound to receive and parse email as JSON, then see the same inbound flow the MailKite way: one MX record, a signed payload, attachments as links.

Receive and parse inbound email on Resend — the MX record, the signed email.received webhook, and fetching the body — then see the same flow the MailKite way.

Set up SendGrid's Inbound Parse webhook to receive email as data, then see the same inbound flow on MailKite: one MX record, a signed JSON payload, attachments as links.

Verify a domain and send transactional email with Amazon SES — over the API or SMTP — then send the same message the MailKite way.

Authenticate a domain and send transactional email with Brevo — over the API or SMTP — then send the same message the MailKite way.

Send transactional email from a Cloudflare Worker with Cloudflare Email Service — binding, REST API, or SMTP — then send the same message the MailKite way.

Authenticate a domain and send transactional email with Mailgun — over the API or SMTP — then send the same message the MailKite way.

Authenticate a domain and send transactional email with Mailjet — over the API or SMTP — then send the same message the MailKite way.

Authenticate a domain and send transactional email with Mandrill — over the API or SMTP — then send the same message the MailKite way.

Authenticate a domain and send transactional email with Postmark — over the API or SMTP — then send the same message the MailKite way.

Authenticate a domain and send transactional email with Resend — over the API or SMTP — then send the same message the MailKite way.

Authenticate a domain and send transactional email with SendGrid — over the API or SMTP — then send the same message the MailKite way.

Build event-driven email with JavaScript: verified sequence payloads, event deduplication, payment-completion exits, and mock-first cancellation.

Send private bulk email with JavaScript: SDK batches, per-recipient outcomes, checkpointed retries, and a runnable Node.js mock.

Send private bulk email with Python using SDK batches, validated results, a recipient ledger, selective retries, and credential-free mock tests.

Send private bulk email with PHP: SDK batches, a CLI checkpoint ledger, partial failures, selective retries, and runnable local mocks.

Build a subscriber-to-broadcast newsletter with the MailKite Node SDK, separate management auth, suppression checks, and a no-send mock demo.

Implement a Python newsletter lifecycle with confirmed subscribers, list audiences, management-token auth, broadcasts, and local no-send tests.

Run a local Node.js outreach simulation with pacing, checkpoints, dedupe, and stop-on-reply. Hosted MailKite excludes unsolicited outreach.

Test a SQLite-backed outreach simulation in Python with pacing, reply cancellation, opt-outs, bounces, and dedupe. No email transport is enabled.

Compare bulk email API limits, personalization, recovery, pricing models, and sending policies for MailKite, SES, SendGrid, Mailgun, and Resend.

Compare listmonk and Keila installation, APIs, editors, segmentation, licenses, transport ownership, and newsletter operations.

Compare Smartlead, Instantly, and lemlist APIs, mailbox connections, reply events, sequencing, pricing models, and current sending-policy restrictions.

Go from zero to a working agent inbox on MailKite: create an account, connect the MCP server, add a domain, and open an inbox your agent can send and receive from.

Give an AI agent its own inbox: send and receive email from your agent. Compare agent-native inbox APIs and the ESPs you can wrap, then the MCP-native MailKite way.

The everyday agent email loop on MailKite: send over a verified domain, read inbound as clean JSON, reply in-thread, and attach files — all as MCP tool calls.

Turn one address into an AI agent that answers inbound email, replies in-thread, and escalates what it can't resolve — one route on MailKite, no server.

Give an AI agent its own email inbox with AgentMail — create it, send, and receive — then the MCP-native MailKite way, where the agent has email tools built in.

Give an AI agent its own inbox with Amazon SES — wrap send and wire up inbound — then the MCP-native MailKite way, where the agent has email tools built in.

Give an AI agent its own email inbox with Brevo — wrap its send API and Inbound Parse webhook as tools — then the MCP-native MailKite way, where email is built in.

Give an AI agent its own inbox with Cloudflare Email Service and Email Routing — send and receive from a Worker — then the MCP-native MailKite way.

Give an AI agent email with the Gmail API — OAuth, sending, and push notifications — then the MCP-native MailKite way, where the agent has email tools built in.

Give an AI agent email with Mailgun — wrap its send API as a tool and receive via Routes — then the MCP-native MailKite way, where email is built-in agent tools.

Give an AI agent its own email inbox with Mailjet — wrap send and inbound as tools — then the MCP-native MailKite way, where the agent has email tools built in.

Give an AI agent its own email with Mandrill — wrap the send API as a tool and take inbound over a route webhook — then the MCP-native MailKite way.

Give an AI agent email with Microsoft Graph — register the app, send, and receive change notifications — then the MCP-native MailKite way.

Connect an existing Gmail, Outlook, or IMAP mailbox to an AI agent with Nylas — send and receive — then the MCP-native MailKite way, where email is native tools.

Give an AI agent email with Postmark — wrap its send API and inbound webhook as tools — then the MCP-native MailKite way, where the agent has email tools built in.

Give an AI agent email with Resend — wrap its send API as a tool and receive via a signed inbound webhook — then the MCP-native MailKite way, where email is built-in tools.

Give an AI agent email with SendGrid — wrap its send API and Inbound Parse webhook as tools — then the MCP-native MailKite way, with email tools built in.