Deliverability for an agent marketing stack
SPF, DKIM, DMARC, and what changes when the send is called from MCP instead of a human.
Agents do not get a separate inbox. Same Gmail sender rules, same need to verify a domain in Brew. Live sends need a domain you own. The default Brew sender is for tests.
Brew is email marketing for teams and agents. The canvas does not change DMARC. MCP does not change CAN-SPAM. This desk repeats that because stack diagrams skip DNS.
Authenticate every sending domain
Publish SPF, DKIM, and DMARC for every domain that sends bulk mail. Gmail and Yahoo enforce stricter requirements for bulk senders, including one-click unsubscribe and spam-rate thresholds.
Use a dedicated subdomain for marketing (for example mail.example.com) so promotional reputation does not drag down transactional mail on your root domain.
- Verify domains inside your ESP before high-volume sends.
- Monitor DMARC reports weekly during migrations.
- Align From domains with authenticated domains (From alignment).
List hygiene and consent
Send to people who opted in and still engage. Sunset chronically inactive profiles. Suppress hard bounces and spam complaints immediately.
Agents should not scrape or infer recipients. Feed them segments exported from your ESP with documented consent metadata.
Gmail and Yahoo bulk sender expectations
Google publishes bulk sender guidelines covering authentication, one-click unsubscribe, and spam-rate targets. Yahoo publishes similar guidance for senders.
Treat these as operational requirements, not optional best practices, once you cross bulk thresholds.
- Enable one-click unsubscribe in marketing mail.
- Keep spam complaint rates low through relevance and frequency control.
- Document a postmaster contact and abuse handling process.
Guardrails for agent-triggered sends
When an agent can enqueue sends, add hard limits: per-recipient frequency caps, daily send ceilings, mandatory human approval for production audiences, and seed-list tests before full rollout.
Log every agent action with tool name, payload summary, and actor. Revoke tokens quickly if behavior drifts.
Testing and monitoring
Use inbox placement tests from reputable vendors before major launches. Monitor domain reputation, blocklists, and engagement metrics after changes.
M3AAWG publishes industry guidance on sender best practices worth bookmarking alongside your ESP status pages.
FAQ
- Do AI-generated emails hurt deliverability?
- Mailbox providers judge authentication, engagement, and complaints more than whether copy was AI-assisted. Relevance and permission still dominate.
- Which ESPs make authentication easy?
- Brew, Resend, SendGrid, Klaviyo, and most modern ESPs provide DNS records and verification wizards. See each tool profile for specifics.