Why Does Mailgun Return 'Quota Probe * * *' in 2026?

You sent a batch of transactional emails through Mailgun’s API—and got back a response: Quota Probe * * *. Not a bounce, not a syntax error. Just a dry, cryptic signal that one or more addresses didn’t get delivered. It’s not an address issue. It’s not a DNS misconfiguration. It’s the system saying: “We’re at capacity.”

By 2026, this message has become a common point of confusion for developers and senders using Mailgun’s outbound API. But it’s not a bug—it’s a deliberate throttle. When you see Quota Probe * * *, it means Mailgun’s infrastructure has hit a sending limit tied to your domain or IP, not the email address itself. Understanding this distinction is critical to fixing the root cause: infrastructure limits, not address validity.

Key takeaways

  • Quota Probe * * * in Mailgun’s outbound API signals a daily rate limit exceeded, not a bounce or invalid address.
  • The asterisks are placeholders; the actual message may vary by environment, but the meaning—rate limit exceeded—remains consistent.
  • Unlike delivery failures, this is an infrastructure-level throttle, not a problem with the recipient's inbox, DNS, or email format.

How 'Quota Probe * * *' Affects Your Email Deliverability

When Mailgun returns a "Quota Probe * * *" error, your email never reaches the recipient’s server—it’s blocked at the sender level due to exceeded sending limits. This isn’t a bounce from the recipient’s inbox; it’s a hard rejection by Mailgun’s delivery system based on rate thresholds. Repeated triggers can weaken your sender reputation and trigger throttling or IP-level restrictions, even if your messages are technically valid.

Why Quota Probes Happen Before Delivery

Mailgun enforces sending quotas to maintain delivery health and prevent abuse. If your outbound volume exceeds your configured cap—whether per hour, day, or by domain—Mailgun stops processing new messages and returns the "Quota Probe" error. Unlike a DNS or SMTP failure, this stops delivery before you even reach the recipient’s mail server.

For example, if your app sends 2,000 messages per hour and your plan allows 1,500, the excess 500 will be caught mid-flight. You won’t see a bounce from the recipient’s system; instead, Mailgun’s API will return this error code directly.

Impact on Sender Reputation and Deliverability

Consistently hitting quota limits, even with valid addresses, signals to email providers that your sending behavior is aggressive or poorly managed. This can lead to degraded reputation scores over time—meaning more messages end up in junk folders, or worse, blocked outright.

Providers like Google and Microsoft use sending volume patterns as part of their spam detection algorithms. Sudden spikes or frequent quota breaches are a red flag, even if every email has a correct, deliverable address. The issue isn’t the content, it’s the sending pattern.

According to industry practices documented in RFC 5321, SMTP servers are designed to reject unauthorized or excessive traffic early. Mailgun’s quota probes are a practical implementation of this principle at scale.

Let’s be clear: high-quality email lists aren’t a fix for poor volume control. If you're consistently hitting quota errors, you’re likely sending too much too fast. Verify your list quality and adjust your sending schedule or infrastructure accordingly.

Before you scale up, use bulk verification to remove invalid or outdated addresses that don't contribute to engagement but increase the volume you’re sending. You can clean your list at scale with bulk email list cleaning, ensuring that only high-intent, valid addresses are processed—reducing strain on your quota limits and improving engagement.

Common Causes of 'Quota Probe * * *' in Mailgun

Mailgun's 'Quota Probe * * *' error appears when your outbound sending exceeds your plan’s daily limits, triggers rate-limiting on shared IPs, or fails to manage volume across recipients. This isn’t a bug—it’s Mailgun signaling you’ve exceeded configured thresholds. You’re sending too fast, too much, or too unevenly. Let’s break down the real reasons.

Volume spikes tied to your sending rate

  • You're sending hundreds or thousands of emails within minutes using a single domain or IP, triggering Mailgun’s per-minute or per-hour rate throttling. Even if the total daily quota isn’t reached, sudden bursts can cause probes.
  • High-volume campaigns without a proper warm-up period on shared IPs commonly trigger this. Shared IPs are pooled across many senders; a sudden spike in one account can affect all others.

Improper enforcement of send limits

  • You’re not enforcing per-recipient or per-hour limits during bulk sends. Sending one email per second may seem safe, but Mailgun has hard limits per IP per minute—exceeding these leads to probes.
  • You’re not monitoring daily send volume relative to your plan’s cap. If you’ve upgraded your plan but still see probes, your actual usage might be close or exceed the new limit due to delayed sync or overlooked campaigns.

