SendGrid: emails accepted (202) but never delivered — recipient is on the bounce/spam/unsubscribe suppression list
SendGrid returns success, but messages to some addresses are dropped because they're suppressed.
SendGrid dropped bounced addressDropped: Bounced AddressDropped: Unsubscribed AddressSendGrid emails accepted 202 but not delivered suppression listDropped: Spam Reporting Address Meaning
Check Suppressions (Bounces, Spam Reports, Invalid Emails, Unsubscribes, Blocks) and the Activity feed for "Dropped". Remove the address from the list after fixing the cause (and only if appropriate), and review your sending practices to avoid new suppressions.
Common causes
- Previous hard bounce or spam report
- Unsubscribed globally or by group
- Typo/invalid email earlier
- Block after a temporary issue
- Subuser-specific suppression lists
⚡ Quick fix
- Look in Activity → Dropped for the reason
- Check and remove the entry via Suppressions
- Fix list hygiene and bounce handling
Detailed fix by platform
Shell
curl -s -H "Authorization: Bearer $SENDGRID_API_KEY" https://api.sendgrid.com/v3/suppression/bounces/user@example.com
How to diagnose
- Activity — Dropped?
- Suppression — Present?
- Cause — Fixed?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 4.4.7 554 4.4.7 Message expired: unable to deliver in 840 minutes (delivery timeout)
- bounce rate Email provider suspended or throttled your account: bounce rate too high (hard bounces from invalid addresses)
- frozen Exim: message is frozen — recipient or sender can't be bounced (frozen bounce messages pile up)
Most viewed in Email / SMTP
- 550 5.7.1 550 5.7.1 Relaying denied / Message rejected as spam / Unauthenticated email not accepted
- Laravel: Connection could not be established with host Laravel: Symfony\Component\Mailer\Exception\TransportException: Connection could not be established with host "smtp.mailtrap.io:2525": stream_socket_client(): Unable to connect
- SES: Maximum sending rate exceeded Amazon SES: Throttling — Maximum sending rate exceeded (454 Throttling failure)
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026