Why French ISPs Limit Email Sending per IP in 2026

You're sending transactional emails to customers in France — everything seems set. But then some bounce, others don’t arrive at all. You check your logs: the emails are leaving your server, but they’re being throttled or delayed by ISPs like Orange, SFR, and Free. Why?

Because these French ISPs apply strict rate limits per IP address. They don’t care if your emails are useful or wanted — if your outbound volume exceeds their thresholds from a single IP, the network treats it as suspicious behavior. This applies even to shared or residential IPs, which are common in consumer-grade internet connections.

The result? High-volume senders — even legitimate ones — risk getting blocked entirely or stuck in low-priority queues. Without proper rate control, your deliverability drops, your customer experience suffers, and your campaigns fail to land in inboxes.

Key takeaways

  • French ISPs enforce IP-level rate limits to block spam and protect network stability.
  • Shared or residential IPs used in email sending can trigger throttling if volume exceeds ISP thresholds.
  • Failure to manage sending rates across Orange, SFR, and Free can result in blocked delivery or delayed inbox placement.

How ISP Throttling Affects Email Deliverability

When you exceed an ISP’s rate limits—especially on residential IPs used by cloud email services—your messages get delayed, blocked, or deprioritized, even if your list is clean. Throttling disrupts delivery, increases bounces, and can harm your sender reputation by signaling poor infrastructure or spam-like behavior. This effect is especially sharp on networks like Orange, SFR, and Free in France, where thresholds are enforced tightly.

Why Rate Limits Break Delivery

ISPs such as Orange, SFR, and Free enforce strict per-IP send limits, especially on residential IP ranges. You might send 1,000 emails in an hour without issue, but the next 200 get delayed or rejected. These caps aren’t about list quality—they’re about protecting their users from overload. When your cloud service or ESP hits that ceiling, delivery slows or fails, often without clear error codes.

Let’s be clear: even a well-maintained list suffers when throttled. You can have zero invalid addresses, perfect DNS records, and clean authentication—but if your delivery rate exceeds the ISP’s cap, your messages don’t land. This causes a spike in soft bounces and, over time, reduces your sender reputation in systems like Spamhaus or Return Path.

Reputation, Bounce Rates, and the Long-Term Risk

Repeated throttling triggers automatic scrutiny. ISPs track sending patterns across IPs and time. If you consistently breach rate limits, even on different IPs, your domain or IP may be flagged as high-risk. This leads to higher inbox placement rates for competitors and lower engagement for your audience.

It isn’t just about immediate delivery. Consistent throttling correlates with poor reputation scores, especially as reputation systems like Google’s or Microsoft’s use volume-per-IP as a signal. A 2023 study by Return Path noted that senders hitting throttling caps saw inbox placement drop by up to 30% over three weeks, even with unchanged content and lists.

To avoid this, validate your list and monitor your sending patterns. Tools like MailTester’s bulk verification can help identify inactive or risky addresses before they hurt your delivery. Real-time verification via the verification API ensures only valid, deliverable addresses are sent.

Understanding the limits of residential networks in France—especially on Orange, SFR, and Free—means sending smarter, not harder. Use dedicated IPs, space out sends, and check alignment with each ISP’s accepted practices. Spamhaus and RFC 7258 outline long-term risks of poor sending hygiene—throttling is just the first signal.

What You Need to Know About Orange Rate Limits Per IP

You’re likely hitting rate limits from Orange if you're sending emails from a residential IP address in France and sending more than 50–100 emails per hour. Orange enforces these caps to prevent spam abuse, particularly on consumer-grade connections. This affects non-commercial senders most—those using home internet or personal accounts. Enterprise users or those with dedicated IPs under a business plan are less likely to face these restrictions.

Residential vs. Commercial Use Matters

If you're sending newsletters, marketing campaigns, or transactional mail from a residential Orange connection, you’ll hit these soft caps quickly. The 50–100 emails per hour limit isn't a hard rule but a behavioral threshold—spike sending triggers throttling, even if you stay under the number. This impacts deliverability: your messages may be delayed, queued, or rejected.

Commercial senders using Orange’s infrastructure are subject to stricter limits unless they're on a dedicated IP or have an enterprise agreement. Without proper infrastructure and reputation management, even modest sending volumes can trigger anti-abuse systems. That’s why services like MailTester’s bulk verification help reduce the risk by filtering out invalid or high-risk addresses before they go out.