Spamhaus and Rspamd both track sending behavior patterns that trigger defensive measures; while they don't enforce Mailgun quotas, they influence how aggressively services like Mailgun rate-limit suspicious traffic. You can review real-time data through Spamhaus or Rspamd to understand how your sending profile appears to systems.

Let’s be clear: quota probes aren’t about being blocked. They’re about being throttled temporarily. The fix isn’t always more credits—it’s smarter sending. You can avoid this by validating your list before sending. Invalid or dormant addresses inflate your effective send rate. Use bulk email list cleaning to reduce noise and ensure only deliverable emails count toward your quota.

How to Fix 'Quota Probe * * *' Without Hitting the Limit

When Mailgun returns a "quota probe * * *" error, it means your outbound volume has triggered rate-limiting behavior, not a hard block. You're near or exceeding daily sending capacity. To stay under the limit, distribute sends across multiple domains or IPs, throttle delivery pacing, monitor sender reputation in real time, and avoid sending entire lists at once. This keeps you within Mailgun’s per-day volume thresholds and prevents temporary throttling.

Core Actions to Prevent Quota Probes

  • Use multiple domains or dedicated IPs for sending to spread volume across Mailgun’s rate-limited systems. This reduces the chance any single endpoint hits its daily cap.
  • Implement send throttling: space out messages over time (e.g., 100 emails every 5 minutes) instead of sending thousands in a single burst. This aligns with industry-standard practices like those outlined in RFC 5321, which governs SMTP delivery timing.
  • Use a sender reputation monitoring tool to track real-time threshold usage. Tools like MxToolbox or Return Path (via their public dashboards) help you see inbound signal quality and adjust volume before a quota probe triggers.
  • Never send your entire list in one batch. Segment your list by region, engagement level, or domain type, and stagger delivery over hours or days. This reduces burst risk and improves inbox placement.

Preventative Data Hygiene Reduces Probes

Many quota probes stem from sending to invalid or high-risk addresses that bounce, inflating your effective send rate. Clean your list before sending. Use a real-time email validation API to filter out non-existent or risky addresses—such as disposable domains, catch-alls, or role accounts—before they consume your quota. For larger lists, perform bulk verification first.

Check your send patterns against Mailgun’s rate limits guide—which defines daily and per-IP volume caps—to understand your safe sending window. Tools like bulk email list cleaning help identify invalid or risky addresses before delivery, reducing bounce rates and protecting your sender reputation.

How Email List Validation Prevents 'Quota Probe * * *' Errors

When Mailgun returns a Quota Probe * * * error, it’s a signal that your outbound volume has triggered rate-limiting or suspicious behavior detection. This happens when you send to too many invalid, role-based, or disposable emails in a short time. Email List Validation stops this by scrubbing your list before sending—filtering out bad addresses, reducing volume, and keeping your sending behavior within safe boundaries.

Preventing Rate-Limit Triggers with Cleaner Lists

You’re not fighting quota issues when you send to a clean list. Every invalid or disposable address you remove lowers your total send count. Fewer requests mean your API calls stay within Mailgun’s rate limits and avoid triggering defensive measures like Quota Probe. A well-filtered list keeps your sending pattern consistent and predictable.

Let’s say you’re sending to 10,000 addresses. If 20% are invalid or role accounts, that’s 2,000 unnecessary requests. With Email List Validation, you remove those at the source—reducing your list to ~8,000 valid targets. That’s a meaningful reduction in load per campaign, which directly lowers the chance of hitting rate-limited thresholds.

Verification Accuracy and Deliverability Health

With a 98.9% accuracy rate, Email List Validation identifies only valid, deliverable addresses. That means fewer bounces, fewer complaints, and better sender reputation—all factors that influence whether Mailgun treats your traffic as low-risk.

Emails to role accounts (like support@ or info@) or disposable domains (like mailinator.com) don’t contribute to engagement. They often trigger automated defenses. By rejecting them before delivery, validation prevents your IP from being flagged for suspicious volume patterns, even if the total count is high.

This isn’t just about removing noise. It’s about protecting your ability to send at scale without crossing behavioral thresholds that Mailgun uses to prevent spam. For example, the SMTP RFC 5321 defines how servers handle high-volume traffic—your sending rate matters as much as the content. A clean list helps you stay within acceptable sending rates over time.

