Why does Mailgun return 552 552 5.2.2 'over quota' when sending emails?

You sent a batch of transactional emails. The first few go through. Then, abruptly, you get a 552 5.2.2 error: “over quota rate limit exceeded.” Your logs show no syntax issues. Your domain is authenticated. You’re not being blocked. So why did Mailgun stop you?

That error isn’t a system glitch or a misconfigured DNS. It’s Mailgun enforcing its send rate limits—intentionally, consistently. Every plan tier has a daily and hourly cap. When you hit it, delivery stops until the window resets. This isn’t punishment. It’s a guardrail against abuse, spamming, and service degradation.

Key takeaways

  • Mailgun enforces strict hourly and daily sending limits based on your plan tier and sender reputation.
  • A 552 5.2.2 error means you’ve exceeded your allowed send volume, not that your configuration is wrong.
  • Throttling is a deliberate system feature, not a bug—designed to maintain service stability and prevent sender reputation damage.

How to diagnose if your Mailgun 552 5.2.2 errors are caused by list over-quota or list hygiene problems?

You’re seeing Mailgun 552 5.2.2 errors during spikes in sending volume, but the real issue might be hidden in your list’s quality. Check your sending logs for time-based patterns and correlate them with volume. A sudden burst of 5,000 emails in under a minute can trigger rate limits, but a high ratio of invalid or dormant addresses can indirectly worsen delivery by increasing bounce rates and impacting sender reputation. Clean your list first, then adjust your sending schedule.

Step-by-step diagnosis of 552 5.2.2 error causes

  1. Check your Mailgun dashboard’s sending logs for time-bound error patterns. Look for repeated 552 5.2.2 responses during narrow time windows. If errors cluster at the same moment across multiple recipients, it suggests you’re hitting a rate limit or sending cap, not a recipient-level block.
  2. Correlate error spikes with sending volume spikes. If you sent 5,000 emails in 60 seconds, you likely exceeded Mailgun’s per-minute rate limit. Mailgun enforces rate limits per domain and per IP; exceeding them triggers 552 5.2.2. This is common with poorly throttled automation or bulk campaigns sent without proper pacing.
  3. Review your email list for invalid, inactive, or role addresses. High numbers of invalid or dormant addresses increase bounce rates, which can trigger throttling—even if your sending volume is low. Senders with poor list hygiene often see repeated 552 5.2.2 errors due to recipient-side policies like those documented in RFC 5321, which governs SMTP error codes.
  4. Use bulk verification to assess list health. Run your list through a tool like bulk email list cleaning to identify and remove invalid, disposable, or non-deliverable addresses before sending. This improves deliverability and reduces the chance of hitting rate limits.

Why list hygiene matters even for low-volume sends

Even if your sending frequency is under Mailgun’s rate limit, poor list hygiene can still cause 552 5.2.2 errors. Bounced messages increase your “complaint” and “bounce” rate. If that rate exceeds thresholds, Mailgun may throttle or block your account. A list with 30% invalid addresses won’t just waste sends—it can degrade your sender reputation, triggering automated limits beyond simple volume rules.

Sender reputation isn’t just about volume. It’s about consistency, engagement, and deliverability over time.

By cleaning your list and aligning sending patterns with Mailgun’s technical limits, you reduce both direct rate limit hits and the indirect impact of unreliable delivery.

Mailgun rate limits: What you need to know (without memorizing every detail)

You can send up to 100 emails per minute and 50,000 per day on Mailgun’s standard plans. Exceeding these thresholds triggers a 552 5.2.2 error, meaning your sender is rate-limited. High-volume senders with strong domain reputations may receive higher limits based on historical behavior, but consistent overages can lead to throttling or long-term sender reputation damage.

How Mailgun’s rate limits work in practice

Mailgun applies per-minute and per-day caps to prevent abuse and ensure delivery quality. These are not adjustable on standard tiers—your app or system must handle bursts gracefully. If you hit the minute limit, Mailgun queues additional sends and returns a 552 5.2.2 error until the window resets. This is standard behavior across SMTP providers to protect inbox quality and maintain network stability.

