Prevent bounces

A hard bounce comes from an address that does not exist: it will happen again on every send, and the address must leave the database. A soft bounce comes from a passing obstacle, a full mailbox or a server deferring. Both can be prevented, but not in the same way.

Hard bounce and soft bounce A message leaves for the receiving server. It can come back with a permanent refusal, code 550, in which case the address must be removed, or with a temporary refusal, codes 450 and 451, in which case it must be tried again later. send server 550, closed 450, later
A permanent refusal closes the path, a temporary refusal leaves it open. The shape of the line carries the difference, the colour only repeats it.

What a bounce is

A bounce is the return of a message that the receiving server did not deliver. It is hard when the mailbox does not exist or refuses mail, soft when delivery fails for a passing reason. Both can be prevented, but not in the same way.

Hard bounce, soft bounce, deferral: the trade has its own vocabulary, and it is used loosely. We tie each term, every time, to the technical signal that produces it: a trade term that points to no measurement only serves to sound clever.

Each term, its signal, what to do

Here is the full table. The middle column says what the receiving server actually replied, the right hand column says what to do about it. No term in this list is a marketing word: each one matches a case that the engine tells apart and returns in its response.

The 7 predictable bounce cases, their signal and their status.
TermActual signalStatusWhat to do
Hard bounceThe receiving server refuses the mailbox with a permanent refusal code, the 550 family.invalidRemove the address from the database. A new send will bounce in the same way.
Soft bounce, mailbox fullThe server recognises the mailbox but announces that it is full.riskyKeep the address and try again later. The mailbox exists, it cannot receive right now.
Soft bounce, deferralThe server replies with a temporary refusal, codes 450 and 451, and asks to come back later.unknownDraw no conclusion. A second attempt, later on, most often gets a firm answer.
Soft bounce, server unreachableNo server on the domain answers, or the exchange is cut off before the reply.unknownDraw no conclusion about the address: the fault lies with the server, not the mailbox.
Domain with no mail serviceThe domain declares no server in charge of receiving its mail.invalidRemove the address. No message can be delivered, whatever the mailbox name.
Disposable addressThe domain is listed in the database of temporary mailbox domains.riskyLeave out of recurring sends. The address works today, it will bounce soon.
Domain that accepts everythingThe server also accepts an address drawn at random on this domain.unknownHandle separately, according to the use. The address is flagged as such, and this status is never charged.

Two courses of action, not one

A hard bounce is handled upstream, by removing the address before sending. A soft bounce is handled downstream, by trying again later. Confusing the two loses valid contacts, or keeps dead addresses that damage the sender's reputation.

The most costly mistake is to treat both families the same way. Purging everything that bounced once loses perfectly valid contacts, whose mailbox was simply full that day. Purging nothing lets dead addresses pile up, and a high bounce rate damages the sender's reputation with receiving servers.

Read what the unknown status means

Clean your lists directly in Brevo and your other tools

A clean list, a well configured domain

Validation prevents the bounces caused by the address: missing mailbox, domain with no mail service, temporary address. These are hard bounces, the ones that damage a sender's reputation, and they are dealt with before the first send.

For every message to reach its destination, a well authenticated sending domain complements a clean list. To check yours, submit an address on your sending domain: YesWeCheck reads its declarations, mail server, sending authorisation, anti spoofing policy, and rates them at a glance.

Check the configuration of a mail domain

Frequently asked questions

What is the difference between a hard bounce and a soft bounce?
A hard bounce signals that the mailbox does not exist or refuses mail: it will happen again on every send, and the address must leave the database. A soft bounce signals a passing obstacle, a full mailbox or a server deferring: the address is still good, and the send is tried again later.
Which bounces does address validation prevent?
Validation prevents the bounces caused by the address: missing mailbox, domain with no mail service, temporary address. These are hard bounces, the ones that damage a sender's reputation, and they are dealt with before the first send.
Why remove addresses that hard bounce?
A hard bounce is handled upstream, by removing the address before sending. A soft bounce is handled downstream, by trying again later. Confusing the two loses valid contacts, or keeps dead addresses that damage the sender's reputation.
How can the bounces of a file be estimated before sending?
The audit mode of batch processing produces a quality report on the whole file without charging a credit: it estimates the deliverability of the list and works out the cost of full processing before it is launched.

Going further

On an existing database, batch processing answers the question in a single pass: how many addresses would bounce, and for what reason. Audit mode gives the estimate without using a single credit, so you know what the file is worth before deciding to clean it.

Content updated on 7 September 2026.