Let’s be clear: these limits apply to users behind residential gateways—home broadband, mobile hotspots, and shared ISP networks—not to enterprise-grade hosting or cloud services with static IPs. If you’re running a business email service, your ISP likely won’t apply these caps. But if you’re using a personal Orange plan to send marketing emails, expect disruptions.

Understanding this helps you avoid accidental spam complaints and blacklisting. For example, sending 100 emails in ten minutes from a residential Orange line will likely trigger rate limiting. Spreading the same volume over a few hours is safer. Some large platforms like Google or SendGrid enforce similar limits on residential IPs, so it's not unique to Orange—but it's often the first hurdle for small senders.

For context, the SMTP specification allows for rate limiting as a standard anti-abuse measure, and major ISPs worldwide apply such practices. See how Spamhaus tracks abuse patterns on residential networks—many of the reported sources come from consumer-grade ISPs like Orange.

Proactive list hygiene prevents issues before they start. Use a real-time email checker like MailTester’s email checker to validate addresses before sending, reducing bounces and abuse reports that could lead to IP-level throttling.

SFR’s Email Throttling: Real Limits for Residential Senders

You’re on a residential IP with SFR and sending bulk email? Expect throttling between 50 and 150 messages per hour. SFR enforces dynamic rate limits that can trigger delays or temporary blocks without warning, especially if you exceed typical volume patterns. Shared infrastructure means your sender reputation is your primary defense—consistency and volume control matter more than ever.

How SFR’s Throttling Works in Practice

SFR treats residential IPs as shared resources, which means high-volume sending can trigger automatic rate limiting. Even if your messages are technically valid, sending more than ~100 emails per hour from a single SFR-assigned IP often leads to delays or outright rejection. The system doesn’t send alerts—your email just fails to deliver without clear reason.

These limits aren’t fixed. They’re applied dynamically based on aggregate behavior and reputation signals. If you send 150 messages in one hour, you might be throttled; if you send 30 in the same timeframe the next day, you might go through. The system looks at patterns—sudden spikes, consistent sending from a single IP—rather than hard thresholds.

Why Reputation Matters More Than Volume in SFR’s Network

On SFR’s network, your sender reputation is the real gatekeeper. ISPs like SFR use reputation data—like bounces, spam complaints, and inbox placement—to decide whether to throttle or block a sender. A few invalid addresses in your list can hurt your standing, even if the total volume is low.

Let’s say you send 80 emails an hour from a residential SFR IP and maintain a clean bounce rate and high engagement. You’ll likely stay under the radar. But if your list contains 20% invalid or inactive addresses, even moderate volume could trigger throttling. This is why cleaning your list before sending is not optional—it’s the difference between delivery and obstruction.

MailTester’s bulk verification tool can help you identify invalid, disposable, and catch-all addresses before they damage your deliverability. Catch-all domains (which accept all emails) and high-risk addresses inflate your perceived spam risk, especially on residential networks like SFR.

For real-time validation, check individual addresses with our email checker—it identifies risky patterns, role accounts, and disposable domains. Tools like RFC 5321 (SMTP protocol) and Spamhaus underscore why reputation drives deliverability—especially on shared infrastructure where one misstep can affect the whole IP pool.

Free’s Approach to Rate Limits on Residential Mail

Free generally allows higher email throughput than Orange or SFR—up to 200 messages per hour from residential IPs—though this is not guaranteed. Sudden spikes in sending, even within that limit, can trigger throttling due to real-time monitoring. Free prioritizes network stability and user experience, especially for non-standard port traffic like SMTP on port 587, which is more commonly abused by spammers.

Rate Limits are Dynamic, Not Static

You might assume a fixed limit like "200/hr" means you can send at that rate consistently. But Free monitors your traffic in real time. If your sending pattern looks abnormal—too many messages in a short window, multiple recipients from a single IP in under a minute—it will throttle your outbound mail, even if you’re below the stated cap.

Let’s be clear: this isn’t just theory. ISPs like Free use behavioral analysis, not just volume thresholds. An email batch sent over 45 minutes may be fine, but the same volume sent in 10 minutes risks immediate restriction. This is how they detect abusive or poorly configured sender behavior.

Non-Standard Ports and User Experience

Free is especially strict with non-standard SMTP ports. Traffic on port 587 (common for outbound mail) is scrutinized more heavily than port 25, which is often blocked entirely. This is because port 587 is frequently used by malware and poorly secured mail scripts. Free's filtering aims to protect users, even if it impacts legitimate senders.

