Article content and detailed guides remain in English. The selected language applies to controls and quick instructions.

Back to articles

How to Handle Bounced Emails After Extraction

On this page

Why Extracted Lists Produce Bounces

When you extract email addresses from documents, spreadsheets or web pages, the tool collects strings that match its email pattern in the source. It does not check whether those addresses are currently active. Some addresses in older documents will have become invalid since the document was created. Others may have been mistyped when they were originally recorded.

The first time you send to an extracted list, expect some bounces. How you handle them determines whether you maintain a clean list and a healthy sender reputation.

Hard Bounces vs Soft Bounces

Hard bounces

A hard bounce is a permanent delivery failure. The receiving server has rejected the message because the address does not exist, the domain is invalid, or the server has explicitly blocked delivery.

Common hard bounce codes:

  • 550 5.1.1. User unknown. The mailbox does not exist on this server.
  • 550 5.1.2. Domain not found. The domain in the address has no mail servers.
  • 550 5.1.0. Address rejected. A general permanent rejection.
  • 550 5.7.1. Delivery refused by policy. The server has explicitly blocked your message.

Action: Remove hard-bounced addresses from your list immediately. They will never work. Continuing to send to them damages your sender reputation.

Soft bounces

A soft bounce is a temporary delivery failure. The address may be valid, but the message could not be delivered right now.

Common soft bounce codes:

  • 450 4.2.1. Mailbox full. The recipient's inbox has reached its storage limit.
  • 451 4.7.1. Temporary rate limit. The receiving server is throttling your messages.
  • 452 4.5.3. Too many recipients. The server is limiting the number of messages it accepts in a session.

Action: Retry soft-bounced addresses on your next send. If the same address soft bounces on three or more consecutive sends, treat it as stale and remove it.

Bounce Rate and Sender Reputation

Your bounce rate is the percentage of sent messages that bounce. Email service providers (Gmail, Outlook, Yahoo) monitor bounce rates as a signal of list quality. A high bounce rate suggests you are sending to outdated or improperly sourced addresses.

General guidelines from major email providers suggest keeping your hard bounce rate below 2%. A single send with a high bounce rate can trigger throttling or blocking by receiving servers.

For extracted lists, the bounce rate depends on the age and quality of the source material. A list extracted from a current employee directory will have a lower bounce rate than a list extracted from a five-year-old conference attendee spreadsheet.

Steps After the First Send

1. Export your bounce report

Most email service providers (Mailchimp, SendGrid, Amazon SES, and similar platforms) provide bounce reports that list which addresses bounced and the bounce type. Export this report immediately after your first send.

2. Separate hard and soft bounces

Split the bounce report into two lists: hard bounces (5xx codes) and soft bounces (4xx codes). If your sending platform does not categorise them automatically, use the bounce code to determine the type.

3. Remove hard bounces

Remove every hard-bounced address from your mailing list. Do not retry them. Add them to a suppression list so they are excluded from future sends, even if the same address appears in a new extraction.

4. Tag soft bounces for monitoring

Keep soft-bounced addresses on your list but tag them. Monitor whether they deliver on the next send. After three consecutive soft bounces, remove them.

5. Update your source records

If you maintain the original files from which you extracted, note which addresses bounced. This is useful if you re-extract from updated versions of the same source later.

Reducing Bounces Before Sending

Validate extracted addresses

Run your extracted list through an email validation service before sending. Validation services check DNS records, verify the domain has active mail servers, and in some cases ping the mailbox to confirm it exists. This catches many invalid addresses before they bounce.

Email Extractor does not validate addresses. Validation is a separate step.

Consider the source age

The older the source material, the more addresses are likely to have gone stale. See Email list decay explained for details on why addresses become invalid over time.

If you are extracting from files of varying ages, download results as CSV with sources to identify which file each address came from. Prioritise addresses from more recent sources.

Remove obvious issues

Before sending, review the extracted list for addresses that are clearly not deliverable:

  • Addresses with obvious typos (missing TLDs, double dots, invalid characters).
  • Addresses at domains you know are defunct.
  • Disposable email addresses if you are sending to a B2B audience.

Start with a small test send

If you are unsure about the quality of an extracted list, send to a small sample first (10% of the list). If the bounce rate from the test send is above 5%, clean the remaining list before sending to the rest.

Suppression Lists

A suppression list is a permanent record of addresses you should never send to again. It includes:

  • Hard-bounced addresses.
  • Addresses that have opted out (unsubscribed).
  • Addresses that have filed spam complaints.

Before sending to any newly extracted list, check it against your suppression list. Most email service providers maintain suppression lists automatically, but if you are switching platforms or managing lists manually, keep your own copy.

When Bounces Indicate a Bigger Problem

High bounce rate on a fresh extraction

If a large proportion of addresses from a recent source bounce, the source itself may be unreliable. Check whether the original file contained placeholder data, test addresses, or addresses from a decommissioned domain.

Bounces from a previously working list

If addresses that previously delivered start bouncing, the likely cause is list decay. Re-extract from a current version of the source if one is available.

Blocks after a high-bounce send

If a receiving server blocks your messages after a high-bounce send, reduce your sending volume, remove all bounced addresses, and allow time for your sender reputation to recover. See Email sender reputation for recovery steps.

Extract emails

Explore tools

Verify emails

Check address validity before using your list.

ZeroBounce

Email Verification

Verifies email lists and provides tools for monitoring deliverability.

Useful when list cleaning and sender health belong in one workflow.

Explore ZeroBounce (opens in a new tab)