Rate limiting isn’t just a technical hurdle—it impacts delivery. Repeatedly hitting limits signals poor sending hygiene to receiving servers. According to industry data from Return Path, senders with inconsistent volume patterns see up to 30% lower inbox placement over time. Even if you're not blocked outright, a strained reputation affects long-term deliverability.

When reputation matters more than the limit

Mailgun evaluates sender reputation over time. If your history includes clean sending, engagement, and low bounce rates, you’re more likely to receive higher rate limits automatically. Conversely, if your domain has a history of spam complaints or high bounce volumes, your ability to scale even without hitting the cap is reduced.

Let’s be honest: rate limits aren’t the only thing that can break your flow. If your email list is full of invalid, outdated, or disposable addresses, you’ll hit limits faster and suffer more bounces. That’s where proactive list hygiene helps. Tools like Email List Validation help catch invalid addresses before they trigger errors. With 98.9% accuracy, their bulk verification process ensures you’re only sending to real, deliverable recipients—reducing strain on your sending rate and protecting your sender reputation.

For real-time checks during onboarding or API workflows, their real-time email verification API validates addresses instantly. You can also use their bulk verification tool to clean large lists before sending. These steps directly reduce the risk of triggering 552 5.2.2 errors due to poor list quality.

Mailgun’s limits are a feature, not a flaw. They exist to keep the system fair and reliable. The best way to work within them is to send only to valid, engaged recipients. Use reputation-aware tools to validate and segment your list. This approach keeps your inbox placement high and your sending efficient.

The role of email verification in preventing Mailgun 552 5.2.2 errors

Using email verification before sending reduces the number of invalid addresses that trigger Mailgun’s 552 5.2.2 error, which signals an over-quota rate limit exceeded failure. Invalid emails lead to bounces, retry attempts, and spikes in sending volume that can trigger rate limiting. A clean list prevents unnecessary strain on Mailgun’s delivery system and maintains sender reputation.

How invalid addresses inflate delivery volume

When you send to a list with many invalid or non-existent emails, Mailgun receives rejection responses for each one. Each bounce counts toward your sending rate, even if it’s not a human inbox. If your system retries or attempts to re-deliver non-deliverable addresses, you can exceed Mailgun’s rate limits—leading to the 552 5.2.2 error, even if your message is otherwise legitimate.

Let’s say you send to 10,000 emails with 1,500 invalid ones. That’s 15% bounce rate. If Mailgun’s threshold is 10% in a short time window, you’re likely to hit a rate limit—even if the rest of your list is active. Verified lists keep bounce rates below threshold levels, avoiding this trigger altogether.

Verifying in real time prevents hidden failures

A real-time verification API doesn’t just detect invalid addresses—it also flags risky ones, like those on catch-all domains or disposable email providers. These aren’t technically wrong, but they often delay delivery or trigger filtering. Catch-all domains accept all emails, so Mailgun may deliver to them, but without confirmation the message never reaches a real person. That counts as a failed delivery and can push your sending volume too high.

Tools like real-time email verification check for syntax, domain validity, and mailbox existence in microseconds. They surface addresses likely to be delayed or blocked—even if they don’t return an immediate error. You avoid the cascading issue where a single delayed or rejected email causes retries that push you over rate limits.

Industry standards like RFC 5321 define how email servers handle delivery errors and timeouts. When a system fails to comply with accepted practices—like retrying indefinitely or sending to high-bounce volumes—it gets flagged. Verifying your list ensures your sending behavior aligns with these expectations.

Most email providers, including Mailgun, treat consistent high bounce rates as a sign of poor list hygiene. This directly impacts sender reputation and increases the chance of being throttled or blocked. A verified list is not just more accurate—it’s more sustainable.

5 steps to fix and prevent Mailgun 552 5.2.2 errors from recurring

You’re hitting Mailgun’s 552 5.2.2 "over quota rate limit exceeded" error because your send volume exceeds your plan’s limits or your list contains addresses that cause retries or rejections. Fix it by cleaning your list first: remove invalid, role-based, and disposable emails; reduce bounce risk; send in bursts instead of spikes; monitor your per-minute volume; and test deliverability after cleanup to confirm inbox placement. These steps resolve the immediate error and stop it from coming back.

