Skip to content

E2a

v1.0.6 Security

This release includes 1 security fix for security teams reviewing exposed deployments.

Published 1mo Communication & Email
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →
This release patches 1 known CVE

Topics

ai-agents email email-api go hitl human-in-the-loop
+3 more
mail-gateway smtp webhook

Affected surfaces

auth

Summary

AI summary

Updates Features & improvements, Highlights, and 6ddd35c across a mixed release.

Full changelog

Highlights

Breaking — email.received is now a metadata-only notification (#321)

email.received no longer embeds the message body (raw_message) or the raw auth_headers blob. Subscribers now fetch the full message (body + attachments + signed headers) from GET /v1/agents/{recipient}/messages/{message_id} using the message_id + recipient in the event — the same notify→fetch model client.listen() already uses. The raw auth_headers blob is replaced by a structured auth verdict ({spf, dkim, dmarc}, same shape as MessageView.auth) so agents keep their trust-decision input inline.

Why: bounds the webhook fan-out payload (no raw MIME / attachments amplified across N subscribers × retries) and stops shipping full message PII to every subscriber. Migrate any email.received consumer that read raw_message/auth_headers to the fetch model (auth is available inline).

Features & improvements

  • Envelope-encrypt DKIM private keys at rest (#322) — per-domain DKIM signing keys are now encrypted in the database.
  • Per-axis SES sending status (#309) — domains report which DNS record (DKIM vs MAIL FROM) still needs fixing, instead of an all-or-nothing rollup.
  • verify_domain detects a truncated/mismatched DKIM record (#312) — a clipped DKIM TXT now reports dkim: "mismatch" (distinct from missing) with a "re-publish the full value" hint, so it can't silently leave a domain stuck pending.
  • Forwarding carries the original message's attachments by default (#314).

Fixes

  • Inbound gate fails closed for shared-relay senders (#316, #299) — security hardening of the inbound authentication gate.
  • HTTP MCP server is now stateless (#317).
  • Events API gated on the outbox flag — returns 501 when disabled (#315).
  • SDK version-skew guardrails in CI (@e2a/[email protected]) (#310).
  • HITL approval buttons stack on mobile so they render correctly (#313).
  • Web: wrap long DNS/identity values so records & chips don't overflow (#311); stop overlaying the SPF probe onto the ownership DNS row (6ddd35c).

Docs

  • Webhook examples aligned with the metadata-only email.received (#323).
  • Documented the inbound gate's From-authentication limitation (#318, #320).

Full changelog: https://github.com/Mnexa-AI/e2a/compare/v1.0.5...v1.0.6

Breaking Changes

  • `email.received` no longer includes `raw_message` or `auth_headers`; subscribers must fetch the full message via `GET /v1/agents/{recipient}/messages/{message_id}`.
  • Per‑domain DKIM private keys are now encrypted at rest in the database.

Security Fixes

  • Inbound gate fails closed for shared‑relay senders — security hardening of inbound authentication (#316, #299).
View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track E2a

Get notified when new releases ship.

Sign up free

About E2a

All releases →

Related context

Related tools

Beta — feedback welcome: [email protected]