Why is Orange.fr throttling my legitimate emails and how can I resolve it?
Matthew Whittaker
Co-founder & CTO, Suped
Published 8 Jun 2025
Updated 28 May 2026
8 min read
Summarize with
Orange.fr throttles legitimate email when its local reputation systems see risk that is specific to Orange and Wanadoo, even when Gmail, Microsoft, Yahoo, and other mailbox providers are accepting the same traffic. The usual causes are high complaint signals, too many invalid recipients, rapid connection patterns, sudden volume changes, authentication mismatches, blocklist (blacklist) listings, or a brand reputation problem tied to another stream using the same visible domain.
The resolution is not one magic form submission. I start by capturing the exact SMTP response, slowing only Orange and Wanadoo traffic, checking SPF, DKIM, and DMARC domain matching, suppressing weak recipients, reviewing complaint-prone streams, checking IP and domain blocklists, then contacting Orange with evidence once the sender has already fixed the obvious causes. Orange's Orange postmaster page is the official place to check current SMTP guidance and error-code meanings.
Why Orange throttles otherwise good mail
Orange and Wanadoo do not have to agree with the reputation score you see at other mailbox providers. A sender can look healthy elsewhere and still hit Orange-specific rate limits because Orange weighs its own complaint feedback, recipient quality, delivery history, authentication, and policy rules. If only Orange.fr and Wanadoo.fr are deferring messages, treat it as an Orange-local issue first, not a global deliverability collapse.
The strongest clue is the SMTP response. A temporary 4xx deferral means Orange is asking you to retry later. A permanent 5xx rejection means the message, sender, domain, or IP failed a policy check. Do not average all French providers together. Free.fr, SFR, La Poste, and Orange have different filtering paths, so mixing them hides the useful signal.
Common Orange-style SMTP responsestext
451 4.7.1 Too many connections, try again later 421 4.7.0 Temporarily deferred due to reputation 550 5.7.1 Message rejected as suspected spam 550 5.7.26 Sender domain failed DMARC policy 554 5.7.1 IP listed on a public blocklist
Do not treat other inbox success as proof
A clean result at Gmail or Microsoft is useful, but it does not prove Orange has the same view of your mail. Orange throttling should be diagnosed with Orange-specific bounce logs, recipient engagement, complaint history, and authentication results.
|
|
|
|---|---|---|
4xx | Temporary rate limit | Slow retries |
5xx | Policy rejection | Fix cause |
RBL | Blocklist hit | Check listings |
DMARC | Domain mismatch | Match domains |
Use the exact code before changing DNS, volume, or content.
Start with the fastest diagnosis
Before changing infrastructure, send a fresh test email through the exact production path that Orange is throttling. Use the same envelope sender, return-path domain, DKIM selector, content family, and unsubscribe headers. A synthetic message from a different system gives you a clean-looking result that does not explain the failing traffic.
Use Suped's email tester to inspect a real message for authentication, DNS, content, and header issues. That gives you a sender-side baseline before you compare Orange-specific deferrals against the same message path.
Email tester
Send a real email to this address. Suped opens the report when the test is ready.
?/43tests passed
Preparing test address...
The goal is to separate four different problems that often look identical in a dashboard: a message-level rejection, an IP reputation issue, a domain reputation issue, and a send-rate issue. Each one has a different fix.
- Bounce evidence: Capture the full SMTP response, remote host, timestamp, sending IP, envelope sender, and message category.
- Provider split: Break Orange.fr and Wanadoo.fr out from other French mailbox providers so the trend is not diluted.
- Header check: Confirm SPF pass, DKIM pass, DMARC pass, return-path domain, visible From domain, and DKIM signing domain.
- Complaint review: Compare recent complaint rates for price alerts, lead capture, reactivation, and partner traffic separately.
- List quality: Suppress users with repeated deferrals, recent hard bounces, long inactivity, and no clear consent trail.
Screenshot-style view of the Orange Postmaster guidance website.
Match Orange's acceptance rules
Orange publishes sender rules that are unusually specific compared with many mailbox providers. Their guidance includes limits on concurrent connections, messages per connection, recipients per message, DNS hygiene, reverse DNS, and authentication. If you hit throttling, verify the mechanical limits before assuming the content has a problem.
Orange has also tightened complaint expectations in recent guidance. The internal Orange deliverability update explains why senders should treat Orange complaint rates as a primary delivery signal, not a secondary metric.
Orange complaint-rate triage
Use this as an operational view when deciding whether to keep, slow, or pause a stream.
Healthy
Below 0.3%
Mail can keep normal cadence while other signals are reviewed.
Review
0.3% to 0.59%
Segment the stream, reduce riskier cohorts, and inspect acquisition source.
Stop and fix
0.6% or higher
Pause weak cohorts and send only recent, consented, engaged recipients.
Use Orange-specific throttles
- Connections: Keep Orange and Wanadoo concurrency lower than your global default while reputation recovers.
- Retries: Use patient retry intervals instead of hammering a deferred queue every few minutes.
- Cohorts: Send recent clickers and account-event mail before low-engagement promotional mail.
Example Orange throttling profileyaml
orange.fr: max_connections_per_ip: 2 max_messages_per_connection: 100 max_recipients_per_message: 100 retry_backoff: "15m, 30m, 60m, 120m" wanadoo.fr: max_connections_per_ip: 2 max_messages_per_connection: 100 max_recipients_per_message: 100 retry_backoff: "15m, 30m, 60m, 120m"
Fix the sending pattern first
When throttling is already happening, the fastest way to make it worse is to keep sending every segment at the same cadence. Orange sees more retries, more queued mail, and more users marking delayed or unexpected messages as unwanted. Slow the traffic, then choose the cleanest mail to continue.
Pause or reduce
- Cold cohorts: Stop sending to recipients with no opens, clicks, purchases, or logins in the recent window.
- Lead generation: Separate partner-acquired and co-registration traffic from owned opt-in mail.
- Bulk retries: Prevent deferred queues from retrying in tight loops against Orange MX hosts.
Keep sending
- Transactional mail: Continue receipts, password resets, security alerts, and requested account notifications.
- Recent engagement: Prioritize users who clicked, purchased, logged in, or requested alerts recently.
- Stable streams: Keep streams with low complaints, low unknown users, and consistent volume history.
This is also the point where brand-level reputation matters. If the same visible domain is used for clean price alerts and aggressive acquisition mail elsewhere, Orange can throttle the brand broadly. Separate mail streams by purpose, make consent traceable, and keep the visible From domain tied to the user's expectation.
Audit authentication and domain identity
Authentication problems do not always cause immediate rejection. Sometimes they reduce trust enough that a sender gets deferred instead. Check the message exactly as Orange receives it, including SPF result, DKIM result, DMARC result, reverse DNS, HELO name, envelope sender, visible From domain, and DKIM signing domain.
Suped's domain health checker is useful here because it checks DMARC, SPF, DKIM, DNS, and common domain setup issues in one pass. For ongoing operations, Suped's DMARC monitoring shows which sources are authenticated, which are failing, and which ones need a DNS or sending-platform fix.
DMARC record detail view showing SPF, DKIM, DMARC, rDNS diagnostics, and DNS records
A safe DMARC rollout starts with visibility before enforcement. If Orange is throttling, do not jump straight to a stricter policy without knowing every legitimate source. Use reporting to find every sender, fix failures, then stage the policy upward.
Visibility-first DMARC recorddns
_dmarc.example.com. 3600 IN TXT ( "v=DMARC1; p=none; rua=mailto:dmarc@example.com; " "ruf=mailto:dmarc@example.com; fo=1; adkim=s; aspf=s" )
Where Suped fits
Suped is strongest when the issue crosses authentication, DNS, blocklists, and operational alerts. It brings DMARC, SPF, DKIM monitoring, hosted SPF, hosted DMARC, hosted MTA-STS, SPF flattening, blocklist monitoring, and real-time alerts into one workflow instead of forcing teams to reconcile separate reports by hand.
Check blocklists and reputation
Orange error responses can point to public RBL or reputation listings. A blocklist (blacklist) hit does not always mean every provider rejects the mail, but it gives Orange a reason to slow or block the stream while other signals are reviewed.
Check both IP and domain reputation, especially when the same brand sends mail across multiple vendors or dedicated IPs. Suped's blocklist monitoring helps teams catch listings early and see which domains or IPs need action.
Blocklist checker
Check your domain or IP against 144 blocklists.
Spamhaus
0Spam
Cisco
NoSolicitado
URIBL
abuse.ro
ALPHANET
Anonmails
Ascams
BLOCKEDSERVERS
Calivent Networks
EFnet
JustSpam
Kempt.net
NordSpam
RV-SOFT Technology
Scientific Spam
Spamikaze
SpamRATS
SPFBL
Suomispam
System 5 Hosting
Team Cymru
Validity
www.blocklist.de Fail2Ban-Reporting Service
ZapBL
2stepback.dk
Fayntic Services
ORB UK
technoirc.org
TechTheftSpamhaus0SpamCiscoNoSolicitadoURIBLabuse.roALPHANETAnonmailsAscamsBLOCKEDSERVERSCalivent NetworksEFnetJustSpamKempt.netNordSpamRV-SOFT TechnologyScientific SpamSpamikazeSpamRATSSPFBLSuomispamSystem 5 HostingTeam CymruValiditywww.blocklist.de Fail2Ban-Reporting ServiceZapBL2stepback.dkFayntic ServicesORB UKtechnoirc.orgTechTheftSpamhaus0SpamCiscoNoSolicitadoURIBLabuse.roALPHANETAnonmailsAscamsBLOCKEDSERVERSCalivent NetworksEFnetJustSpamKempt.netNordSpamRV-SOFT TechnologyScientific SpamSpamikazeSpamRATSSPFBLSuomispamSystem 5 HostingTeam CymruValiditywww.blocklist.de Fail2Ban-Reporting ServiceZapBL2stepback.dkFayntic ServicesORB UKtechnoirc.orgTechTheftSpamhaus0SpamCiscoNoSolicitadoURIBLabuse.roALPHANETAnonmailsAscamsBLOCKEDSERVERSCalivent NetworksEFnetJustSpamKempt.netNordSpamRV-SOFT TechnologyScientific SpamSpamikazeSpamRATSSPFBLSuomispamSystem 5 HostingTeam CymruValiditywww.blocklist.de Fail2Ban-Reporting ServiceZapBL2stepback.dkFayntic ServicesORB UKtechnoirc.orgTechTheftSpamhaus0SpamCiscoNoSolicitadoURIBLabuse.roALPHANETAnonmailsAscamsBLOCKEDSERVERSCalivent NetworksEFnetJustSpamKempt.netNordSpamRV-SOFT TechnologyScientific SpamSpamikazeSpamRATSSPFBLSuomispamSystem 5 HostingTeam CymruValiditywww.blocklist.de Fail2Ban-Reporting ServiceZapBL2stepback.dkFayntic ServicesORB UKtechnoirc.orgTechTheftWhen a listing exists, do not request delisting before fixing the cause. Remove bad acquisition sources, stop mail to unknown users, reduce complaint-heavy campaigns, and document the remediation. A delisting request without operational change gives Orange little reason to trust the next retry.
Triage order for Orange throttling
Start with the signals that explain throttling fastest, then move into deeper remediation.
SMTP responses
30%Complaint rate
25%Authentication
20%Recipient quality
15%Blocklists
10%Contact Orange with useful evidence
Contact Orange after you have slowed the stream, checked authentication, cleaned weak recipients, and gathered representative logs. The practical contact path is abuse@orange.fr or the current contact route listed on the postmaster page. English is acceptable for a clear technical report, but a vague complaint about throttling gets a weak response.
- Identity: State the sending brand, visible From domains, envelope domains, DKIM domains, and sending IPs.
- Evidence: Include exact SMTP responses, timestamps with timezone, queue IDs, and a small set of sample message IDs.
- Controls: Explain current rate limits, retry backoff, recipient suppression rules, and complaint handling.
- Remediation: List the fixes already made, including stream pauses, list cleanup, authentication repairs, and delisting work.
- Request: Ask whether the domain, IP, or message stream has a specific reputation or policy issue.
Short contact templatetext
Subject: Orange.fr throttling review request for example.com Hello Orange postmaster team, We are seeing Orange.fr and Wanadoo.fr deferrals for legitimate price-alert mail from example.com. Sending IPs: 192.0.2.10, 192.0.2.11 Visible From domain: example.com Envelope domain: bounce.example.com DKIM domain: example.com Sample SMTP responses: 2026-05-28 09:14 UTC, 451 4.7.1 temporary deferral 2026-05-28 09:22 UTC, 421 4.7.0 reputation deferral Actions taken: - Reduced Orange concurrency to 2 connections per IP - Paused inactive recipients and partner-acquired cohorts - Confirmed SPF, DKIM, and DMARC pass on production mail - Checked IP and domain blocklist status Can you confirm whether this is an IP, domain, rate, or content issue? Regards, Postmaster team
If the brand has obvious spam or uncontrolled lead-generation traffic, do not expect Orange to explain every filter decision. Fix the sender first. Orange is more likely to review a case when the message stream is clearly requested, technically authenticated, and already operating under conservative limits.
Views from the trenches
Best practices
Separate Orange and Wanadoo metrics before changing global throttles or sender policy.
Contact Orange only after capturing SMTP logs, timestamps, IPs, domains, and fixes.
Review brand-level acquisition mail when clean streams are throttled at Orange only.
Common pitfalls
Treating Gmail or Microsoft success as proof that Orange reputation is also healthy.
Retrying deferred Orange mail too aggressively and turning throttling into pressure.
Asking for escalation before suppressing weak recipients and complaint-heavy cohorts.
Expert tips
Group Orange and Wanadoo together, but keep Free, SFR, and La Poste in separate views.
Use a short French or English technical report with exact errors and remediation steps.
Look for hidden lead-generation traffic using the same brand domain before escalating.
Marketer from Email Geeks says Orange-only throttling should be separated from Free, SFR, and La Poste because shared French-provider reporting hides the cause.
2022-03-21 - Email Geeks
Marketer from Email Geeks says Orange can react to brand-level reputation when lead-generation traffic elsewhere uses the same visible identity.
2022-03-21 - Email Geeks
The practical resolution path
The answer is direct: Orange.fr throttles legitimate email when Orange's local view of risk is worse than your global reputation view. Fix it by slowing Orange-specific delivery, proving authentication, removing complaint and unknown-user risk, checking blocklist (blacklist) status, and escalating with exact evidence only after those controls are in place.
For most teams, Suped is the best overall DMARC platform for this workflow because it connects the signals that matter: DMARC reports, SPF and DKIM checks, hosted SPF, hosted DMARC, hosted MTA-STS, SPF flattening, real-time alerts, blocklist monitoring, and multi-domain management for MSPs. The practical benefit is that an Orange incident becomes a traceable workflow instead of a scattered set of DNS checks, bounce exports, and manual notes.
