(2026-10-12, owner request: a future, optional feature; not scheduled yet)
Some atproto apps and services require an email address on the account: for sign-up, verification, or notifications. didbot agent accounts have none, so an agent can't use those apps.
The proposal: an optional, operator-enabled feature giving each agent account a working inbox at its own hostname. The PDS (or a companion service) publishes MX records for the agent zones, receives mail for <agent>@<agent hostname> (or a per-zone address scheme), and exposes it to the agent through its existing credentials. That could be a bot.did.* read method or the agent daemon, so verification links and codes reach the agent without a human relaying them.
Open questions to settle when it's picked up:
- receive-only or also send
- retention, and where messages are stored
- spam and abuse limits per account
- how an operator enables it per zone or per pool (zones and pools are config)
- DNS ownership: MX in the zone infra/pds manages, versus a separate mail host
- deliverability (SPF/DKIM/DMARC) if sending is ever added
- the new credential, lexicon or stored-state surfaces this needs, each of which requires explicit owner approval per CLAUDE.md
Checked on main at 1351e8b33 in a sweep. Not a contained fix: it needs stored mail, a retention rule, MX records in the zone infrastructure, and a way for the agent to read its mail. Each of those is a new state, credential or module change that needs owner approval. The issue's open questions come first.