A month ago, an error with my business's email address caused it to bounce. Even after I discovered and fixed the issue, this led to a still-unknown amount of emails to silently be suppressed while I carried on unaware.
Email suppressions should be something everyone should be aware about but I've found over the last few weeks that no service provider was aware their mail API services (e.g., Mailgun, Sendgrid, and others) would suppress bounced emails.
I'm writing this article not only to share my experiences, but hopefully raise awareness for this sort of problem with both customers and service providers so no one will have to go through this very annoying mess like I have.
Making a dumb mistake and breaking my email, causing issues I didn't anticipate.
As I am a person who runs this web app, I wanted a personal email address using the domain — [email protected]
Of course, setting up an email address requires some logistics, and I originally went the easy-but-pricey way of setting up Google Apps and paying $5/month. I set up my personal Gmail to receive emails sent from [email protected] and promptly moved onto other things. This was probably done in mid 2018.
In February 2019, I noticed the $5 monthly charge on my credit card and decided to kill my Google Apps account to save myself some pocket change, completely forgetting that that was what powered [email protected] I have a bunch of other emails that were set up using a legacy, free, version of Google Apps that forward to my Gmail account, and in a short-sided moment, I failed to remember that this email address was not set up that way as well, nor that it wouldn't fall back to this behavior after cancelling the paid subscription.
All emails from any service that was using that email would now bounce, and of course, I had no idea this was happening.
Later, a kind soul emailed me to let me know my email address was bouncing, leading to a frantic few hours discovering that I broke my email when I disabled Google Apps, leading me to set up a temporary mail server, and then setting up Google Domains for future forwarding. Voila, [email protected] worked again! I moved forward with my life confident that I fixed the issue.
My inbox felt quieter, but some emails worked.
Weeks again later, I started to notice something weird. I received fewer emails than before, and I would wonder if the email was still working. But when sending myself an email from an outside source, the email would arrive successfully so I would put it out of my mind again.
It wasn't until I few days ago I realized that I wasn't receiving any emails from Gumroad, which was particularly worrying, as I needed to ship physical products after receiving a product payment notification.
(Yes, notifications are enabled. No, they’re not in spam. Yes, other emails from Gumroad are working.) pic.twitter.com/40TRaSaE7R— Tracy Osborn (@tracymakes) March 8, 2019
Gumroad responded that they were having issues with Gmail, so I blamed the whole thing on some disappearing Gmail email bug with Gumroad, and not my fault or responsibility, and put it out of my mind yet again.
Just to add: it's super weird because they don't effect all emails nor do they go into spam. They just don't show up (and then sometimes they do a while later).— Sahil Lavingia (@shl) March 8, 2019
Then I noticed that mailing-list exports weren't arriving in my email from ConvertKit, nor password reset requests. And yet again I sent myself test emails, which arrived promptly, and I reassured myself that my email address was indeed working.
Fixing my own mail service led me to realize that mail API services were silently suppressing my email.
It wasn't until I was working on the new version of this web app when I finally discovered what was actually happening. I launched the new version, and in testing, ran into a 500 error. This should have emailed me a report, which never arrived (of course), so I hustled over to Mailgun to see if my web server actually sent the email.
It was there I discovered how mail API services will silently suppress bouncing emails, and I hadn't been receiving emails from my own mail service for about a month.
Seeing [email protected] suppressed by my own mail service caused a big a ha moment: All web services I used with that email were silently suppressing my emails. It explained why I received some emails, but not others; why emailing from another email address worked fine while emails and notifications from services I used were silently failing.
And web services themselves weren't often aware of this issue, like Gumroad above, who blamed it on Gmail.
I now have the task of pinging every single service I signed up for with this email address to see if my emails are being suppressed.
Web services and support forget that this is a feature offered by their mail API services.
For example, on Mailgun's features page:
The 2 Types of Email Bounces: (...) Hard bounce: messages may permanently fail because the email address doesn’t actually exist or is no longer valid. For this bounce type, bounce management software can automatically suppress these emails from your email lists. This will help you keep a clean email list and a positive email reputation.
On Mandrill's side:
After a bounce occurs for a recipient email address, Mandrill stops attempting delivery of the email. Further email to that address will be rejected temporarily.
Rejections shouldn't be removed in bulk, but if you know that a bounce was temporary or you've resolved an issue with the receiving server, you can remove individual rejections for a small hit to your account's reputation.
Increasing awareness that this is something someone should check out if they suspect email issues.
The original problem was solely my fault, for making a quick, silly decision to cancel a service I was using and not thinking through the consequences.
However, figuring out and fixing the issue has been made so much more difficult due to the services I used forgetting to check their email suppression lists when I emailed in asking for support.
I had also asked several very computer- and web-savvy friends for help figuring out my email issues and they also failed to remember that email suppression lists could have been the cause of my email issues
Fixes if this happens to you.
- Of course, don't make changes to your email provider that could potentially cause bounces. Prevention is the best medicine.
- Password resets are a great way to quickly trigger an email to test whether your email address is being suppressed.
- If you're using an email provider like Gmail, you can add +WORD to your email address (for example, [email protected]ebbooks.com will still go to [email protected]). You can switch out the email used on a website and trigger a password reset to see if an email will then arrive. If they do, that likely means your original email is suppressed by their system.
- Ask support to remove your email address from their email suppression lists, and be prepared to walk them through the process as quite a few I conversed with weren't aware this could be an issue.
This has been a fun issue to diagnose and fix over the last few weeks and I've learned a lot in that time. Here's hoping it helps you as well!