Skip to content
Orange (orange.fr and wanadoo.fr)

OFR_109: too many messages per connection

Your server sent more messages over one SMTP connection than Orange accepts. Orange recommends at most 100 messages per connection.

Orange
Provider
Sources checked
Author

At a glance

Code
OFR_109
Who has to act
The sender. The fix is on the sending side: your domain, your server or your list.

What it means

Code 109 is the per-connection counterpart of code 104. Your server kept one SMTP connection open and sent too many messages through it. Orange asks you to reduce the number of messages per connection and gives 100 as the recommended value, alongside two simultaneous connections per IP and 100 recipients per message. Orange also says different limits may apply depending on your reputation, so a sender with a weak reputation may meet this below 100.

Common causes

  • Your server is set to reuse a connection for an unlimited number of messages.
  • A bulk send pushes hundreds of messages through one session.
  • A low reputation at Orange brings a lower limit than the recommended one.

How to fix it

  1. 01Cap your server at 100 messages per connection toward Orange, or lower.
  2. 02Make sure a rejection mid-session leads to a new connection and a retry.
  3. 03If the problem continues after the fix, use the Orange contact form linked from its postmaster page and choose the option "Un problème d'envoi d'emails vers les adresses Orange ou Wanadoo (deliverability issue)".

Sources

What this page rests on, checked on 20 Oct 2026. The explanation is ours; the reply text is the server's.

  1. OFR_104Too many simultaneous connections.Your server opened too many connections to Orange at the same time. Orange recommends no more than two simultaneous connections per sending IP address.Orange
  2. 451Transaction limit per session reached.Your server sent more messages over one SMTP session than GMX allows, currently 100, so GMX deferred the next one. Close the session and open a new one.GMX, WEB.DETemporary

All 20 Orange codesEvery code in the wikiPaste your own bounce

Beat · paid monitoring

A heartbeat for your email.

Beat runs every check on this site on a schedule: 41 checks, 33 blacklists and real inbox placement. The moment something breaks, it tells you what broke, why it matters, and the exact fix.

example.comWatching
  • SPFpass
  • DKIMpass
  • DMARCp=none
  • Blacklists0 of 33

Illustrative. Your domain, every few hours.

Also from us:Pulse: your own sending infrastructureConsulting: $65/hr, no retainer