Diagnose the root cause with list health

Before you adjust sending patterns, know what’s in your list. You might be hitting limits because of old, invalid, or role-based addresses like admin@, sales@, or support@. These often bounce or trigger rate-limiting on recipient servers. Let’s start by removing them.

  1. Run a full list validation to catch invalid addresses, role-based emails, and disposable domains. Use a tool that checks against real-time data, not just syntax. Many of these addresses won’t deliver, and Mailgun counts them against your quota when they fail.
  2. Identify and remove high-bounce-risk addresses like those from temporary or throwaway domains. Even if an address seems valid, it may generate a hard bounce or blocklist after a few attempts. Repeated retry attempts on those addresses can trigger rate limiting.
  3. Implement staggered sending — don’t send all emails at once. Spread deliveries across 15–30 minute intervals. This keeps your send rate under your Mailgun plan’s cap and avoids triggering throttle mechanisms. For long-running campaigns, schedule send windows throughout the day.
  4. Monitor sending volume per minute. Mailgun limits the number of emails you can send per minute based on your plan. Use your provider’s dashboard or a tool like MxToolbox to track your real-time sending rate and adjust if you're approaching the limit.
  5. Use inbox placement testing after cleanup to verify your improved list now lands in inboxes, not spam folders. Send a test batch to known addresses and check real delivery results, not just SMTP success. Tools like inbox placement testing simulate real-world delivery conditions.

Fixing 552 5.2.2 isn’t just about sending less—it’s about sending smarter. High-quality, cleaned lists behave better with ISPs and avoid hitting infrastructure limits in the first place. You’ll send more reliably, with fewer bounces and lower risk of being throttled.

Rate limiting isn’t a punishment—it’s a defense. Sending responsibly is how you stay on good terms with Mailgun and other providers.

How Email List Validation helps reduce Mailgun rate limit errors

You’re hitting Mailgun’s 552 5.2.2 "over quota" error not because of sending limits, but because your list is full of invalid or high-risk emails. Validating your list upfront cuts dead addresses, catch-all accounts, and disposable domains—common causes of rejected sends—reducing bounce fatigue and helping you stay under throttling thresholds. A clean list means fewer failed deliveries and a healthier sending reputation. SMTP standards define how email servers handle rate limits and rejection codes; ignoring invalid addresses violates the underlying mechanics.

Full-stack verification prevents wasted sends

  • Our service performs full syntax checks, SMTP-level validation, and catch-all detection—each layer catching what others miss. This 98.9% accurate process identifies hard bounces and risks before they hit Mailgun’s servers.
  • Disposable domains and role accounts (like admin@ or support@) are often flagged by Mailgun’s filters. We catch them early, so they don’t consume your quota.
  • Greylisted domains may appear valid but delay delivery. Our engine flags these cases, so your automation doesn’t retry unnecessarily and spike throttle events.
  • High-risk or unverified addresses can trigger sender reputation penalties. By validating your list, you reduce the signal noise that leads Mailgun to enforce stricter rate limits.

Seamless integration reduces manual work

  • Validate up to 100 emails for free with no expiration. No rush—your credits stay active until you’re ready to scale.
  • Use our real-time verification API to clean emails as they’re added—ideal for forms, onboarding, or CRM syncs.
  • Automate cleansing before sending with native integrations for Mailgun, SendGrid, HubSpot, and Klaviyo. Clean data enters the system; bad addresses never trigger a 552 error.
  • Run inbox placement tests to confirm your verified list lands in inboxes—not spam—before bulk sending. This improves deliverability and keeps your sender reputation strong.

When every send counts, fixing delivery issues at the list level is smarter than reacting to 552 errors after the fact. A proactive validation step isn’t a workaround—it’s how top deliverability teams operate. Clean your list in bulk and send with confidence.

Common list hygiene mistakes that indirectly trigger Mailgun rate limits

You’re hitting Mailgun’s 552 5.2.2 error not because of a config issue, but because your list contains too many invalid, outdated, or spam-trap-like addresses. Sending to lists with 30%+ invalid emails floods Mailgun’s systems, triggering automatic rate limiting. Even if your emails are technically valid, poor list hygiene creates feedback loops that look like abuse to Mailgun’s reputation filters.

