SES, SMTP and custom sender integrations.
Total traffic cap for this provider account. If the cap is reached, emails stay queued and retry later.
Recipient domains this provider must not touch. Example: put gmail.com when SES is weak for Gmail.
SNS bounce and complaint events create hints. Block means cool or exclude that domain on this provider.
| Provider | Rules | Use When |
|---|---|---|
| Amazon SES shared | Use 60-80% of SES quota, never above MaxSendRate. | Transactional and normal production traffic. |
| Amazon SES dedicated IP | Start low; increase over 2-6 weeks by ISP/domain. | High volume with reputation control. |
| Custom SMTP | Start 1/min, 20/h, 100/day until provider proves stable. | Unknown SMTP vendor or mailbox-style sender. |
| Custom HTTP | Start below vendor docs, then adjust from bounce/complaint data. | Mail API provider, internal relay, or future custom sender. |
| Service | What It Tells Us | How We Should Use It |
|---|---|---|
| Google Postmaster Tools | Gmail domain reputation, IP reputation, spam rate, auth errors. | Drive Gmail-specific cool down and routing hints. |
| Microsoft SNDS / JMRP | Outlook/Hotmail complaint and IP reputation signals. | Cool down Microsoft domains separately from Gmail/Yahoo. |
| Yahoo / AOL complaint feedback loop | Complaint events for Yahoo-managed inboxes. | Feed domain health just like SNS complaints. |
| Provider webhooks | Delivery, bounce, complaint, deferral and throttle events. | Update email status and provider/domain health automatically. |
AMAZON_SES · eu-central-1 · 7200/min · 100/h · 4000000/day