01A bounce suppresses the address automatically
When Amazon SES reports a bounce, MailEnv:
- Marks the message as bounced in your email logs, with the bounce type and reason.
- Changes the recipient's subscriber status to invalid.
- Sends you a dashboard notification naming the address and the reason.
There's nothing to set up. This runs on every account, for every send.
02Future sends are blocked before they reach SES
Once an address is invalid, MailEnv refuses any new send to it with a 403. The request never reaches Amazon SES, so it can't bounce again or add to your bounce rate.
Handle the 403 in your code by logging it and moving on. Don't retry: the address won't become sendable on its own.
03Check suppressed addresses
Open Subscribers and look at the Invalid count. Search for a specific address to see its status.
Open notifications from the bell icon to see recent bounces with their reasons. Email Logs shows each message's final status: delivery, bounce, complaint, or reject.
04Watch complaints too
When someone marks your email as spam, the message shows a complaint status in your email logs. Complaints hurt your reputation even faster than bounces: Amazon SES starts a review at a 0.1% complaint rate.
If you see complaints, stop emailing that person, and check that everyone on the list really asked for your mail.
05Keep bad addresses out from the start
The suppression list catches problems after they happen. Verification stops them before they happen: new addresses are checked before the first send. Learn how to clean your list.