Outdated lists with high invalid rates

Many teams reuse old lists without cleaning. Addresses change. Users leave. Domains shut down. If your list has 30% or more invalid or undeliverable addresses, it doesn’t just waste send capacity—it actively degrades sender reputation. Mailgun monitors bounce rates and hard failures; consistently high volumes trigger throttling. You might send only 100 emails, but if 30 fail immediately, Mailgun may halt your next batch. This isn’t a delivery problem. It’s a list hygiene problem.

Automating without rate limit awareness

Let’s be clear: automation doesn’t eliminate rate limits. When you schedule mass sends every 10 seconds without respecting Mailgun’s API limits, you’re inviting the 552 5.2.2 error. You might not be sending at maximum speed, but if your code doesn’t throttle based on delivery responses—including temporary failures—you’re still stressing Mailgun’s systems. Industry best practices recommend pacing sends based on real-time feedback and respecting the SMTP response codes that govern message handling.

Role-based and disposable emails

Emails like admin@, info@, or contact@ are rarely used for personal engagement. They often resolve to catch-all servers, which return “valid” responses but never deliver to real people. These addresses inflate your send count without ROI and often get flagged by spam filters. Disposable domains (e.g., mailinator.com, 10minutemail.com) are another red flag. Most fail deliverability checks, and Mailgun blocks them by default. Sending to them triggers spam complaints and reputation hits—even if you never meant to.

These aren’t edge cases. They’re systemic. The fix isn’t in your sending code—it’s in how you maintain your list. Before sending, verify every address. Use real-time validation to catch invalid, role-based, and disposable emails. Bulk-cleaning your list now reduces bounce rates and protects your sender reputation, keeping you under Mailgun’s rate limits.

Before you send, validate. Clean your list once, send with confidence: clean your list at scale.

How to integrate list hygiene into your email workflow

You can prevent Mailgun’s 552 5.2.2 over quota rate limit exceeded errors by validating every email before sending and cleaning your list regularly. Let’s build that into your process so you maintain deliverability without manual checks.

Start with verified data

  • Before uploading any list to Mailgun, run it through a bulk verification tool. This catches invalid, disposable, and catch-all email addresses before they trigger bounces or trigger rate limits.
  • Use the bulk email list cleaning feature to process large lists in minutes—no coding needed.
  • Mailgun’s rate limits apply to actual deliveries, not just attempts. Sending to bad addresses inflates your sending volume and reduces your allowed send window.

Automate maintenance

  • Schedule weekly cleanups of your active lists. Over time, email addresses become invalid—6-8% of a list degrades annually, even with good signups.
  • Integrate the Email List Validation API into your signup or onboarding workflow. This validates emails in real time as they’re entered, blocking known invalid addresses before they hit your database.
  • Set a hard 24-hour verification threshold: if an email isn’t confirmed within that window, reject it. This stops dormant or fake signups from joining your list and keeps your sender reputation clean.
  • Monitor sender reputation using inbox placement tests. If your deliverability drops, a sudden spike in invalid addresses is often to blame.

Industry standards like RFC 5321 and tools like Spamhaus track abusive sending patterns and blacklists. High bounce rates—especially from syntax errors or non-existent domains—are red flags that signal poor list hygiene.

Using real-time verification and automated cleanups isn’t optional; it’s how you stay within Mailgun’s rate limits and maintain inbox placement. It’s the difference between sending and being blocked.

Why real-time verification is better than bulk checks alone

You don’t just need to find invalid emails—you need to know which ones are risky, even if they technically accept mail. Bulk checks tell you what’s wrong after the fact. Real-time verification catches risky addresses *as they’re used*, before they damage sender reputation or get your messages blocked due to spamtrap history or blacklisting. A valid email isn’t always safe.

Beyond the basic "valid/invalid" split

Just because an email address passes a bulk validation doesn’t mean it’s safe to send to. Some domains allow mail delivery but house spamtrap addresses—legacy emails that were once real but are now monitored by blacklist operators. Sending to these can hurt your sender reputation, even if the bounce rate stays low.