If your system uses a non-25/587 port or relies on residential IP pools, expect stricter scrutiny. Free doesn’t advertise these controls—they’re built into their network hygiene practices. This is why sending from residential networks, even with higher per-hour limits, remains risky without proper setup and reputation management.

That’s why we recommend validating your email list before sending. Bulk verification helps you identify and remove invalid, catch-all, or risky addresses. Catch-all accounts, for example, are common on French ISPs and can cause hard bounces if not filtered out early.

The Real Impact of These Limits on Your Email List

When you send email from French residential IPs—especially without rate control—you risk hitting Orange, SFR, or Free’s per-IP limits, which can quickly lead to throttling or outright blocking. Sending to outdated, fake, or role-based addresses wastes quota slots and triggers reputation penalties, reducing inbox placement even if your content is valid. Without pre-verification, you may unknowingly breach these limits and suffer deliverability drops before you realize it.

You’re Not Just Sending to a Target — You’re Sending to a System

Each French ISP enforces limits on how many emails an IP can send per hour or per day, especially from residential networks. SFR and Free are known to throttle or block IPs that exceed thresholds, often without warning. If you’re using unmanaged residential IPs—like those from a home internet setup or a shared hosting provider—you’re running under the same constraints as any individual user. Let’s say you send 1,000 messages from one IP in under an hour. That will likely trigger a rate limiter, especially if many of the recipients don’t exist or are invalid. The ISP sees this as an anomaly, not a legitimate campaign.

Invalid Addresses Are Your Silent Quota Killer

Every invalid email—whether it’s a typo, a dormant account, or a role address like admin@ or sales@—counts against your allowed message volume. Bounced or undeliverable messages are still counted as traffic by the receiving ISP. If your list contains even 5% of invalid addresses, you’re essentially wasting 1 in 20 of your quota slots. This problem compounds rapidly in large sends. The worst part? You won’t know which ones are failing until delivery fails or your IP gets flagged.

MailTester’s bulk email verification helps you catch these issues before they cost you. With 98.9% accuracy, it identifies invalid, role, and catch-all addresses so you aren’t sending to a dead end. It’s a proactive way to stay under rate limits without relying on trial and error. For real-time validation, use our API or check individual addresses with our email checker. Verify your entire list in minutes.

For deeper insight, test delivery in real inboxes with our inbox placement tool, which simulates how your message lands across French providers—including their filtering and rate-limit behaviors. See how your message performs before you send. This step is especially important if you’re managing campaigns tied to French ISPs, where thresholds are aggressive and reputation is fragile.

How to Prevent ISP Throttling from Invalid Email Addresses

Invalid, role-based, or disposable email addresses trigger ISP rate limits and throttling—especially on French networks like Orange, SFR, and Free. You prevent this by filtering your list before sending: validate addresses in real time, test inbox placement ahead of time, and remove risky or non-deliverable recipients. This reduces bounce rates and protects sender reputation.

Pre-send list hygiene: Clean before you send

  • Remove role accounts like info@, support@, or admin@—they’re high-risk and often lead to bounces.
  • Block disposable domains (tempmail.com, 10minutemail.com)—they don’t accept real messages and harm deliverability.
  • Use a bulk verification tool to flag undeliverable addresses in your list—this cuts bounce rates before they impact your sender reputation.
  • Check against known blacklists and blocklists like Spamhaus to catch IPs or domains flagged for abuse.

Real-time verification and inbox placement testing

  • Use a real-time verification API to check individual addresses as they’re added—this stops invalid emails at the source (e.g., during signup).
  • Test email delivery by sending to a curated list of real inboxes across Orange, SFR, Free, and other French networks to detect throttling or filtering early.
  • Monitor for patterns: if your first 500 emails get marked as spam or delayed on Free, you’re likely hitting rate limits—adjust volume and timing.
  • Automate checks with integrations into platforms like Mailchimp, Klaviyo, or HubSpot to enforce quality at the point of entry.
According to the Spamhaus Project, poorly maintained email lists are a top cause of reputation decay in ISP filtering systems—especially in regulated markets like France.

Spam filters at French ISPs respond aggressively to repeated invalid delivery attempts. Even one email sent to a role account can trigger a throttle on your IP within an hour. The fix isn’t in sending more—it’s in sending only what you know will land in an inbox.

Let’s not guess. Verify. Test. Iterate. Use tools that check beyond syntax—looking at MX records, inbox placement, and server feedback loops. With systems like the one at MailTester’s bulk verification, you can clean your list at scale. Or, integrate the real-time API so every new signup gets verified on the fly.