The integration works inline with your current stack. Whether you use Mailgun, SendGrid, or HubSpot, Email List Validation acts as a pre-send gatekeeper. You verify your list in bulk via the bulk verification tool or integrate the real-time API for on-the-fly checks during onboarding.

Use Inbox-Placement Testing to Pre-Test Your Mailgun Campaigns

You can prevent a quota probe in Mailgun by testing your campaign’s delivery behavior with a small sample set using inbox-placement tools. These tools simulate real-world inboxing across major providers like Gmail and Outlook, revealing whether your messages would trigger throttling or filtering under actual sending conditions. Let’s dig into how this works before you send to your full list.

Simulate Real Delivery Behavior Before You Send

Mailgun enforces sending limits based on reputation and behavior, not just volume. Sending to a large list without testing risks triggering a quota probe if your emails are flagged as spammy or low-deliverability. A single high bounce rate or sudden volume spike can set off alarms even if your content is clean.

That’s why you should test your campaign with a sample set—say, 100-500 recipients—before full deployment. Inbox-placement testing lets you see how your message lands in real inboxes across 12 major providers, including Gmail, Outlook, and Yahoo. You’ll know if your sender reputation or message content causes filtering or throttling early, before you hit a quota limit.

How Inbox-Placement Testing Reveals Quota Probe Risks

When you send via Mailgun, the system evaluates sender reputation, bounce rates, engagement, and feedback loops in real time. If a campaign shows low inbox placement or high complaint rates in testing, Mailgun may limit your sending volume—even if you’ve stayed under the hard limits.

By simulating this behavior ahead of time, you identify risks before they impact your deliverability. Email List Validation’s inbox-placement feature, for example, tests your emails across Gmail, Outlook, and others, and returns detailed results showing placement percentage, spam scores, and feedback loop flags.

Use this insight to refine your subject line, from address, or content before going live. You’re not just checking if an email is valid—you’re testing whether it will be trusted. Test your next campaign’s inbox placement and reduce the odds of triggering a quota probe. This is the most reliable way to stay within Mailgun’s sending thresholds without throttling.

For context, industry standards show that even a 5% spam complaint rate can trigger delivery restrictions with major providers. Spamhaus and APWG report that sender reputation impacts deliverability long before volume thresholds are hit.

The Role of List Hygiene in Avoiding Rate-Limiting Errors

Rate-limiting errors like "quota probe" in Mailgun’s outbound API often stem from sending too many messages to poor-quality addresses. When your list contains inactive, role-based, or disposable emails, you’re forced to send more emails to find real users, increasing the risk of triggering throttling. Clean email lists reduce unnecessary sends, helping you stay below rate limits while improving deliverability and sender reputation.

Why Bad Data Drives Rate Limiting

You’re not just sending to people who want your content—you’re sending to placeholders, outdated accounts, and disposable domains that never open messages. These addresses either bounce, get ignored, or trigger spam signals. When Mailgun detects high volumes of these interactions, it throttles outbound traffic as a protective measure. This isn't a failure of your API setup—it’s a sign your list needs cleaning.

For example, role accounts like admin@, marketing@, or sales@ rarely engage. Senders often assume they’re valid, but many are catch-alls or simply ignored. Disposable email domains (like mailinator.com) are frequently used for signups that never convert. Sending to them inflates your volume without adding value, directly increasing the chance of a quota probe.

How List Hygiene Prevents Throttling

By removing inactive, role, and disposable emails before sending, you reduce overall send volume without losing engagement. Fewer total messages spread over time mean a lower chance of crossing throttle thresholds—especially important during high-volume campaigns.

According to industry data from Return Path, list hygiene correlates strongly with inbox placement rates and sender domain reputation. Keeping your list accurate and engaged is an industry-standard practice, not optional. Mailgun’s rate limits are designed to protect the ecosystem, so staying below thresholds requires more than just code—it requires clean data.

With tools like bulk verification, you can identify and purge invalid addresses in bulk. The API version lets you validate addresses at scale in real time, so every send you send is to a known-good email. This reduces bounce rates and protects your sender reputation, which indirectly helps avoid quota probes in the first place.

Let’s be clear: you can’t outsmart rate limits with higher send speed. You can only avoid them through better data. That’s why ongoing list hygiene is not a one-time task—it’s a baseline for reliable outbound delivery.

SMTP Setup and Sending Policies to Avoid 'Quota Probe * * *'

