Every mail campaign produces bounces — messages that cannot be delivered. Managing bounces well maintains sender reputation, keeps lists clean, and reveals operational issues early. This article explains bounce types, SMTP response codes, processing strategies and the UK-specific considerations for bounce management.
A bounce is a message generated by a mail server indicating that a previous message could not be delivered. The bounce arrives back at the envelope sender address (the MAIL FROM specified when the message was originally sent), not the From: header.
Bounces come in two main forms:
Both require processing by the original sender to maintain list hygiene.
Permanent failures. The message cannot be delivered and will never be deliverable to this recipient. Common causes:
Action: suppress immediately. Never retry. Continued attempts to hard-bounced addresses hurt reputation significantly.
Temporary failures. The message might be deliverable later. Common causes:
Action: retry queue automatically handles most cases. Sender mail servers typically retry for 4-72 hours before giving up. Persistent soft bounces should be treated as hard bounces after a threshold (e.g. 5+ soft bounces over 30 days).
Response codes in bounces follow RFC 5321 and RFC 3463 (Enhanced Status Codes):
| Code | Class | Meaning |
|---|---|---|
| 2xx | Success | Message accepted |
| 4xx | Soft failure | Temporary; retry |
| 5xx | Hard failure | Permanent; do not retry |
| Code | Meaning |
|---|---|
| 421 | Service not available, closing connection |
| 450 | Mailbox unavailable (e.g. busy) |
| 451 | Local error in processing |
| 452 | Insufficient storage |
| 550 | Mailbox unavailable (e.g. not found) |
| 551 | User not local; please try forwarding |
| 552 | Exceeded storage allocation |
| 553 | Mailbox name not allowed |
| 554 | Transaction failed |
Three-part codes in the form X.Y.Z:
Examples:
5.1.1 — Bad destination mailbox address (user not found).5.7.1 — Delivery not authorised (rejected by policy).4.2.2 — Mailbox full.5.7.9 — DMARC authentication failure.Major receivers often categorise bounces:
Standard workflow for a UK mail sender:
For UK SMEs sending moderate volumes, bounce processing tools:
bouncehammer (open-source) process NDRs and maintain suppression lists.pflogsumm, custom scripts integrating bounces with list management.For typical UK businesses using a marketing platform, the platform handles bounce processing; your role is to monitor the dashboards and respond to anomalies.
Bounce rates directly affect sender reputation:
Gmail's published bulk-sender requirements include a stated bounce rate threshold. Microsoft and Yahoo similar. Keep bounces low through active list management.
VERP is a technique where each recipient receives a uniquely-tagged envelope sender. Bounces come back with the tag, uniquely identifying which recipient bounced:
MAIL FROM:<bounce+user%[email protected]>
RCPT TO:<[email protected]>When this message bounces, the bounce is addressed to bounce+user%[email protected], and the envelope tag tells you exactly which recipient bounced — no need to parse the bounce body.
VERP simplifies bounce processing at scale. Most UK mailing list and ESP software supports it natively.
For UK businesses reviewing bounce data, meaningful patterns to look for:
Rapid increase in bounce rate after a previously-stable period. Causes:
Spike localised to a single receiver (e.g. all Gmail bounces, no Outlook). Causes:
Same addresses soft-bouncing week after week. Probably full mailboxes or inactive accounts. Treat as hard after a threshold; suppress.
Recently migrated mail providers? Expect bounce patterns to shift during the transition. Stabilise before drawing conclusions.
Q: How quickly should I suppress hard-bounced addresses?
A: Immediately. First hard bounce — permanent suppression. Delayed suppression risks repeated attempts to dead addresses; receivers interpret as poor list hygiene.
Q: What about temporary-looking bounces that turn out permanent?
A: Soft bounces that recur for 5+ attempts over 7-14 days should be treated as hard. Tracking tools automate this escalation.
Q: Do out-of-office replies count as bounces?
A: No. They are auto-replies, not non-delivery reports. Filter separately — standard mail clients tag them.
Q: Should I remove addresses after a single soft bounce?
A: No. Soft bounces are temporary. Retry through normal queuing; suppress only on recurrence.
Q: Can I re-send to hard-bounced addresses after waiting?
A: No. Hard bounce means permanent failure. Waiting does not change the recipient's mailbox existence. Continued attempts harm reputation.
Q: How do I distinguish between "mailbox full" and "mailbox does not exist"?
A: Enhanced status codes: 4.2.2 for full (soft), 5.1.1 for not-found (hard). Parse both the numeric code and the text response.
Q: Why do some bounces have no clear recipient?
A: Occasionally a receiver generates an NDR with ambiguous details. Check the Received headers, envelope sender tag (VERP), or message-id to identify the original. Lack of detail often indicates a misconfigured receiver; bounce usefulness is limited.
Q: Can a high bounce rate get me blocklisted?
A: Indirectly. High bounces = poor list = spam-trap risk. Spam trap hits lead to Spamhaus listing. Bounces are a leading indicator of blocklist risk.
Q: Do I need to track bounces for transactional mail?
A: Yes. Transactional mail bounces may indicate dead customer accounts — relevant for account management. Tracking prevents repeated attempts to dead addresses.
Q: What is a typical bounce rate for a well-maintained UK business mailing list?
A: Under 1%. High engagement, regularly-cleaned lists produce very low bounce rates. Rates over 2-3% suggest list issues.
Q: Can bounces reveal recipient email system changes?
A: Yes. If an entire batch of @firm.co.uk recipients bounce at once, the firm likely migrated mail providers. Investigate and may need to wait for DNS stabilisation.
Q: How do bounces interact with GDPR data-retention obligations?
A: Bounced addresses in suppression lists are processed for the legitimate interest of preventing further unwanted mail. No specific retention period; data stays as long as needed for suppression purposes.
Q: Are there UK-specific bounce-handling regulations?
A: No. Standard industry practice applies. UK GDPR allows suppression processing as legitimate interest.
Q: Can I use bounce data for A/B testing list hygiene practices?
A: Yes. Run different list-cleaning approaches and measure bounce rates; informs best practice for your audience.
Q: Do bounce handling practices differ for transactional vs marketing mail?
A: Slightly. Transactional bounces may trigger customer-service follow-up (ask customer to update email). Marketing bounces just suppress.
Q: What tools automate bounce processing for smaller UK senders?
A: ESPs (Mailchimp, Sendinblue, Klaviyo) include built-in handling. Open-source bouncehammer. Custom scripts integrated with Postfix or Exim. Choose based on volume and in-house capability.
Q: How do I handle bounces for mail sent via managed platforms?
A: The platform handles automatically. Monitor via their dashboard. Export suppression list if you migrate to another platform.
Q: Can bounces reveal that my email domain has a PTR/authentication problem?
A: Yes. Persistent 5.7.1 or 5.7.26 bounces across multiple recipients suggests your domain is failing authentication or is blocked. Investigate SPF/DKIM/DMARC.
Q: What is the difference between a bounce and a deferral?
A: Deferral is a soft-bounce at the sender's queue — message not yet delivered or permanently failed, queued for retry. Bounce is the eventual NDR after either retry exhaustion or immediate permanent rejection.
Q: How quickly should bounce processing happen after receiving?
A: Real-time or near-real-time. Automated processing runs within minutes of receiving the NDR. Delay allows continued sending to bad addresses.
Q: Can my bounce rate affect other senders using the same IP?
A: Yes. Shared-IP reputation is averaged. Your high bounces affect neighbours and vice versa. One of the arguments for dedicated IPs at moderate volume.
Q: Are bounces during DMARC rollout different from normal bounces?
A: Yes. DMARC-failure bounces (5.7.9) indicate authentication issues, not recipient issues. Different remediation — fix SPF/DKIM, not list.
Q: Do UK hosted mail platforms provide bounce-rate dashboards?
A: Most do. SmartXHosting, Microsoft 365, Google Workspace all expose bounce statistics via their admin interfaces. Use for routine monitoring.
Q: How does bounce processing affect email deliverability over time?
A: Directly. Clean list (low bounces) builds reputation; high-bounce list damages it. Active bounce suppression is a key reputation maintenance practice.
Q: Can I use bounce rates to evaluate different audience segments?
A: Yes. Segments with higher bounces may indicate poor lead source quality, aging subscribers, or segment-specific delivery issues. Useful marketing signal.
Q: What is the SMTP 554 response code typically associated with?
A: Generic "transaction failed". Often paired with enhanced code explaining — 5.7.1 (policy rejection), 5.7.9 (DMARC fail), 5.7.26 (authentication required). Read both for diagnosis.
Q: Should my UK business archive bounce reports for audit purposes?
A: Optional. For operational purposes, rolling 90-day retention is sufficient. For regulated sectors, align with data retention policy.
Q: Are bounce reports protected under UK GDPR?
A: They contain email addresses (personal data). Processing for deliverability purposes is legitimate interest. Standard privacy handling applies.
Q: Can bounces impact other authentication mechanisms indirectly?
A: Yes. High bounces damage reputation; low reputation increases likelihood of receivers penalising authenticated mail. Indirect but real.
Q: Do transactional UK services (Stripe, Xero notifications) handle their own bounces?
A: Yes. Each service maintains its own bounce handling, typically invisible to you as a customer. Your domain reputation benefits from their professional handling.
Q: What is the difference between VERP and standard bounce-return addresses?
A: Standard uses a single bounce address for all recipients; parsing required to determine which recipient bounced. VERP encodes the recipient in the return address; no parsing needed. VERP scales better.
Q: Can bounces be suppressed at the mail server level?
A: Yes. Some configurations discard NDRs entirely (e.g. to prevent backscatter). More common is forwarding all bounces to a dedicated processing mailbox, not discarding.
Q: What is backscatter and how does it relate to bounces?
A: Backscatter is NDRs sent to forged sender addresses. Spammer sends mail with your domain as forged sender; receiver bounces; the bounce arrives at you even though you did not send the original. DMARC p=reject largely eliminates this.
Q: Should a UK business publish a bounce-handling policy publicly?
A: Not typically. Internal documentation of bounce thresholds, suppression practice is sufficient. No public-facing requirement.
Q: Can bounce reports be forwarded to external SIEM or log aggregation?
A: Yes. Many UK businesses feed bounce data into Splunk, Sumo Logic, Elastic, or similar for unified logging. Provides correlation with other IT events.
Q: How does bounce management differ for one-to-one business correspondence vs marketing campaigns?
A: One-to-one: if a customer's bounce occurs, someone should follow up (ask for updated address). Marketing: automated suppression, no follow-up. Different workflows.
Q: Are bounce rates affected by the time of day mail is sent?
A: Minimally. Response times vary but success rates are essentially time-independent. Bounce rates reflect address validity, not timing.
Q: Does bounce data help plan UK-specific marketing campaigns?
A: Indirectly. Low-bounce segments have healthy engagement potential. High-bounce segments need cleaning before campaigning. Informs segmentation.
Q: How do bounce responses interact with GDPR "right to erasure" requests?
A: If a recipient requests deletion of their data, remove from all lists and suppressions. Subsequent bounces (you should not be sending anyway) do not create new data. Handle erasure completely.
Q: Can bounce data inform whether I should change email infrastructure?
A: Yes. Persistently high bounces despite clean lists suggest infrastructure issues (authentication, reputation, blocking). May indicate migration to better-managed infrastructure.
Q: Is VERP complicated to set up for a small UK business?
A: Most ESPs and marketing platforms configure VERP automatically. Manual setup on Postfix/Exim requires configuration but is well-documented. Small UK businesses usually gain VERP for free via their platform.
Q: Are there any UK NCSC or ICO guidelines specifically on bounce management?
A: Not specifically. General data-protection and deliverability best practices apply. No UK-specific bounce regulation.
Q: What bounce handling support does a typical UK managed platform offer?
A: Automatic suppression, dashboard metrics, API access to suppression lists, export for migration. Check with your specific provider for feature set.
Q: Is there a best practice for reviewing bounce trends at board level?
A: For businesses where email is mission-critical (e.g. UK e-commerce, SaaS), bounce rate and deliverability are board-relevant operational metrics. Monthly review alongside broader marketing metrics is typical.
Q: Can bounce processing help identify spam sent from a compromised account on my domain?
A: Yes. Sudden high volumes of bounces from a particular user account suggest compromise. Account abuses often trigger high bounce rates quickly as spam hits bad addresses. Alert on user-level anomalies.
Q: Are there any legal obligations for UK businesses around bounce data handling?
A: No specific obligations beyond general UK GDPR. The incidental email address data in bounces is covered under standard privacy practices.
Q: Does bounce rate affect my sender reputation score at Google Postmaster Tools?
A: Indirectly. High bounces correlate with poor list hygiene which correlates with poor engagement which hurts reputation. Explicit bounce-rate score is not shown but impact is visible in the overall reputation category.
Q: Can I disable bounce handling entirely if I use a cloud ESP?
A: Not recommended. Even with an ESP, some bounce data flows back to you (returned to envelope sender). Handle or explicitly forward to the ESP for consistent processing.
Q: What bounce-related metrics matter most for UK sender reputation?
A: Hard bounce rate (target < 2%), soft bounce rate (target < 5%), total bounce rate (aggregate). Monitor per-campaign, per-receiver, over time.