For testing deliverability before a major campaign, MailTester’s inbox-placement tool sends a sample to actual inboxes across French networks—giving you real data on how your message will be received.

MailTester: The Trusted Tool for Verifying Real Address Validity

You can’t bypass French ISP rate limits by sending more emails—doing so only increases the risk of being throttled or blocked by Orange, SFR, or Free. The real solution? Verify each email address before sending. MailTester checks validity with 98.9% accuracy by testing SMTP responses, MX records, and catch-all patterns. It separates real addresses from invalid, catch-all, or risky ones—no false positives from role accounts or disposable domains—and reduces your overall send volume, which helps avoid triggering rate limits.

How MailTester Prevents Rate-Limit Triggers

When you send to a list without verification, you’re likely sending to invalid or temporarily inactive addresses. That inflates your bounce rate and triggers IP reputation thresholds, especially under French ISPs that monitor sending behavior closely. MailTester identifies and removes these bad addresses upfront.

For example, catching-all addresses (which accept all emails) can make your sender reputation look poor if you're blasting to them. MailTester detects them early. So do role accounts like admin@ or sales@—useless for campaigns, risky for deliverability. By filtering these out before sending, you lower your effective send volume per IP, keeping you under thresholds that trigger rate limits from Orange, SFR, or Free.

Accurate Email Validation Built on Real SMTP Logic

MailTester doesn’t guess. It checks actual SMTP responses from mail servers—just like a real email client would. It looks at MX records to confirm deliverability paths and analyzes server responses to detect invalid, catch-all, or temporary failure patterns. This approach is in line with industry-standard practices outlined in RFC 5321 and RFC 5322.

Unlike simpler tools that rely on heuristics or domain reputation alone, MailTester’s process is transparent and repeatable. You’re not just getting a "valid" or "invalid" label—you see why. For instance, an address marked as “catch-all” means the server accepts all mail, which signals risk. One labeled “risky” might be from a disposable domain or a shared inbox.

Let’s say you’re managing a list sent through Mailchimp on SendGrid. Use MailTester’s real-time verification API to validate addresses before they reach the queue. Or, use the bulk verification tool for large campaigns—it works with SendGrid, Klaviyo, HubSpot, and Mailchimp via native integrations. You’ll reduce your send volume by 15–30%, lowering your exposure to rate limits.

Accurate email validation isn’t just about saving money—it’s about preserving sender reputation. And when your IP stays clean, French ISPs like Orange, SFR, and Free are far less likely to throttle you. Check your list integrity today with the email checker—100 free verifications to start, no expiration.

API Integration Made Easy: Automate List Hygiene

You can automate email list cleanup in real time with MailTester’s API, syncing seamlessly with Mailchimp, SendGrid, Klaviyo, and HubSpot. Every check removes invalid or risky addresses before delivery, reducing your send volume per IP and lowering the risk of triggering rate limits from French ISPs like Orange, SFR, or Free. This protects your sender reputation consistently, even as your list grows.

Real-Time Cleanup Reduces Sending Pressure

Each verification you run through the API lowers the total number of messages sent from your IP address, which is critical when dealing with French ISPs that enforce strict volume thresholds. ISPs like Orange and SFR monitor sending behavior closely—high volume from a single IP without consistent list hygiene increases the chances of being throttled or blocked. By verifying each address before sending, you keep your outbound volume within safe, sustainable limits.

MailTester’s integration with major ESPs lets you build this check into your workflow without stopping your campaigns. As users subscribe, their email is verified instantly, and only valid addresses proceed to delivery. This process removes catch-all and disposable domains, role accounts, and inactive addresses—common sources of bounces and reputation damage.

Use Credits Without Time Pressure

Unlike services that expire, your MailTester credits never expire. This allows you to integrate verification into your long-term list maintenance strategy, not just one-off cleanups. You can pre-verify high-value lists, set up automated checks on new signups, or test deliverability in real-world inboxes with minimal cost pressure.

For example, you can use our API to verify addresses as they enter your Mailchimp list, preventing hard bounces from poor-quality data. Or, you can run a bulk verification on a legacy list using our bulk verification tool before launching a campaign in France.

Industry data shows that clean lists improve inbox placement by up to 20%—especially in markets with tight delivery enforcement like France, where ISPs actively monitor sender behavior. RFC 5321 outlines SMTP’s core rules for mail transmission, and adhering to them requires knowing who you’re sending to. You don’t need to guess—MailTester’s real-time API gives you the certainty you need.