When Mailgun returns a 'Quota Probe * * *' error during outbound sends, it usually means your sending activity triggered rate-limiting or reputation checks due to mismatched sending behavior. To prevent this, ensure your domain’s SPF, DKIM, and DMARC records are correctly set, avoid shared IPs, warm up your sending volume gradually, and monitor delivery events in real time using webhooks. These practices help maintain sender reputation and prevent triggering automated rate-limiting.

Secure Your Domain Configuration

  • Verify SPF aligns with your sending infrastructure; include only authorized sending servers to avoid authentication failures.
  • Enable DKIM signing with a strong key (2048-bit or higher) and ensure it’s correctly published in DNS.
  • Use DMARC with a quarantine or reject policy to protect your domain from spoofing and maintain deliverability trust.
  • Test your setup using tools like MXToolbox or dmarcanalyzer.com to catch misconfigurations early.

Scale Sending Responsibly

  • Use dedicated IPs instead of shared pools to control your sending reputation independently.
  • Warm up new domains or IPs by starting with low volume (e.g., 100–500 emails/day) and increasing gradually over 7–14 days.
  • Monitor bounce rates: consistently high rates (>0.5%) can trigger throttling or blocklists.
  • Set up webhooks to receive real-time delivery status updates directly from Mailgun or your ESP.
  • Use a service like bulk email list cleaning to remove invalid or risky addresses before sending—this reduces bounce rates and improves sender reputation.
  • Integrate with tools like Mailgun, SendGrid, or HubSpot via their webhooks to act on delivery events or failures immediately.
Consistent authentication and gradual volume scaling are industry-standard practices for maintaining sender reputation across providers.

Let’s be honest: even a single misconfigured header or a sudden spike in volume can trigger a 'Quota Probe * * *' message. Avoiding it isn’t about guessing—it’s about proving you're a trusted sender through predictable, secure, and verifiable behavior. Use the right tools to audit your lists and infrastructure, and keep your sending practices transparent and scalable.

Real-World Example: A 10,000-Email Campaign That Triggered 'Quota Probe * * *'

When a marketing team sent 10,000 emails in 30 minutes using a new Mailgun domain, Mailgun’s outbound system flagged 56% of addresses with 'quota probe * * *'—despite the emails being valid. The issue wasn't invalid addresses but a send rate that exceeded Mailgun’s per-IP sending limits. This behavior is normal for outbound email platforms under load; they throttle to prevent abuse and maintain sender reputation. After throttling to 200 emails per minute and validating the list, the campaign delivered successfully.

What ‘Quota Probe * * *’ Really Means

Mailgun uses 'quota probe * * *' as a signal that your sending volume has triggered rate-limiting mechanisms. It doesn’t mean the email address is invalid—it means your sending speed exceeded the allowed threshold for that IP address. New domains, especially, face stricter scrutiny. This is a protective measure, not a rejection. It’s similar to how ISPs and email providers like Gmail or Microsoft use sending rate controls to filter spam.

Industry standards confirm that sudden bursts can trigger defensive actions. According to the Messaging, Malware, and Mobile Anti-Abuse Working Group (Spamhaus), spikes above 100–200 emails per minute often trigger temporary holds even on good senders. Mailgun follows this principle: volume, not content, can be flagged.

How to Fix It: Segmentation and Throttling

Let’s say you’re launching a campaign with 10,000 emails. Don’t send them all at once. Validate your list first—many addresses may not be reachable or may be role-based (like admin@ or sales@), which can hurt deliverability. Use a real-time verification API to clean your list before sending.

After cleaning, segment your list by volume, then send in batches of 200–300 emails per minute. This aligns with Mailgun’s guidelines for new domains. You’ll avoid rate limits, keep your IP reputation intact, and reduce bounce rates. For instance, a prior campaign that sent 10,000 in 30 minutes saw 56% fail. After verification and throttling, the same list delivered with nearly zero errors.

Tools like email list validation services help identify risky addresses and prevent over-sending. For teams managing large campaigns, integrating a reliable verification tool ensures only valid, deliverable addresses are sent. If you're using Mailgun or other ESPs, pre-screening your list is not optional—it’s a best practice to avoid quota probes and maintain sender reputation.

Start with a bulk verification to remove invalid and high-risk addresses: clean your list before sending to prevent abuse alerts and keep your domain safe.

What 'Quota Probe * * *' Is Not

