Interpret Exim Bounce Logs to Trace One Failed Email Delivery
Learn how to decode Exim bounce logs to identify and fix one failed email delivery. Use real-time verification to prevent bounces before they happen.
What happens when an email fails to deliver? A real-world breakdown
You send a campaign. The system says “sent.” But no one opened it. You check the list. One email, maybe ten, didn’t get through. You’re left guessing: was it a typo? A filter? A server error?
Deliverability isn’t binary. Emails either land in the inbox, get rejected, or bounce. Each failure leaves a trace—deep in the server logs. For admins using Exim, that trace is in the bounce logs. But reading them isn’t intuitive. The output is dense, technical, and meant for machines.
Without decoding the log entries, you’re blind to the real reason: a typo in the address, a temporary server issue, or a spam filter blocking the sender. Understanding these logs isn’t about guessing—it’s about interpreting the signals in context.
Key takeaways
- Exim bounce logs record the full path of delivery failure, including error codes and timing.
- Understanding log entries like "550 5.1.1 User unknown" or "450 4.7.1 Try again later" separates misconfigured addresses from temporary issues.
- Interpreting Exim logs allows you to distinguish between invalid addresses and server-side failures, directly improving list hygiene and sender reputation.
Why Exim bounce logs matter for list hygiene
You can’t clean a list if you don’t know which emails are failing. Exim bounce logs expose dead addresses, misconfigured domains, and temporary delivery issues—before they hurt your sender reputation. Ignoring them means higher bounce rates, degraded deliverability, and a greater chance of being blacklisted. Proactively reading these logs lets you prune bad data before sending, keeping your list healthy and your inbox placement strong.
The hidden signals in Exim bounce logs
When an email fails to deliver through Exim, the system logs more than just “failed.” It captures the reason: a nonexistent address, a full inbox, a rejected domain, or a temporary server timeout. These details are gold for maintaining list hygiene. You’re not just seeing bounce counts—you’re diagnosing the root cause.
For instance, a hard bounce with a “user unknown” or “domain not found” code means the address is dead. A soft bounce like “550 mailbox full” may indicate a temporary issue, but repeated failures signal a deeper problem. Left unchecked, these keep accumulating and skew your overall bounce rate metrics.
Bounce rates and sender reputation
Mail providers track your bounce rate over time. If yours consistently exceeds 2% (a common threshold), they start treating your messages as spam. Even a single high-volume campaign with unverified emails can trigger flagging or temporary throttling.
According to industry best practice, high bounce rates correlate strongly with poor inbox placement—often to the tune of 30–50% lower delivery. A study by Return Path (now Validity) found mail with bounce rates above 5% had a 70% chance of landing in the junk folder, even with strong content.
Let’s be honest: your list grows by chance. People change jobs, delete accounts, or switch providers. You can’t rely on your sending system to catch all of it. That’s why interpreting Exim logs isn’t just maintenance—it’s prevention. You’re identifying trouble before it happens.
Use logs not as a cleanup after the fact, but as a real-time feedback loop. Schedule regular checks. Export bounce records. Compare them to your customer records. If an email was marked as “invalid” weeks ago, remove it from your active list.
Tools like the bulk verification service at EmailListChecker.io can help validate your entire list in advance, catching issues that Exim logs will later report. By combining proactive verification with reactive log analysis, you create a defense-in-depth approach to deliverability.
The three types of bounces in Exim logs: hard, soft, and transient
When a message fails to deliver, Exim logs assign a status code that tells you exactly why. Hard bounces (5xx codes like 550 5.1.1) mean the address is permanently invalid. Soft bounces (4xx codes like 451 4.4.1) point to temporary issues—server overload, full inbox, or policy blocks. Transient bounces (4xx codes like 421 4.4.2) reflect short-term server congestion, not a flawed email. These distinctions are critical for cleaning lists and improving sender reputation. RFC 5321 defines SMTP status codes, including these common patterns.
Understanding the SMTP status code pattern
SMTP status codes follow a consistent format: the first digit indicates the category of failure. 5xx means permanent failure. 4xx means temporary. 2xx means success. Exim uses these codes in logging to help diagnose delivery issues. A hard bounce like 550 5.1.1 is a clear signal to remove the address—no retry will help. Soft and transient bounces may resolve themselves, but repeated failures degrade sender reputation over time.
Comparing bounce types across Exim logs
| Bounce Type | Common Code Example | Indicates | Recommended Action |
|---|---|---|---|
| Hard Bounce | 550 5.1.1 | Address does not exist, domain invalid, or rejected by policy | Immediately remove from your list. This is permanent. |
| Soft Bounce | 451 4.4.1 | Mailbox full, server temporarily down, or message policy blocked | Wait and retry. If repeated, consider removing the address after 2–3 attempts. |
| Transient Bounce | 421 4.4.2 | Server overload, connection limits reached, or throttling in place | Do not act on the address—this is server-side congestion. Retry later. |
These codes are not just labels—they're a diagnostic map. Misinterpreting a soft bounce as a hard one leads to unnecessary list cleaning. Confusing a transient bounce with a permanent failure wastes send attempts. Use these patterns to route your response: scrub hard bounces, defer soft ones, and ignore transient ones. Over time, this reduces bounces, improves deliverability, and protects sender reputation. For bulk list validation that identifies these signals before sending, verify your entire list at scale with tools designed to flag invalid and risky addresses before delivery.
How to find and read Exim bounce logs on your server
You can interpret Exim bounce logs by locating the main log file at /var/log/exim_mainlog or the reject log at /var/log/exim_rejectlog. Use grep 'Failed to deliver' to isolate delivery failures. Check the recipient email and the error code right after the attempt to diagnose why the email didn't reach its destination.
Step-by-step inspection of Exim logs
- Locate the correct log file — Exim typically writes delivery logs to
/var/log/exim_mainlog. If you’re seeing rejections or immediate bounces, check/var/log/exim_rejectlogfor early-stage failures. - Filter for delivery failures — Run
grep 'Failed to deliver' /var/log/exim_mainlogto extract only lines where an email could not be delivered. This reduces noise. You’ll see timestamps, source, recipient, and status codes. - Identify the recipient and error code — Look for the email address in the output. Immediately after the address, an error code appears — like
550(user unknown),450(temporarily unavailable), or554(rejected by policy). These codes follow specific SMTP standards defined in RFC 5321. - Check the context — Expand the search with
grep '550' /var/log/exim_mainlogto see all failed deliveries due to missing users. Addgrep -B5 -A5 '[email protected]'to view 5 lines before and after a specific address for full context, including sender and headers. - Correlate with sender reputation — If you're seeing consistent
554or550errors for many addresses, consider whether the sender domain or IP has been blacklisted. Use tools like MxToolbox or Spamhaus to check reputation status.
Common error codes and their meaning
| Code | Meaning | Typical cause |
|---|---|---|
| 550 | User unknown | Email address doesn't exist |
| 551 | User not local | Forwarding failure or address not hosted |
| 554 | Rejected (e.g., spam, blacklisted) | Policy, reputation, or content filter |
| 450 | Temporarily unavailable | Greylisting, rate limiting, or mail server issue |
Understanding these codes helps you determine if the issue is a bad address, server-side filtering, or deliverability policy. For example, repeated 550 failures across a list suggest data quality issues — you may want to verify your list before sending.
Proactively checking logs prevents wasted sends, inbox placement drops, and sender reputation damage. Tools like bulk email verification help catch invalid addresses before delivery, reducing bounce rates and keeping your sending domain healthy.
Decode common Exim error codes: what each number truly means
When an email fails in Exim, the error code tells you whether the problem is permanent (5xx) or temporary (4xx), and why. A 550 means the recipient address is invalid or blocked; a 450 means the server is temporarily busy. Retry logic matters—after multiple 4xx attempts, you may get a "Retry timeout" error, signaling the delivery is stuck. Knowing these codes lets you act fast: fix invalid addresses, adjust retry settings, or scrub outdated domains before sending.
Permanent failures: 5xx codes mean the address is broken or blocked
- 550 means the recipient address doesn't exist or the server rejected it outright—common with typoed emails or domains that block all incoming mail.
- 552 indicates the message was too large to accept. Check the recipient’s mail server limits.
- 553 5.1.0 often points to a domain policy rejecting the address, such as a role account (e.g., [email protected]) being disabled.
- 554 usually means the sender’s domain is on a blocklist or the content triggered spam filters.
- When you see a 5xx, don’t retry. This is a dead end—remove the address from your list.
Temporary failures: 4xx codes mean retry may solve it
- 450 means the server is temporarily busy or under load. Wait and retry later—this is often a rate-limiting issue.
- 451 implies a local processing error—like a disk full or a temporary policy misconfiguration. Retry after some time.
- 452 means the server lacks space to accept the message. Retry once the server clears space.
- Multiple 4xx failures with "Retry timeout" indicate the server isn’t responding to retries. This often means the destination host is unreachable or has aggressive throttling.
- These errors require delay or suspension of retries—aggressive retrying worsens sender reputation and can get you blocked.
Understanding these codes helps you avoid wasting bandwidth on failed deliveries. For instance, if you’re sending newsletters and consistently hit 550s, you likely have outdated or invalid addresses. Use a tool like bulk email verification to catch these before they cause a backlog or harm your sender reputation.
For real-time insights, Exim logs follow RFC 5321 standards for SMTP error codes. You can reference the official specification at RFC 5321 for precise definitions. In practice, treating 5xx as final and 4xx as retryable is a proven, scalable pattern used by high-volume senders.
Interpret one failed delivery: a practical example from real logs
You’re troubleshooting a failed email delivery. The log shows: 2024-03-14 10:05:12 1tJZfK-0001aK-1X => [email protected] R=dnslookup T=remote_smtp_hybrid H=mail.company.com [198.51.100.10] SMTP connection closed after sending 550 5.1.1 User unknown. This is a hard bounce: the recipient domain resolved correctly, but the mail server explicitly rejected the address. The user doesn’t exist, was deleted, or the mailbox was disabled. Remove this email immediately—no retries.
What the log tells you, step by step
Let’s break down what happened. The timestamp indicates when the delivery attempt was made. The 1tJZfK-0001aK-1X is a unique message ID used for tracking. The R=dnslookup means the system first verified the domain was reachable via DNS. That’s a positive sign—it wasn’t a typo or a malformed domain.
Next, the T=remote_smtp_hybrid tells us the system attempted delivery through standard SMTP. It connected to mail.company.com at IP 198.51.100.10. So far, so good. Then the server sent back the SMTP code 550 5.1.1 User unknown. This is a standard hard bounce response.
SMTP status code 550 means “permanent failure.” The 5.1.1 subcode specifically means the recipient address does not exist. According to RFC 5321 (the core SMTP specification), this is a definitive rejection. It’s not a temporary issue like a full inbox or rate limiting. The address is invalid or was removed.
Why this matters for your list hygiene
Hard bounces like this hurt your sender reputation. Sending to invalid addresses repeatedly can trigger blacklists and reduce inbox placement for the rest of your list. Services like Exim, Postfix, or Sendmail log these events so you can audit delivery success rates.
Use tools like bulk email verification to catch these issues before you send. These tools test your list at scale and flag invalid addresses—including hard bounces—using the same DNS and SMTP checks your mail server runs.
For real-time verification during signup or onboarding, the email verification API can return results in milliseconds, blocking invalid addresses before they enter your database.
When you see a 550 5.1.1 in logs, trust it. The server isn’t being polite—this is a machine-level rejection. You’re not just losing one email; you’re preventing future deliverability damage. Stay proactive. Clean your list early.
Why real-time verification beats post-mortem log analysis
You can’t fix a failed email delivery after the fact—bounces degrade sender reputation, hurt future inbox placement, and waste send capacity. By the time you analyze Exim bounce logs, the damage is already done. Real-time email verification catches invalid, catch-all, and risky addresses *before* they reach your server, preventing bounces altogether.
Post-mortem is too late
Exim bounce logs tell you what failed—but not why, and not until after the email hit the wire. By then, your sender reputation has taken a hit, and the bad address remains in your list, skewing metrics and harming future deliverability. You're reacting to problems that could have been avoided.
According to RFC 5321, bounce messages are standard, but they’re a symptom, not a solution. Relying on them means accepting failure as routine. It’s like checking an engine after the car has broken down.
Prevention, not detection
Instead of parsing logs after delivery fails, verify emails in advance. Services like Emaillistchecker.io scan lists in bulk, identifying invalid, catch-all, and risky addresses with 98.9% accuracy. This includes detecting disposable domains, malformed formats, and role accounts that commonly bounce. You never send to them at all.
With real-time verification, your bounce rate drops by up to 90% on clean lists. That’s not just fewer errors—it’s stronger sender reputation, better deliverability, and less wasted bandwidth.
Let’s say you’re sending to 10,000 addresses. Without verification, 10-15% might fail. With Emaillistchecker.io’s bulk verification, you identify and remove those before sending. Your campaign lands with fewer setbacks and higher engagement. Clean your list before you send—before you get caught in the log analysis cycle.
How Emaillistchecker.io can prevent Exim bounces before they happen
Instead of sifting through Exim bounce logs to trace a single failed delivery, you can stop those bounces before they occur. Emaillistchecker.io verifies email addresses at scale, catching invalid, disposable, or risky addresses—such as role accounts or known trap domains—before they ever hit your mail server. This reduces hard bounces, protects sender reputation, and improves deliverability. No more digging through logs. No more wasted sends.
Proactive verification stops bounces before they happen
- Run bulk list verification on your entire subscriber list to isolate addresses that will hard bounce—no need to wait for Exim to reject them during send.
- Use the real-time verification API during onboarding or lead capture to validate emails instantly at the point of entry—no log analysis required.
- Integrate directly with platforms like Mailchimp, SendGrid, HubSpot, and Klaviyo to validate emails during sync, so only valid addresses are added to your campaigns.
- Identify and flag high-risk addresses—like
admin@,support@, or disposable domains—before they damage your sender reputation or trigger spam filters. - See a complete breakdown of address health: valid, invalid, catch-all, or risky. Understand the root cause before sending.
Simple, flexible, low-risk start
You can begin today with 100 free verifications—no credit card, no time limit. These credits never expire, so you can test the system at your pace. Once you're ready to scale, you're not locked into any plan. The system works at your speed, whether you're scrubbing a 10K list or validating thousands on the fly.
For insight into how email quality affects deliverability, industry benchmarks show that high bounce rates (over 2%) often lead to inbox filtering or blacklisting—especially with mail servers using Exim (RFC 5321, RFC 5322). You can learn more about server-level email standards at The IETF’s official RFCs.
Discover how bulk verification works: upload your list and see risky addresses flagged in minutes. Or integrate with your stack: sync verification with your current tools and start cleaning at scale. Your list is cleaner, your logs are quieter, and your campaigns perform better.
What you lose by ignoring Exim logs and bounce data
Ignoring Exim bounce logs means you’re flying blind on deliverability: high bounce rates—even from a few invalid addresses—damage sender reputation, trigger spam filters, and reduce inbox placement. You risk being flagged by providers like Gmail or Outlook, which penalize repeat bounces and can silently throttle your sends. This isn’t hypothetical—all email services monitor sender behavior closely, and unverified lists amplify these risks.
Reputation damage starts with the first invalid address
Every bounce, even a soft one, adds friction to your sender reputation. Reputable providers like Google and Microsoft track sustained bounce rates, and consistent spikes signal poor list hygiene. A few invalid emails aren’t harmless—they compound. If your list includes even 1–2% invalid addresses across thousands of sends, you’re exposing your domain to filtering.
Spam traps and non-existent domains silently hurt outreach
Repeated sends to invalid domains or email addresses that no longer exist can trigger spam traps—a common method used by anti-spam organizations to catch negligent senders. These traps don’t bounce; they’re designed to be dormant until you hit them. Once triggered, your domain can be blacklisted or flagged as high-risk. According to Return Path’s inbox placement reports, domains with historical bounces see up to a 15% drop in deliverability across major providers.
Let’s be clear: troubleshooting delivery issues after the fact is a waste of time. You’re chasing symptoms—missing emails in inboxes, low open rates—when the root cause was preventable. Most failures stem from poor list quality, not technical misconfigurations. Tools like bulk email verification catch invalid, outdated, or disposable addresses before you send, reducing bounces and protecting reputation.
Exim logs offer real-time insight into failures, but only when you act on them. Ignoring them means you’re trusting guesswork over data. The cost? Lost campaigns, blocked domains, and damaged sender reputation. The fix? Build verification into your workflow. Use tools that validate addresses at scale—before, not after—your messages fail.
The smarter path: fix the source, don’t just read the logs
Reading Exim bounce logs tells you what failed—but not why, and never before it happened. By the time you see a bounce, the damage is done. The real fix is stopping bad email addresses from ever entering your list. Verify at sign-up, verify before every send, and let logs become obsolete.
Logs are reactive, not preventive
Exim bounce logs show you the fallout of failed deliveries—soft bounces, hard bounces, transient errors. But they don’t prevent them. You're inspecting the wreckage after the crash, not adjusting the course. Relying on logs for deliverability is like checking your car’s engine after a breakdown. It explains the failure, but it doesn’t stop the next one.
Most bounce types—like invalid syntax, non-existent domains, or blocked mailboxes—are known before sending. A well-verified list eliminates these at the source. You don’t need to troubleshoot what you already prevented. This isn’t about faster parsing; it’s about stopping the problem before it starts.
Verification at the point of entry
Let’s say you collect emails during sign-ups. If you don’t scrub them for misspellings, disposable domains, or role accounts (like admin@ or info@), you’re already planting seeds for bounces and spam complaints. A single invalid address can hurt your sender reputation—especially on platforms using real-time feedback loops.
That’s why you verify before storage and again before sending. Use an email verification API to check addresses in real time as they’re added. Tools like EmailListChecker’s API confirm syntax, domain existence, and inbox validity instantly—without slowing down your workflow.
For larger lists, run bulk verification via EmailListChecker’s bulk service to clean outdated or invalid entries. This reduces bounce rates across the board and improves inbox placement over time. According to RFC 5321, mail servers expect only valid recipients; sending to non-existent addresses undermines trust.
When you verify early and often, logs don’t become useless—they become backup records, for rare edge cases. You’re no longer chasing bounces. You’re sending to known-good addresses, every time.
Keep your email list clean: the foundation of deliverability
A clean email list reduces hard bounces, protects your sender reputation, and improves inbox placement. Every invalid address you send to risks your domain’s credibility with inbox providers.
Interpreting Exim bounce logs reveals why a message failed — whether due to a non-existent address, a full inbox, or a temporary server issue. But logging errors doesn’t stop them. Prevention comes from verifying addresses before sending.
Use Emaillistchecker.io to verify, clean, and monitor your list in real time. Catch invalid, disposable, and role-based addresses before they harm your deliverability. Focus your efforts on engagement — not on chasing bounces.
Sources
- The average email bounce rate across all industries is 2.48%, based on combined Mailchimp and Campaign Monitor data covering more than 30 billion emails. — WebFX (Mailchimp & Campaign Monitor data) (2026)
- Mailchimp's platform-wide data puts the average hard bounce rate at just 0.21% and the soft bounce rate at 0.70%, meaning well-maintained lists bounce under 1% in total. — Verified.email (Mailchimp data via Mailerio) (2025)
Keep reading
- Email bounces: codes, causes and prevention (complete guide)
- Define Bounce Rate Limits to Pause Email Campaigns in HubSpot
- Syncing Bounce Data from Mailgun with Email Verification API Output
- Trace a Message That Failed to Deliver by Parsing Bounce Log Data
- Real-Time Email Validation for Mailchimp Bulk Emails to Avoid Bounces
Ready to put this into practice? Emaillistchecker.io verifies emails with 98.9% accuracy — start with 100 free verifications.
Frequently asked questions
What does Exim error code 550 mean?
A 550 error is a hard bounce, indicating the recipient address is invalid, nonexistent, or rejected by the receiving server.
Can a soft bounce cause a permanent delivery failure?
Not by itself, but repeated soft bounces without resolution can damage sender reputation and eventually lead to hard filtering.
How do I identify a hard bounce in Exim logs?
Look for 5xx error codes like 550 (User unknown) or 553 (Recipient address rejected) immediately following the recipient line.
Why does my Exim log show 'Temporary delivery failure'?
This indicates a 4xx error—usually due to a full mailbox, server overload, or rate limiting. It is not a broken address.
Can Exim logs detect spam traps?
Not directly. They show bounces, but not the cause. Spam traps are typically found through list hygiene tools or reputation monitoring.
Is it safe to ignore transient bounces?
Yes, but only if they are isolated. Frequent transient bounces may signal server policy issues or throttling.
How often should I verify my email list?
At least once per quarter, or before major campaigns. For high-volume senders, verify before every send batch.
Does Emaillistchecker.io verify role emails?
Yes. It flags role accounts (e.g., info@, sales@) as risky because they often lack inbox placement or are auto-rejected.
Can Emaillistchecker.io prevent Exim bounces entirely?
No system can guarantee zero bounces. But 98.9% accuracy significantly reduces hard bounces before delivery.
How do I integrate Emaillistchecker.io with SendGrid?
Use the API to verify addresses during onboarding, or sync lists before sending via the SendGrid integration.
What is the difference between a catch-all and a non-existent address?
A catch-all accepts all emails, even invalid ones, and may bounce later. A non-existent address returns immediate 550 errors.
Do disposable email domains show up in Exim logs?
Yes—disposable domains will often return hard or soft bounces, depending on their policy. Emaillistchecker.io identifies them in advance.