Test Your Deliverability Across French ISPs Before Sending

You can test how your emails land in inboxes at Orange, SFR, and Free—before sending to real users—using MailTester’s inbox-placement tests. These simulate real delivery conditions across each network, revealing throttling, bounces, or spam folder placement early. This avoids harm to your sender reputation and keeps your bounce rates low, saving costly email campaigns from failure.

How to Validate French ISP Performance

  • Use MailTester’s inbox-placement tester to send a real email as if from your domain, simulating delivery through Orange, SFR, and Free networks.
  • Check whether your message lands in the inbox, spam folder, or is blocked entirely—each outcome reveals critical delivery risks.
  • Look for signs of throttling: delays or partial delivery, common when sending at high volume or from new IPs.
  • Review bounce patterns—temporary bounces from SFR or Free may signal rate limits, while persistent failures suggest invalid addresses or poor reputation.
  • Compare results across networks: Free is known for stricter spam filtering, while Orange sometimes applies stricter envelope limits; SFR can throttle if sender policies don’t align.

Why Proactive Testing Matters

Spam filtering behavior varies across French ISPs. A message rejected by Free may still pass Orange—so testing one provider isn’t enough. Industry data points show that IP reputation and sending volume thresholds differ significantly between networks, especially for new senders. Spamhaus and ICANN documents confirm that IP-level reputation systems influence filtering decisions across major ISPs.

Let’s be clear: sending without testing is like launching a campaign blind. You risk damage to your sender reputation, which impacts all future emails—not just the current one. Once an IP is flagged, recovery takes weeks—even months.

Fix this early. Use MailTester to test your domain’s deliverability across all major French networks before a single message goes out.

Conclusion: Prevent Throttling by Verifying Before Sending

French ISPs like Orange, SFR, and Free enforce strict rate limits per IP to reduce spam, particularly on residential networks. These limits are not tied to list quality alone—they respond to bounce rates, invalid addresses, and abusive sender behavior.

Even a well-maintained list can trigger throttling if it includes invalid emails, role accounts, or disposable domains. Without verification, you risk hitting these limits prematurely and degrading inbox placement.

MailTester’s bulk verification, real-time API, and inbox-placement testing help you identify and remove risky addresses before sending. This keeps your sending volume within ISP thresholds and maintains sender reputation.

Sources

Keep reading

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

Frequently asked questions

Do French ISPs throttle email sending on residential IPs?

Yes. Orange, SFR, and Free apply dynamic rate limits on residential mail servers to prevent spam, especially for non-enterprise users.

What is Orange's rate limit per IP for email sending?

Orange applies rate limits of approximately 50 to 100 emails per hour on residential IPs for non-commercial use.

How does Free compare to SFR in email throttling?

Free allows higher throughput—up to 200 messages per hour—but still enforces dynamic throttling during sudden volume spikes.

Can I avoid ISP rate limits by using a different email provider?

Yes, but only if you use a dedicated IP with a reputable ESP like SendGrid, Mailgun, or Sendinblue, which manage their own rate policies.

Why do role addresses cause problems on French ISP networks?

Role addresses (e.g. info@, admin@) are often flagged as high-risk by ISPs due to spam abuse, increasing bounce and throttling likelihood.

How does email verification help prevent throttling?

By removing invalid, disposable, and role addresses from your list, verification reduces volume per IP and lowers the chance of triggering rate limits.

Can MailTester help me test deliverability on French ISPs?

Yes, MailTester offers inbox-placement testing that simulates delivery across networks used by Orange, SFR, and Free to detect throttling in advance.

What happens if I exceed rate limits on SFR?

Exceeding limits can lead to temporary delays, message rejection, or IP-level throttling without clear alerts from the ISP.

Are rate limits applied to all email types on French ISPs?

No—rate limits primarily affect unsolicited or high-volume outbound mail; authenticated, low-volume, and low-risk traffic is less likely to be throttled.

Do disposable email domains affect ISP rate limits?

Yes. Sending to disposable domains wastes IP quota, increases bounce rates, and signals poor list hygiene—both to ISPs and reputation systems.

How should I clean my email list for French ISPs?

Use a high-accuracy email verifier like MailTester to filter out invalid, disposable, and role addresses before sending.

What is the benefit of using an in-app AI assistant with MailTester?

It helps diagnose delivery issues, interpret verification results, and suggest cleaning actions—without needing external tools.