explaingit

mnexa-ai/e2a

Analysis updated 2026-05-18

133GoAudience · developerComplexity · 4/5Setup · moderate

TLDR

An authenticated email gateway that gives AI agents a verified email address to send and receive mail.

Mindmap

mindmap
  root((e2a))
    What it does
      Verified agent email
      SPF DKIM checks
      Signed headers
    Delivery
      Webhook for cloud agents
      WebSocket for local agents
    Outbound
      Agent to agent relay
      Agent to human via SMTP
      Human in the loop approval
    Tooling
      CLI
      TypeScript SDK
      Python SDK
    Audience
      Developers
      AI agent builders

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Give an AI agent its own email address it can use to send and receive verified mail.

USE CASE 2

Hold outgoing agent emails for human approval before they are sent.

USE CASE 3

Let two AI agents email each other through a relay without setting up their own mail servers.

USE CASE 4

Verify that an inbound email really passed SPF and DKIM checks before trusting its sender.

What is it built with?

GoDockerPostgreSQLTypeScriptPython

How does it compare?

mnexa-ai/e2aimshire/xu-shopadguardteam/urlfilter
Stars133140113
LanguageGoGoGo
Last pushed2026-06-25
MaintenanceActive
Setup difficultymoderatehardhard
Complexity4/54/53/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Self-hosting needs Docker, and receiving real inbound mail requires pointing DNS MX records at the relay.

The README shows a license badge but the specific terms are not detailed in the text shown.

In plain English

e2a is a service that gives AI agents their own working email address, letting them send and receive messages the same way a person does, while checking that every sender on both sides is who they claim to be. When an email arrives, e2a checks standard authentication signals, SPF and DKIM, to confirm it really came from where it says it did, then attaches its own signed headers before passing the message along. Agents running in the cloud receive new mail as a webhook, a message pushed to a URL you provide, while agents running locally can instead connect over a WebSocket and get notified without needing a public web address. On the way out, agents can send mail to other agents through e2a's own relay, or to real humans through an upstream mail provider such as Amazon SES or Resend. One notable feature is an optional human in the loop step: outgoing mail can be held until a person approves it, either through a dashboard, a link sent by email, or the command line. This gives a way to keep a person in control of what an autonomous agent actually sends. The project includes a command line tool along with TypeScript and Python software development kits, so a developer working in either language can plug the authentication and message handling into their own code without dealing with the raw email protocol directly. You can either sign up for a hosted version at e2a.dev, which gives you a shared domain with no DNS setup needed, or run e2a yourself using Docker, which starts a database, an API server, an SMTP relay, and a dashboard in one step. Running your own copy requires pointing a domain's mail records at your server if you want to receive real inbound email.

Copy-paste prompts

Prompt 1
Help me self-host e2a with Docker Compose and create my first API key using the bootstrap command.
Prompt 2
Show me how to verify a webhook signature using the Python SDK before trusting the email sender.
Prompt 3
Explain the difference between cloud mode and local mode agents in e2a.
Prompt 4
Walk me through setting up the human in the loop approval flow for outbound agent emails.

Frequently asked questions

What is e2a?

An authenticated email gateway that gives AI agents a verified email address to send and receive mail.

What language is e2a written in?

Mainly Go. The stack also includes Go, Docker, PostgreSQL.

What license does e2a use?

The README shows a license badge but the specific terms are not detailed in the text shown.

How hard is e2a to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is e2a for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.