Quota Probe * * * in Mailgun’s outbound API isn’t a sign of invalid syntax, spam content, or permanent failure. It means your sending rate hit a temporary limit during delivery—typically due to a burst in volume or too many requests in a short window. This is a rate-limiting signal, not a technical or content error. It’s not a rejection, and it doesn’t mean the email is bad. Resending after the throttle period ends often works. For context, email providers use similar mechanisms to prevent abuse, as outlined in RFC 5321’s delivery control logic. Let’s break down what it isn’t.

Not a Syntax or Format Issue

  • It does not mean the email address is malformed or wrongly structured. A malformed address would trigger a different error, like Invalid Email Address or Malformed Email.
  • You don’t need to reformat or scrub the address. The issue isn’t with the email itself, but with your sending pattern.
  • Mailgun’s validation stack checks syntax before delivery; Quota Probe * * * appears only after that check passes.

Not a Spam or Content Block

  • Mailgun does not return this message for content that triggers spam filters. Spam issues typically return Spam Detected or similar, not quota probes.
  • This is not a signal about your message body, subject line, or sender reputation. If your content were the problem, you’d see a different error code.
  • Providers like Spamhaus and MxToolbox track spam reputation independently of rate throttling—this isn’t about blacklisting.

Not a Permanent Failure

  • Resending the same message later—often within minutes—is likely to succeed once the rate limit resets.
  • Quota Probe * * * is temporary. It’s a mechanism to protect infrastructure during traffic peaks, not to permanently block sending.
  • If you’re hitting this frequently, consider spacing out sends, using Mailgun’s batch API, or verifying your list for inactive addresses to reduce volume spikes.

For teams managing high-volume outbound sends, understanding this distinction keeps you from overreacting. You’re not sending invalid emails or getting blocked—just hitting a speed bump in the delivery pipeline. If you're using Mailgun or similar services, validating your list upfront can reduce these triggers. Check your list for low engagement or outdated addresses with a real-time email verification tool designed for enterprise-scale cleaning. Clean your list before sending to minimize rate limits and improve reliability.

Conclusion: Build a Proactive Deliverability Strategy

Quota probe errors in Mailgun’s outbound context stem from infrastructure constraints, not individual email validity. They signal that your sending volume or frequency has triggered rate limiting, which means your server is under stress, not your list.

Preventing these errors isn’t about fixing addresses—it’s about smarter sending. By reducing list size and improving send precision through email validation, you lower the likelihood of hitting rate limits in the first place.

  • Use Email List Validation to identify and remove invalid, risky, or disposable addresses before sending.
  • Run inbox placement tests to confirm deliverability across real mail providers.
  • Integrate real-time verification into your workflow to catch issues before they impact delivery.

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 quota probe * * * mean in the Mailgun API?

It means your sending rate has exceeded Mailgun’s daily or per-IP limit. It is not a bounce—your message is blocked before delivery.

Is quota probe * * * a temporary or permanent error?

It is temporary. The error clears when the sending window resets. Resending later may succeed.

Can 'quota probe * * *' be caused by invalid email addresses?

No. The error is triggered by volume, not validity. Valid addresses can be throttled if you send too quickly.

How do I prevent quota probe * * * in Mailgun?

Throttle sends, use multiple sending domains or IPs, and clean your list with Email List Validation to reduce volume.

Does Email List Validation help with quota probe errors?

Yes—by removing invalid, role, and disposable addresses, it reduces list size and prevents sending overload.

Why did Mailgun return quota probe * * * for valid addresses?

Because sending volume exceeded the daily or IP-based limit. Validity doesn’t matter—rate does.

What is the difference between quota probe * * * and a hard bounce?

A hard bounce means the address is invalid. Quota probe means the sending rate is too high—address validity is not the issue.

Can I override quota probe * * * in Mailgun?

No. You cannot override Mailgun’s rate limits. You must adjust your sending pattern or upgrade your plan.

How do I test for quota probe * * * before sending?

Use inbox-placement testing to simulate delivery under real conditions before sending to a full list.

What tools integrate with Email List Validation for Mailgun?

Email List Validation integrates with Mailgun, SendGrid, HubSpot, Klaviyo, and other platforms via API.

Does Email List Validation remove disposable emails?

Yes—its 98.9% accurate verification identifies and flags disposable domains, role accounts, and invalid addresses.

How does list hygiene reduce the risk of quota probe issues?

A cleaner list means fewer emails sent overall, reducing the chance of hitting a sending limit.