Real-time verification goes further. It checks not just syntax and MX records, but also factors like domain reputation, known trap flags, and whether the inbox is a role account (like admin@ or sales@). These signals help you prioritize which addresses to send to—and which to leave alone.

Preventing damage before it starts

Let’s say you’re sending a campaign to 10,000 subscribers. A bulk check might mark all 10,000 as valid. But real-time validation reveals one address is a known spamtrap with a history of abuse. Sending to it can trigger warnings or blocklists, even if it accepts messages for now.

This is where real-time checks shine. They evaluate risk dynamically, using SMTP responses, DNS checks, and reputation data. A domain with high bounce rates or poor sender history gets flagged. You’re not relying on outdated data or assumptions. You’re making real-time, data-backed decisions.

According to Spamhaus, spamtrap detection and reputation analysis are critical in modern email deliverability—because even one bad send can trigger automated filtering systems. Real-time verification is not a luxury; it’s a necessary layer of defense.

For teams using Mailgun, this means fewer 552 5.2.2 errors caused by hitting rate limits or being flagged by recipient servers. You avoid hitting internal limits because you’re not sending to risky addresses that lead to server-level throttling. Real-time validation keeps your sending volume efficient and your reputation intact.

Conclusion: Fix the root cause, not just the symptom

The Mailgun 552 5.2.2 error isn’t a technical glitch — it’s a signal. It means your outbound volume is exceeding the recipient’s rate limits, often due to poor list hygiene, high spam complaint rates, or sending to outdated or invalid addresses.

You can work around it with retries or throttling, but those only mask the problem. True reliability comes from preventing bounces and throttles before they happen — by verifying every email before sending.

Using Email List Validation stops invalid, risky, and over-quota-prone addresses from entering your send queue. This isn’t just about avoiding errors. It’s about building sustainable sender reputation, consistent inbox placement, and predictable deliverability.

Keep reading

Ready to put this into practice? Email List Validation verifies emails with 98.9% accuracy — start with 100 free verifications.

Frequently asked questions

What does Mailgun 552 5.2.2 mean in plain terms?

It means you’ve hit your daily or hourly sending limit on Mailgun. The system blocked further deliveries due to rate throttling.

Can bad list hygiene cause Mailgun 552 5.2.2 errors?

Yes. Sending to invalid or high-risk addresses increases bounce rates and may prompt Mailgun to throttle your account if it detects abuse patterns.

How often does Mailgun reset its rate limits?

Limits reset hourly and daily based on your plan. Reaching the cap during high-volume periods will trigger 552 5.2.2 errors until the next window.

Does removing all invalid emails stop 552 5.2.2 errors?

Not alone. It helps by reducing bounce volume, but you still need to manage sending speed and avoid spikes that trigger throttling.

How can I verify my list before sending to Mailgun?

Use Email List Validation to run bulk verification or connect via API to check addresses in real time before sending.

What’s the difference between catch-all and invalid email addresses?

Catch-alls accept all emails (even invalid ones), while invalid addresses don’t exist. Catch-alls can cause bounces even if the domain is valid.

Can disposable email domains cause 552 5.2.2 errors?

No directly — but they often fail deliverability tests and add load without real engagement, increasing bounce rates and reducing sender reputation.

Is there a way to know my exact Mailgun rate limits?

Yes — check the Mailgun dashboard under 'Sending Limits' or consult your plan settings. Limits vary by tier and reputation.

How does sender reputation affect Mailgun rate limits?

Poor reputation (e.g., high bounce rates) can reduce your send limits or increase throttling, even if your volume is within rules.

Can I use Mailgun with Email List Validation without coding?

Yes. The web app provides bulk uploads and one-click validation. You can also integrate easily with Mailchimp, SendGrid, and HubSpot.

Are there free tools to check if an email is valid before sending?

Yes — Email List Validation offers 100 free verifications to start, with credits that never expire.

Do I need to verify every email after signup?

Yes, ideally. Real-time email verification at sign-up prevents invalid or disposable emails from entering your list in the first place.