Barracuda rate control: 421 too many connections

What it means

Barracuda’s gateways include a Rate Control feature that counts how many connections each sending IP makes in a half hour period. When an IP goes over the threshold the recipient’s admin configured, the gateway defers further connection attempts from that IP until the next half hour, and each deferred message gets a temporary 4xx reply telling your server to retry later. Barracuda does not publish the exact reply text, which varies by product version, so the example is typical wording.

Because it is a 4xx, nothing is lost. Your server keeps the messages queued and retries, and the deferral lifts once the half hour window resets. The problem appears when you send a large batch to one organization, such as a school or company newsletter, or when many users share one outbound IP.

This is a volume limit, not a judgement about your reputation. It differs from the BRBL block, which is permanent while you stay listed.

Likely causes

• A bulk send to many addresses at one Barracuda-protected organization in a short time.
• Your MTA opens a new connection for every message instead of reusing connections.
• Many users or applications sharing one NAT IP, all sending to the same recipient domain.
• A forwarding loop or auto-reply storm that generates repeated deliveries.

Checks that apply

• MX Lookup Shows whether the recipient’s MX belongs to a Barracuda cloud service, confirming where the limit is enforced.
• MailFlow Monitor Tracks delivery of test messages over time, showing when deferrals clear after you slow your send rate.

FAQ

Will my mail eventually be delivered?

Yes, as long as your server keeps retrying within its queue lifetime and the sending rate drops below the limit.

Can I get exempted from Barracuda rate control?

Only the recipient’s admin can do that, by adding your IP to the Rate Control Exemption or allow list in their Barracuda settings.