Amazon SES Mail Manager
Amazon SES Mail Manager is an email processing service for inbound email. It receives email via SMTP ingress points, applies traffic policies and rule sets, then routes messages to archives, relays, S3, SNS, WorkMail, or drops them.
Key Capabilities
- Ingress Points — SMTP endpoints (OPEN, AUTH, or MTLS) that receive email. Point your MX records here. Configurable TLS policy:
REQUIRED, OPTIONAL, or FIPS.
- Traffic Policies — Connection-level filtering by sender IP, recipient, or TLS version. Evaluated before message body is received.
- Rule Sets — Message-level processing with conditions (SPF/DKIM verdicts, headers, size, IP) and actions (archive, bounce, relay, S3, SNS, Lambda, drop).
- SMTP Relays — Forward email to external SMTP servers with optional authentication.
- Archives — Durable email storage with async search and export. Configurable retention from 3 months to permanent.
- Address Lists — Managed allow/block lists used in rule conditions. Supports bulk CSV/JSON import.
- Add-ons — Third-party integrations (spam filtering, threat analysis) attachable to rule sets.
When to Use This Skill
- Setting up an inbound email processing pipeline
- Walking a developer through Mail Manager configuration decisions step by step
- Filtering spam or blocking senders/IP ranges before email reaches your systems
- Archiving email for compliance, legal hold, or eDiscovery
- Routing email to different destinations based on recipient, sender, or content
- Forwarding email to on-premises or third-party SMTP servers
- Building allow/block lists for email filtering
- Enforcing TLS requirements on inbound connections
What This Skill Does NOT Cover
- Outbound email sending — Use the Amazon SES V2 API (
sesv2 client) for sending email.
- SES core features — Identity verification, DKIM/SPF/DMARC setup, configuration sets, suppression lists. See the
aws-ses skill.
- WorkMail setup — Mail Manager can deliver to WorkMail mailboxes, but WorkMail provisioning is a separate service.
Common Mistakes (Quick Reference)
| Mistake |
Fix |
Using ses or sesv2 client |
Use boto3.client('mailmanager') |
| Creating ingress point first |
Create traffic policy + rule set first |
RecipientCondition in traffic policy |
Use StringExpression with Attribute: RECIPIENT |
Values in TlsExpression |
Use singular Value for TLS expressions |
Missing DefaultAction on traffic policy |
Always set DefaultAction: ALLOW or DENY |
SOURCE_IP in traffic policy |
Traffic policies use SENDER_IP; rule sets use SOURCE_IP |
| Updating rule set without fetching first |
update_rule_set replaces ALL rules — fetch first |
| DNS before ingress point is ACTIVE |
Poll get_ingress_point until Status == ACTIVE |
Evaluate field in DmarcExpression |
DmarcExpression has no Evaluate — just Operator + Values |
Archive ARN in TargetArchive |
Use archive ID (a-xxxx), not ARN — 66-char limit enforced by API |
CFN !GetAtt Archive.ArchiveId returns ARN |
Extract ID: !Select [1, !Split ["/", !GetAtt Archive.ArchiveArn]] |
| Archive name collision after rollback |
Append ${AWS::AccountId} — names persist through PENDING_DELETION |
| FIPS TLS policy can't be changed |
FIPS is immutable after creation — delete and recreate to change |
| TLS policy default varies by region |
FIPS in US/CA, REQUIRED elsewhere — set explicitly |
See Agent Instructions for detailed explanations, full condition/action syntax, and the complete common mistakes list.
Resource Links
- Agent Instructions — Full workflow patterns, condition/action reference, agent instructions
- Getting Started Guide
- Traffic Policy Guide
- Rule Set Guide
- Archive Guide
- Relay Guide
- Address List Guide
- Cleanup Guide
- Troubleshooting Guide
- Guided Setup Decision Tree
- Event-Driven AI Pipeline
- SES v2 + Mail Manager API Index
- Examples
- Mail Manager Developer Guide
- API Reference
Summary
This skill provides the context AI agents need to work with Amazon SES Mail Manager correctly — the right API client, condition/action syntax, resource dependency order, and common pitfalls. Start with the Agent Instructions for the full reference, or use the Guided Setup for an interactive walkthrough.
1---2name: aws-mail-manager3description: Process, route, filter, and archive inbound email with Amazon SES Mail Manager. Use when building email ingress pipelines, spam/IP filtering, compliance archiving, SMTP relay forwarding, address allow/block lists, or any inbound email processing workflow. Covers ingress points, traffic policies, rule sets, relays, archives, and address lists.4license: Apache-2.05---67# Amazon SES Mail Manager89Amazon SES Mail Manager is an email processing service for inbound email. It receives email via SMTP ingress points, applies traffic policies and rule sets, then routes messages to archives, relays, S3, SNS, WorkMail, or drops them.1011## Key Capabilities1213- **Ingress Points** — SMTP endpoints (OPEN, AUTH, or MTLS) that receive email. Point your MX records here. Configurable TLS policy: `REQUIRED`, `OPTIONAL`, or `FIPS`.14- **Traffic Policies** — Connection-level filtering by sender IP, recipient, or TLS version. Evaluated before message body is received.15- **Rule Sets** — Message-level processing with conditions (SPF/DKIM verdicts, headers, size, IP) and actions (archive, bounce, relay, S3, SNS, Lambda, drop).16- **SMTP Relays** — Forward email to external SMTP servers with optional authentication.17- **Archives** — Durable email storage with async search and export. Configurable retention from 3 months to permanent.18- **Address Lists** — Managed allow/block lists used in rule conditions. Supports bulk CSV/JSON import.19- **Add-ons** — Third-party integrations (spam filtering, threat analysis) attachable to rule sets.2021## When to Use This Skill2223- Setting up an inbound email processing pipeline24- Walking a developer through Mail Manager configuration decisions step by step25- Filtering spam or blocking senders/IP ranges before email reaches your systems26- Archiving email for compliance, legal hold, or eDiscovery27- Routing email to different destinations based on recipient, sender, or content28- Forwarding email to on-premises or third-party SMTP servers29- Building allow/block lists for email filtering30- Enforcing TLS requirements on inbound connections3132## What This Skill Does NOT Cover3334- **Outbound email sending** — Use the Amazon SES V2 API (`sesv2` client) for sending email.35- **SES core features** — Identity verification, DKIM/SPF/DMARC setup, configuration sets, suppression lists. See the `aws-ses` skill.36- **WorkMail setup** — Mail Manager can deliver to WorkMail mailboxes, but WorkMail provisioning is a separate service.3738## Common Mistakes (Quick Reference)3940| Mistake | Fix |41|---------|-----|42| Using `ses` or `sesv2` client | Use `boto3.client('mailmanager')` |43| Creating ingress point first | Create traffic policy + rule set first |44| `RecipientCondition` in traffic policy | Use `StringExpression` with `Attribute: RECIPIENT` |45| `Values` in TlsExpression | Use singular `Value` for TLS expressions |46| Missing `DefaultAction` on traffic policy | Always set `DefaultAction: ALLOW` or `DENY` |47| `SOURCE_IP` in traffic policy | Traffic policies use `SENDER_IP`; rule sets use `SOURCE_IP` |48| Updating rule set without fetching first | `update_rule_set` replaces ALL rules — fetch first |49| DNS before ingress point is ACTIVE | Poll `get_ingress_point` until `Status == ACTIVE` |50| `Evaluate` field in DmarcExpression | DmarcExpression has no `Evaluate` — just `Operator` + `Values` |51| Archive ARN in `TargetArchive` | Use archive ID (`a-xxxx`), not ARN — 66-char limit enforced by API |52| CFN `!GetAtt Archive.ArchiveId` returns ARN | Extract ID: `!Select [1, !Split ["/", !GetAtt Archive.ArchiveArn]]` |53| Archive name collision after rollback | Append `${AWS::AccountId}` — names persist through `PENDING_DELETION` |54| FIPS TLS policy can't be changed | `FIPS` is immutable after creation — delete and recreate to change |55| TLS policy default varies by region | `FIPS` in US/CA, `REQUIRED` elsewhere — set explicitly |5657See [Agent Instructions](references/agent-instructions.md) for detailed explanations, full condition/action syntax, and the complete common mistakes list.5859## Resource Links6061- [Agent Instructions](references/agent-instructions.md) — Full workflow patterns, condition/action reference, agent instructions62- [Getting Started Guide](references/setup/getting-started.md)63- [Traffic Policy Guide](references/traffic-policies/traffic-policy-guide.md)64- [Rule Set Guide](references/rule-sets/rule-set-guide.md)65- [Archive Guide](references/archives/archive-guide.md)66- [Relay Guide](references/relays/relay-guide.md)67- [Address List Guide](references/address-lists/address-list-guide.md)68- [Cleanup Guide](references/cleanup/cleanup-guide.md)69- [Troubleshooting Guide](references/troubleshooting/troubleshooting-guide.md)70- [Guided Setup Decision Tree](references/workflows/guided-setup.md)71- [Event-Driven AI Pipeline](references/workflows/event-driven-ai-pipeline.md)72- [SES v2 + Mail Manager API Index](references/api/ses-api-index.md)73- [Examples](examples/README.md)74- [Mail Manager Developer Guide](https://docs.aws.amazon.com/ses/latest/dg/mail-manager.html)75- [API Reference](https://docs.aws.amazon.com/ses/latest/APIReference-V2/API_Operations_Amazon_SES_Mail_Manager.html)7677## Summary7879This skill provides the context AI agents need to work with Amazon SES Mail Manager correctly — the right API client, condition/action syntax, resource dependency order, and common pitfalls. Start with the [Agent Instructions](references/agent-instructions.md) for the full reference, or use the [Guided Setup](references/workflows/guided-setup.md) for an interactive walkthrough.
amazon-ses