Article
Mailgun High Bounce Rate Warning: How to Fix It Fast
By Unlimited Verifier Team ·

Summary
A Mailgun high bounce rate warning means too many recent messages were permanently rejected, so Mailgun flags your list quality as a risk. To clear it, suppress every hard bounce, verify the remaining list, and bring your rate under 2%. Mailgun's public documentation does not publish a fixed threshold for this warning, so treat the figure in your notice as authoritative.A Mailgun high bounce rate warning means too many of your recent messages were permanently rejected, so Mailgun is flagging your sending as a list-quality risk; to clear it, suppress every hard bounce, verify the remaining list, and get your rate under 2%. The warning is an early signal rather than a suspension, but accounts that ignore it can move to formal review, so act while the problem is still concentrated in one segment.
Quick answer
- Read the notice first. Note the sending domain, the time window and the rate it cites. That is the number you must bring down.
- Separate list bounces from reputation bounces. Failures in the 5.1.x family (such as an unknown mailbox) respond to list cleaning. Policy blocks (5.7.x) and throttling (4.7.0) do not.
- Suppress, then verify. Keep every hard bounce suppressed, verify the rest of the list, and send only Valid contacts at first.
- Plan to 2% as your ceiling and 1% as your target for the first sends after the warning clears. Mailgun's documentation doesn't publish a fixed figure for this warning.
- Don't clear Mailgun's bounce list to reset the rate. You will simply re-mail the dead addresses.
What does a Mailgun bounce warning actually measure?
A Mailgun bounce warning measures permanent delivery failures as a share of your sends over a recent window. The inputs are what receiving servers reported back to Mailgun, not your own view of list quality.
Mailgun is an email sending API owned by Sinch. A hard bounce is a permanent failure: the receiving server says the address cannot accept mail. A soft bounce is temporary, such as a full mailbox or a throttling response, and the sender may retry. Mailgun records hard bounces on its bounces list and stops sending to those addresses, which is why a hard bounce usually stops repeating once it is recorded.
Confirm which denominator your notice uses. Dividing failures by accepted messages and by delivered messages produces different rates, so compare like with like before you decide whether you are under the line.
Bottom line: The warning counts permanent failures against your sends. Your job is to shrink the failures, not to argue about the denominator.
What bounce rate triggers Mailgun's warning?
Mailgun doesn't publish a fixed threshold for this warning in its public documentation, as far as we can determine, and the trigger can vary with account history and sending pattern. Treat the figure in your notice or dashboard as authoritative, and plan to a 2% ceiling with a 1% target.
Other published figures are useful context, though they measure different things:
- Amazon SES states in its documentation that it reviews accounts at a 5% bounce rate and may pause sending at 10%. These are SES rules, not Mailgun's. Our Amazon SES bounce rate limit explained guide walks through them.
- Google's sender guidelines ask bulk senders to keep spam complaints below 0.3%. That is a complaint measure, not a bounce measure, so don't mix the two.
- Many platforms act before 5% when one campaign hits a stale list. Our pillar guide on high bounce rate account suspension covers how these thresholds interact.
Why 2%? Sources disagree, and a 5% trigger leaves almost no margin once a bad batch lands. A 2% ceiling gives you room before most automated triggers, and the 1% target keeps re-entry sends well clear of it.
Low-volume senders face a sharper version of the problem. If 30 of 400 messages bounce, that is 30 ÷ 400 = 7.5%, and one batch can cross any threshold. What bounce rate gets your ESP account suspended compares limits across platforms.
Bottom line: No Mailgun number is confirmed in public documentation, so plan to 2%, aim for 1%, and treat your notice as the final word.
Why does the warning fire when most of my list looks fine?
Averages hide concentrated problems. An account can sit at around 2% overall while one imported segment runs at 7%. The warning responds to the total, but the cause is usually a single source.
Three patterns explain most surprises:
- Imports and legacy segments. Purchased, scraped or old CRM lists often carry years of dead addresses. Why did my bounce rate jump after importing a list covers the usual causes, and how to avoid ESP suspension when importing old lists covers prevention.
- Repeated soft failures. A mailbox that stays full or keeps throttling can eventually be treated as dead. Some providers stop accepting mail to a mailbox that repeatedly fails, and your logs may then record a permanent failure. Each attempt looked temporary, but the pattern is a list signal.
- Catch-all domains. A catch-all domain accepts mail for any local part at SMTP time, so a send to a nonexistent mailbox can look accepted. The problem stays out of your early delivery stats while the address still carries risk. This is why catch-all flags belong in a warning investigation, and why catch-all email verification is part of the cleanup.
Bottom line: The overall rate is a symptom. Look for the one segment, source or date responsible for most failures.
How do I tell list bounces from reputation bounces?
List bounces are fixed by cleaning. Reputation and policy bounces are fixed by changing what and how you send. Mixing them up can waste weeks of work on the wrong fix.
The SMTP enhanced status codes in RFC 3463 make the distinction practical:
| SMTP reply | Enhanced code | Typical meaning | Fixed by list cleaning? |
|---|---|---|---|
| 550 | 5.1.1 | Recipient mailbox does not exist | Yes. Suppress and verify |
| 550 | 5.1.2 | Bad destination system address (often a domain that doesn't receive mail) | Yes. Remove that domain's addresses |
| 550 | 5.1.3 | Malformed address syntax | Yes. Fix the source form or import |
| 550 | 5.7.1 | Message refused by policy, often reputation or content | No. Address sending reputation and content |
| 421 | 4.7.0 | Temporary rate limiting or throttling | No. Slow down sends |
| 452 | 4.2.2 | Recipient mailbox full | Not directly. Suppress only after repeated failures |
Receiving providers word their messages differently, so rely on the enhanced code rather than the text. If 5.7.1 errors rise while your list is clean, the problem is reputation, not addresses. Check Google Postmaster Tools for domain reputation and spam-rate data, and read can a single campaign ruin sender reputation for the recovery path.
Bottom line: The 5.1.x codes respond to list cleaning. If most of your failures are 5.7.x or 4.7.0, a clean list alone won't clear the warning.
How do I find the campaign or import causing the spike?
Pull the permanent failures for your window, group them by date, tag and domain, and match each cluster to a known event. Spikes usually begin on a specific day, and that day points to a campaign or import.
Use message tags. Mailgun's o:tag parameter lets you label each send by campaign or source, so failures can be grouped without guesswork. If you didn't tag sends, match failure timestamps to your import dates and campaign calendar.
Use this table to form a hypothesis:
| Pattern in the failure data | Most likely cause |
|---|---|
| One sudden spike on one date, concentrated in one tag | One campaign hit a stale or newly imported segment |
| A steady climb over several weeks | A signup form or integration is accepting bad addresses |
| Many failures to one company's domain | A source list or acquired contacts from that organisation |
| Many random-looking addresses on free-mail domains | Bot signups or a scraped source |
Once you have a hypothesis, check the source directly. Ask who added those contacts, when, and by what method. Write the answer down, because it becomes the root-cause sentence in any review.
Bottom line: Spikes have dates and owners. Find the date, then find the source.
How do I fix a Mailgun bounce warning step by step?
Work through these seven steps in order. Each one produces evidence you will need if the warning becomes a review.
- Pause sends to the flagged segment. Every new send to a bad segment adds to the failures, so stop before you start cleaning.
- Export the permanent failures for the period in your notice. Keep address, code, timestamp and tag. Filter failed events for permanent severity in Mailgun's logs, or pull the same data from the bounces endpoint of Mailgun's API.
- Diagnose the pattern using the table above, then write one sentence naming the cause. This sentence opens your remediation message.
- Confirm the suppressions. Check that every hard bounce is on Mailgun's bounces list and record the count. This protects you from re-mailing them.
- Verify the full remaining list. Include contacts that never received the failing send, because they can be just as dead. An address that wasn't mailed this time is still untested.
- Re-send only verified segments, starting with the most engaged contacts and ramping over one to three weeks. For dormant segments, is it safe to email a list that is two years old explains when a cautious approach is needed.
- Monitor every send by tag. Set a warning at 1% and a stop at 2%. A stop means halting the segment until you know why.
Step 5 is where most teams cut corners. Deleting only the bounced addresses leaves the rest of the source untested, and a reviewer will see that gap.
Bottom line: Diagnose before you delete, verify everything, and watch each send against a hard ceiling.
Should I clear Mailgun's bounce suppression list?
No. Mailgun's suppression list stops your account from repeatedly mailing addresses that have already failed. Clearing it re-exposes you to those addresses, and each new failure feeds the rate the warning measures.
There is one narrow exception. If a bounce came from your own error, such as a typo in a domain you have since corrected, remove only that address and document why. Verify it first. Clearing the whole list to "reset the numbers" is one of the fastest ways to turn a warning into a review.
Bottom line: Keep the suppressions. Remove an entry only with evidence that the bounce was your mistake.
Which email verification option fits a Mailgun sender?
For a one-off cleanup of a large legacy list, a bulk verifier with clear output buckets is usually the fastest route. For ongoing checks inside your own systems, add an API step. The right choice depends on volume, on who maintains the process, and on what the output needs to show.
| Option | How it runs | What you get | Best fit | Watch-outs |
|---|---|---|---|---|
| Mailgun's email validation API | Called from your code against Mailgun's service | Validation results returned to your application | Teams already scripting against Mailgun | You build the sorting, suppression and audit logic yourself. Check current pricing and limits in Mailgun's documentation |
| Unlimited Verifier | Web upload or API | Results sorted into Valid, Risky and Invalid, with catch-all, disposable and role-based flags | Bulk cleanups of large legacy lists that need an audit trail | No native Mailgun integration, so you export, verify and re-import, or script the API |
| DIY SMTP probing | Your own servers | Raw server responses | Engineering teams with time to maintain it | Many mail servers rate-limit or block probing, and catch-all handling is left to you |
| Relying on Mailgun's bounce list alone | Nothing new | Only addresses that have already failed | Minimal effort | Every untested address stays in the list |
For Unlimited Verifier, the differentiators that matter during a warning investigation are three-bucket output, catch-all detection, flags for disposable and role-based addresses, and export as CSV, Excel or JSON. The engine's code is published as an open-source verifier on GitHub, so your team can review the checks. Compare email verification pricing on the volume you will really process, not the headline rate. For a broader view, see the best email verification tools and our buyer's guide to choosing an email verifier.
Bottom line: Use a bulk verifier with clear buckets for the cleanup, then add an API step if you need checks to run continuously.
How do I clean my list and clear the warning?
This walkthrough uses Mailgun's dashboard and the Unlimited Verifier web app. Adjust the Mailgun steps to match your version of the dashboard.
- Export your permanent failures. In Mailgun, open the logs for your sending domain, filter failed events with permanent severity, and set the date range from your notice. Export address, error code, timestamp and tag as a CSV.
- Export your full sending list from your CRM or source platform. Include the email column and any engagement field, such as last open or last purchase date.
- Create a free account. The Free plan covers 25 lists a month of up to 150 emails each, plus 750 deep verifications a month. It has no API access, and results are kept for 24 hours, so download them the same day.
- Upload and verify a list. Accepted files are CSV or Excel up to 10MB, and the email column is detected automatically. Pro handles lists of up to 25,000 emails each, so split larger files first.
- Read the three buckets.
- Valid: suitable for re-entry sends.
- Invalid: remove and suppress.
- Risky: includes catch-all, disposable and role-based addresses. Hold these back.
- Export the results as CSV, Excel or JSON, and record the summary counts for your remediation message. Pro keeps results for 30 days, but save your own copy regardless.
- Suppress the Invalid addresses in Mailgun through the bounces endpoint of its API or your existing suppression import process. Confirm the count matches your export.
- Re-import only Valid contacts into your source system as a new segment. For any individual address that matters, run it through the free single-email checker first.
Bottom line: Export failures, export the list, verify, suppress Invalid, hold Risky, and re-import only Valid.
What does a worked cleanup look like with real numbers?
The figures below are hypothetical, but the arithmetic and plan limits are real.
The situation. Over one week, a SaaS company sent 120,000 messages from Mailgun across three campaigns, drawn from two sources: a 40,000-contact legacy CRM list and an 80,000-contact opt-in list.
- Legacy list: 2,760 hard bounces. 2,760 ÷ 40,000 = 6.9%
- Opt-in list: 1,080 hard bounces. 1,080 ÷ 80,000 = 1.35%
- Total: 3,840 hard bounces. 3,840 ÷ 120,000 = 3.2%
The account was flagged, and the legacy list was the cause.
Plan limits. On the Free plan, a 40,000-contact list needs 267 lists of 150 (40,000 ÷ 150 = 266.67, rounded up). The Free plan allows 25 lists a month, which is 3,750 emails, so the file would take more than ten months. On Pro, the same list splits into 25,000 + 15,000. Standard verification is unlimited on every plan, so this step carries no per-email charge.
Verification. Suppose the standard run returned:
- Valid: 26,400
- Risky: 8,600
- Invalid: 5,000
Check: 26,400 + 8,600 + 5,000 = 40,000.
Deep verification of the 8,600 Risky addresses uses 8,600 of the 25,000 monthly deep verifications. Suppose it moves 3,100 of them to Valid and leaves 5,500 Risky.
- Final Valid: 26,400 + 3,100 = 29,500
- Final Risky: 5,500
- Final Invalid: 5,000
Check: 29,500 + 5,500 + 5,000 = 40,000.
Suppression. Assume the 2,760 previously bounced addresses are all in the Invalid bucket (check the overlap against your export). That leaves 5,000 − 2,760 = 2,240 new suppressions to add in Mailgun.
Cost. One Pro month is $29, or $25 a month when billed annually. That is the only charge in this example.
Re-entry. Suppose 4,200 of the 29,500 Valid legacy contacts engaged in the last 90 days. The sendable pool becomes 80,000 + 4,200 = 84,200. At a 1% ceiling, each send gets a fixed bounce budget:
| Day | Recipients | Volume | Maximum bounces at 1% |
|---|---|---|---|
| 1 | Opt-in contacts engaged in the last 30 days | 12,000 | 120 |
| 3 | Opt-in contacts engaged in the last 90 days | 30,000 | 300 |
| 7 | Remaining opt-in contacts plus engaged legacy Valid contacts | 42,200 | 422 |
Check: 12,000 + 30,000 + 42,200 = 84,200. If any send exceeds its budget, stop and investigate before continuing.
Bottom line: The arithmetic turns "we cleaned it" into an audit trail: 40,000 addresses in, 29,500 sendable, 2,240 new suppressions and a capped ramp.
How long until the warning clears, and how do I re-enter sending?
The warning clears as the failures in its measurement window age out, so the reported rate lags your fixes. A clean send today does not erase last week's failures from the calculation. Check the window length in your notice to know when to expect improvement.
Reputation recovers more slowly than the rate does. Mailbox providers judge domains on complaints and sending history over time, so inbox placement can lag for weeks after the warning clears. Our guide to how to warm up an old email list after cleaning gives a ramp schedule for this stage.
Keep re-entry grounded in email verification compliance and hygiene. Verification shows that a mailbox probably exists, but it does not prove the person opted in. For US sends, the FTC's CAN-SPAM compliance guide sets the baseline for identification and opt-out requirements.
Bottom line: Expect the rate to fall gradually and reputation to lag behind it. Ramp with a hard cap on every send.
How do I stop the warning from coming back?
Verify at the point of entry, not only during cleanups. The cheapest bounce is the one that never reaches your list.
- At signup: Check addresses as people enter them. Our guide to real-time email validation covers the pattern.
- On every import: Verify before upload, so bad rows never reach Mailgun-connected lists.
- On a schedule: Re-verify active lists monthly or quarterly. Addresses decay as people change jobs, which matters most for B2B lists. Email list maintenance best practices sets out a recurring cadence.
For SaaS and ecommerce senders, where signups arrive continuously, these checks matter more than any one-off cleanup. Industry-specific patterns are covered in email verification for ecommerce and SaaS.
For automation, Unlimited Verifier has no native Mailgun or CRM integration. The practical pattern is:
- Pull recent permanent failures from Mailgun's API.
- Send them to the Unlimited Verifier API. Single-email checks are supported, as are bulk requests of up to 10,000 emails per request. Pro includes 100,000 API emails a month. The Free plan has no API access.
- Add the Invalid results to Mailgun's suppression list.
This loop is the core of email verification API and automation. It removes the monthly manual export and means Mailgun never receives a known-bad address twice.
Bottom line: Verify at entry, verify on import, and automate the suppression loop so the warning doesn't return.
What are the common mistakes that keep the warning alive?
- Clearing the bounce list to reset the rate. You re-mail dead addresses, and the rate climbs again.
- Cleaning only the failing campaign. The untested remainder of the same source still holds the problem.
- Treating a 5.7.x spike as a list problem. Cleaning does not fix policy or reputation blocks, so you will spend weeks on the wrong fix.
- Sending a re-engagement campaign to unverified contacts while the warning is open. You will generate fresh failures while the account is under watch.
- Comparing rates on different bases. A rate on accepted messages and a rate on delivered messages are not the same number. Check your notice's base before you conclude you're fine.
- Losing results on the Free plan. Results are kept for 24 hours, so export them the same day you run them.
- Assuming a catch-all acceptance proves a mailbox exists. It doesn't. Hold catch-all addresses back until you have a reason to send to them.
- Counting verification as consent. A valid mailbox can still belong to someone who never opted in.
Bottom line: Most warnings persist because teams clear the symptom, skip the untested remainder, or send again before the numbers recover.
How we compared (and limitations)
This guide is based on public documentation. We have not tested these checks against Mailgun's systems or its review process.
- Mailgun's public documentation, and the Amazon SES documentation for the threshold comparison.
- RFC 3463 for enhanced status codes.
- Google's sender guidelines and Postmaster Tools for complaint and reputation signals.
- The FTC's CAN-SPAM guide for US consent and opt-out basics.
Mailgun does not publish a bounce threshold we could confirm for this warning, so the 2% ceiling is our planning figure rather than a Mailgun rule. Platform behaviour changes without notice, and the enhanced-code meanings above describe the standard, not every provider's wording.
Unlimited Verifier's plan details come from its published plan facts. The 99.5% deep-verification accuracy figure is the company's own stated number, not an independent benchmark. The worked-example figures are hypothetical, and the arithmetic is shown so you can substitute your own numbers.
Bottom line: Use these thresholds as planning guidance, check Mailgun's notice and documentation for the rules that apply to your account, and measure your own results.
Triage by bounce code
| Code family | Meaning | Action |
|---|---|---|
| 5.1.x | Unknown or invalid mailbox | Suppress and verify the list |
| 5.7.x | Policy or reputation block | Fix authentication, content, and complaints |
| 4.7.0 | Temporary throttling | Slow sending pace and retry later |
Steps: 1) Note the domain, window, and rate in the notice. 2) Filter logs by code family. 3) Suppress all 5.1.x hard bounces. 4) Verify the remaining list. 5) Send first to Valid contacts, aiming for under 1% before expanding.
Frequently asked questions
What is a hard bounce in Mailgun?
A hard bounce is a permanent delivery failure, where the receiving server says the address cannot accept mail. Mailgun records hard bounces on its bounces list and stops sending to those addresses. Soft bounces are temporary, such as a full mailbox, and Mailgun may retry them.
Does clearing the Mailgun bounces list fix the warning?
No. Clearing the bounces list resets the record, but the addresses remain dead, so you will simply re-mail them and the rate will rise again. Keep hard bounces suppressed and remove them from your sending list instead.
What bounce rate does Mailgun consider too high?
Mailgun does not publish a fixed threshold for this warning in its public documentation, as far as we can determine. Use the rate and window shown in your notice or dashboard. A practical plan is a 2% ceiling with a 1% target for sends after the warning clears.
Will my Mailgun account be suspended for a high bounce rate?
The warning is an early signal rather than a suspension, but accounts that ignore it can move to formal review. Acting quickly while problems are concentrated in one segment reduces the risk of further action.
Which bounce codes respond to list cleaning?
Failures in the 5.1.x family, such as unknown mailbox, respond to list cleaning because the address itself is invalid. Policy blocks in 5.7.x and throttling responses like 4.7.0 do not, and need sender-side fixes such as authentication, content, or sending pace.
How do I find which campaign caused the bounces?
Review your Mailgun logs filtered by the time window in the notice, then group failed events by campaign, tag, or sending source. A single stale list or import often accounts for most hard bounces, which makes it the first segment to suppress and verify.
Should I verify my whole list or only the bounced addresses?
Verify the whole list before a large send, not only the addresses that bounced. Bounced addresses are already suppressed, but unverified addresses that never bounced yet may still be invalid. Send first to contacts marked Valid, then expand gradually.
Does SPF or DKIM setup affect bounce rate?
Authentication issues usually cause policy rejections rather than unknown-mailbox bounces, so they belong in the 5.7.x family. Correct SPF, DKIM, and DMARC records help deliverability, but they will not remove dead addresses from your list.
How long does it take for the warning to clear?
The warning depends on Mailgun's evaluation window and the rate it measures. Once your recent failures drop, the rate in the rolling window falls over time. Check the dashboard or notice details rather than relying on a fixed timeline, since the public documentation does not specify one.
Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification
Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.
| Free | Pro | |
|---|---|---|
| Price | $0 | $29/month ($25/month billed annually) |
| Lists | 25 a month, up to 150 emails each | Unlimited, up to 25,000 emails each |
| Deep verifications | 750 a month | 25,000 a month |
| API access | No | Yes (100,000 emails a month) |
| Result retention | 24 hours | 30 days |
Why teams choose Unlimited Verifier
- Unlimited standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
Unlimited Verifier states 99.5% accuracy for deep verification.
Create a free account and verify your next list before you hit send.
Want to test a single address first? Try the free email checker.