Suppression Strike System
Less aggressive suppression.
We had a whole lot of email addresses marked as bad because we tried sending emails during the cloudflare outage last week (https://blog.cloudflare.com/cloudflare-outage-on-july-17-2020/). These were automated reports that didn't go to management all weekend because the email addresses were blocked.
I suggest adding a strike feature - maybe if an email fails 3 times for certain reasons (mx records for example) then it's suppressed. Otherwise you end up with issues like this where I have to explain to my bosses why the reports didn't go out and it makes them question why we're using mailgun and not another provider.
Thank you very much for your feedback. The fact that addresses were being suppressed for events where MX records don’t exist was due to a bug in our suppression logic. We’ve since fixed this bug and you should no longer see addresses suppressed due to missing MX records (this would be a soft bounce).
Given this information, I’m curious if this solves your concern?