Ctrl K
ComunidadGuías…
GITHUB · ANALIZADO

e2a

e2a is an open-source email API for applications and AI agents, providing authenticated inbound identity (SPF/DKIM/DMARC), outbound delivery via SMTP or HTTP, optional human-in-the-loop approval, and structured message threading.

Ficha actualizada 23 sept 2026, 14:09 · upstream 23 sept 2026, 13:57 · release v1.9.1

00

Qué es e2a

Descripción editorial construida a partir del repositorio, su documentación y sus señales de mantenimiento.

e2a provides the open-source email infrastructure that applications and AI agents need to send transactional emails reliably. It eliminates the need for public URLs, port forwarding, or shared hosting platforms by running its own mail server on a single domain. The service evaluates SPF, DKIM, and DMARC records before delivering messages, ensuring deliverability while maintaining full control over email content through an optional human-in-the-loop approval gate.

The architecture separates inbound identity verification from outbound delivery: incoming emails are evaluated against DNS-based authentication protocols to confirm sender legitimacy, then delivered via SMTP or HTTP. Outbound sends can be routed through upstream relays (such as SES) or sent directly to other agents using the same protocol stack. This separation allows applications to remain decoupled from email infrastructure concerns while still receiving authenticated inbound messages.

The API supports multiple delivery channels including REST polling, WebSocket streams, and MCP tool integration for agent frameworks like Mastra, OpenAI Agents SDK, and LangChain. Templates are rendered server-side at send time using template variables, enabling dynamic content without client-side rendering. Contact management includes account-level CRUD operations with bulk import capabilities, while scheduled sends can defer delivery up to 90 days in advance.

The hosted service offers a single-page dashboard for managing agents, messages, and approval workflows, along with an MCP server that enables agent frameworks to interact directly with the email infrastructure without additional tooling. Self-hosted deployments use Docker Compose to run PostgreSQL databases, S3-compatible storage (MinIO), and the full SMTP relay stack on a single machine or cluster.

CASOS DE USO
  • AI support agents triaging customer tickets with threaded conversations
  • AI receptionists handling inbound inquiries with auto-routing rules
  • AI scheduling assistants coordinating meetings across multiple participants
  • E-commerce bots processing order confirmations and return requests
  • Sales agents qualifying leads through personalized follow-up sequences
  • Recruiting coordinators managing candidate communications and interviews
PUNTOS DESTACADOS
  • Provides authenticated inbound identity with SPF, DKIM, and DMARC verification without requiring a public URL or shared hosting
  • Supports multiple delivery channels including REST polling, WebSocket streams, and MCP tool integration for agent frameworks
  • Offers optional human-in-the-loop approval gate that holds outbound mail until manual review via dashboard, email, or API
  • Delivers structured message metadata including thread IDs, conversation IDs, and reply headers compliant with standards
  • Supports template rendering at send time using server-side variables for dynamic content generation
  • Provides contact management with account-level CRUD operations and bulk import capabilities
PRECAUCIONES
  • Content screening (prompt injection detection) is self-hosted only, not available on the hosted service
  • Outbound email delivery to human recipients requires upstream SMTP relays such as SES or Resend
  • Scheduled sends are limited to a 90-day deferral window before submission
  • Template customization requires server-side rendering with template variable substitution
  • The MCP toolset is not yet available for all agent frameworks, limiting integration options
01

Perfil de infraestructura

Estimación inicial derivada del repositorio y de los servicios detectados.

CPU2 vCPUrecomendación inicial
MEMORIA2 GBRAM estimada
DISCO20 GBalmacenamiento base
COMPLEJIDADmediumnivel de operación
02

Despliegue detectado

Qué señales reales de instalación hemos encontrado.

Listo para automatizar

Deploy e2a using Docker Compose on a single machine or cluster. The service runs PostgreSQL for message storage and MinIO-compatible S3 storage for attachments. Configure your domain's MX record to point to the e2a relay address. For self-hosted deployments, set `shared_domain` in config.yaml to use the hosted slug shortcut (e.g., `agents.e2a.dev`). Enable content screening by configuring the LLM detector with appropriate model weights and thresholds. The MCP server is available at https://api.e2a.dev/mcp for agent frameworks like Mastra, OpenAI Agents SDK, and LangChain.

✓Dockerfile
✓Compose
✓One-click
03

Stack y dependencias

Componentes inferidos a partir de manifests, configuración y documentación.

FRAMEWORKS
Next.jsNode.jsGoPython
SERVICIOS
PostgreSQLS3/MinIO
BASES DE DATOS
PostgreSQL
PUERTOS
187898080300054331025802587652525
05

Puede sustituir a

Relaciones detectadas por el análisis del repositorio y su categoría.

06

Experiencia real de la comunidad

Ayuda a contrastar la estimación automática con instalaciones reales.

Todavía no hay datos comunitarios para este proyecto.