Verify Email Deliverability When Mailgun Shows 5xx

Why Your Email Is Marked as 'Sent' in HubSpot but Blocked by Mailgun

You sent a campaign. HubSpot says it went out. Mailgun reports a 5xx error—your message was rejected at the receiving server level. No bounce, no delivery failure, just a silent block. You’re left wondering: if it was sent, why didn’t it arrive?

This gap exposes a blind spot in most email workflows: your ESP tracks the SMTP handshake as success, but Mailgun detects real-time server-level denials. The difference isn’t in your code—it’s in your list. Invalid addresses slip through basic validation, causing backend rejections even when the email looks fine on paper.

How to verify email deliverability when Mailgun reports 5xx but HubSpot shows sent? It starts with understanding why the two systems disagree—and how to fix the root cause before every campaign stalls.

Key takeaways

HubSpot records successful SMTP handshakes; Mailgun detects real-time server rejections, leading to mismatched status reports.
5xx errors from Mailgun indicate the recipient server actively rejected your message—often due to invalid, unverifiable, or blacklisted email addresses.
Pre-sending list validation with tools that check for syntax, domain existence, and inbox placement is the only way to catch issues before they damage sender reputation.

How to Verify Email Deliverability When Mailgun Reports 5xx but HubSpot Shows Sent

When Mailgun returns a 5xx error but HubSpot reports your message as "sent," the issue isn’t in your send pipeline—it’s in the final delivery stage. You’re not getting bounces; your emails are being rejected after SMTP handshake, often by servers that don’t respond to verification attempts. The solution: validate email addresses before sending to catch issues SMTP alone can’t detect. Real-time email verification checks beyond syntax—catching role accounts, graylisted domains, and catch-alls that fail in production.

Why SMTP Isn’t Enough—Even When It “Says Yes”

SMTP success doesn’t mean inbox placement. A 250 response from an MX server confirms receipt, but not delivery. The final step—the actual delivery to the user’s inbox—can fail silently. This is especially common with greylisting, where the server delays acceptance until a retry arrives, or with spam filters that drop messages post-handshake. Your email might be accepted by the server, then quarantined or discarded later.

Mailgun’s 5xx errors signal server-side failures—rejection during or after the connection. But HubSpot’s "sent" status only reflects that the message was handed off to the mail server. The disconnect happens in the gap between handoff and final delivery. This mismatch is why you need pre-send verification: you’re not fixing a failed send, you’re preventing it.

What Real-Time Verification Catches That SMTP Misses

SMTP validation only checks if an address exists at a domain. It doesn’t know if the address is a role account (e.g., [email protected]), if the domain uses greylisting, or whether the mailbox is full. These are all real roadblocks to delivery but won’t trigger a 5xx error—only a silent failure later. Catch-alls—domains that accept all emails, regardless of validity—also falsely pass syntax checks and SMTP verification, leading to high bounce rates and poor sender reputation.

Real-time email verification services use advanced checks: they validate the mailbox’s acceptability, analyze domain policies (like DMARC), and test for greylisting behavior. This catches the 8–12% of addresses that pass SMTP but never make it to the inbox. According to RFC 5321, SMTP delivery is never guaranteed; it only confirms the server is open to receive.

For teams using HubSpot, Mailgun, or SendGrid together, pre-verification is the only way to resolve the disconnect. You’re not just fixing bounces—you’re improving inbox placement and sender reputation. You can start with 100 free verifications to test the impact on your campaign performance. Verify your list in real time and reduce 5xx errors before they occur—at the source.

What 5xx Errors Mean and Why They Matter for Email Deliverability

SMTP 5xx errors mean your email was rejected by the recipient’s server—either permanently or temporarily. These are not delivery failures due to your mail server; they’re final rejections from the target inbox. If Mailgun reports 5xx but HubSpot shows “sent,” you’re dealing with a server-level refusal, not a routing issue. This signals that the email address is invalid, the domain blocks you, or the server is actively filtering your message.

What 5xx Codes Actually Mean

Common 5xx responses include 550 (mailbox not found), 551 (user not local), and 554 (rejected due to spam filter). A 550 means the address doesn’t exist at all. A 551 suggests the account is hosted elsewhere, and a 554 often indicates spam policies triggered by volume, content, or sender reputation. These are not transient; they’re definitive. You can’t “retry” a 550 or 554—your email will never reach that inbox.

When these errors appear consistently across multiple sends, the issue isn’t your email content or infrastructure. It’s the list. You’re sending to outdated addresses, invalid domains, or mail servers that block bulk senders altogether. This isn’t just about bounces—it’s about reputation. Sending to high-risk addresses can trigger filters on major platforms, leading to your domain being blocked over time.

Why This Matters for Deliverability

Each 5xx error is a data point about your sender health. According to the Internet Society’s Internet Society, persistent SMTP-level rejections are a primary factor in domain reputation degradation. Even if your messages appear to send in HubSpot, they’re not making it beyond the gateway if the server sends a 5xx. This leads to poor inbox placement, higher spam scores, and potential blacklisting.

Let’s be clear: a “sent” status in a marketing platform doesn’t equal delivery. It just means your API or SMTP client handed the message off successfully. The final verdict comes from the recipient’s server. If it responds with a 5xx, your email is dead on arrival.

The fix isn’t to tweak your headers or resend. It’s to clean your list before every send. Use real-time email verification to flag invalid, catch-all, or high-risk addresses before you send. For bulk lists, run a full validation check to remove 5xx candidates in advance.

You can test this directly: use our bulk email list cleaning tool to scan your list and highlight addresses that would trigger 550, 551, or 554 responses. That way, you only send to addresses confirmed deliverable—even if HubSpot says “sent.”

Why HubSpot Shows 'Sent' When Mailgun Blocks the Message

You're seeing 'Sent' in HubSpot while Mailgun returns a 5xx error because HubSpot tracks the initial SMTP handshake—accepting the message into its queue—as success. Mailgun, however, may reject the message later due to delivery issues like poor sender reputation, temporary blacklisting, or invalid recipient domains. This mismatch means HubSpot logs success, but the email never leaves the server. Without real-time verification, you’re trusting tools that report progress without proof of delivery.

The SMTP Handshake Isn’t Delivery

When you send an email through HubSpot, the system sends the message to the outgoing mail server (like Mailgun) and waits for a positive response—typically a 250 code—indicating the server accepted the message. That’s enough for HubSpot to mark it as “sent.” But acceptance doesn’t equal delivery. The message can still be rejected moments later due to greylisting, a blocked IP, or a nonexistent inbox.

Mailgun’s 5xx status codes—like 550 (user unknown) or 554 (message rejected)—appear only after the initial handshake, meaning HubSpot has already moved on. You’ll see “sent” everywhere, but the email never reaches a real mailbox.

Why This Creates Dead Campaigns

This gap between reporting and actual delivery is why some campaigns look healthy in HubSpot but fail to convert. If your list contains invalid emails, catch-all addresses, or disposable domains, they’ll pass the initial handshake but fail later. Without validation, you’re sending to ghost addresses—the server says yes, but the user never sees it.

Industry-standard tools like MxToolbox or Spamhaus confirm that false positives in email routing are common when only handshake status is monitored. According to the RFC 5321 specification, the 250 response means “transaction successful,” not that the message was delivered to the recipient. You need more than status codes. You need inbox placement testing and list cleansing.

To avoid this, verify your list in real time before sending. Tools like Email List Validation can catch invalid domains, disposable emails, and high-risk addresses before they ever hit your ESP. With a 98.9% accuracy rate and instant results, you get a clean, deliverable list—no false positives, no wasted send credits.

Test deliverability before you send. See where your messages land—inbox, spam, or bounce. Use inbox placement testing to confirm real inboxes before every campaign. You’re not just logging success—you’re proving delivery.

The Real-Time Verification Process for High-Confidence Deliverability

If Mailgun reports 5xx errors but HubSpot says your message was sent, the issue isn’t always your content or configuration—it’s likely a list with invalid or unreachable emails. The only way to know for sure is to verify each address in real time. This process checks for SMTP errors, catch-alls, role accounts, and disposable domains before you send, so you only target deliverable inbox addresses.

Import your list into Email List Validation—no cleanup needed. The tool automatically detects and removes duplicates, identifies disposable domains, and flags role accounts like support@ or admin@ that rarely receive mail.
Run a bulk verification across 15+ criteria, including live SMTP, MX record validation, and DNS checks. This detects issues like temporary server errors (like 5xx), blocked domains, and invalid mailbox syntax—before your sender reputation is damaged.
Review each verified email's verdict. You’ll see status indicators: valid (safe to send), invalid (undeliverable), catch-all (accepts all emails, not a real user), risky (low engagement, high bounce risk), or disposable (temporary address).
Filter out all non-valid addresses. Sending only to emails with a valid status ensures your campaign reaches real inboxes. This drastically reduces bounces, protects your sender reputation, and improves inbox placement.
Use inbox-placement testing to send a real message to each valid address and confirm it lands in the primary inbox, not spam. This is the gold standard—because it simulates actual delivery conditions across real mail servers.

The 5 steps described in “The Real-Time Verification Process for High-Confidence Deli…”, in order.

Why This Process Works When Tools Disagree

Mailgun’s 5xx errors don’t always mean the email is invalid—they could be due to temporary server issues or greylisting. HubSpot shows "sent" because it succeeded at the API level, but that doesn’t mean the message reached a real inbox. Real-time verification cuts through this ambiguity using active checks.

How It Fits Into Your Workflow

You can integrate Email List Validation with your existing tools—Mailchimp, SendGrid, HubSpot—via our pre-built integrations. Or use the real-time API for automatic verification during signup. For larger lists, start with bulk list cleaning. The 98.9% accuracy rate comes from validating against live infrastructure, not just patterns.

“Email deliverability isn’t about sending more—it’s about sending only to addresses that can actually receive.”

According to RFC 6210, sender reputation is heavily influenced by bounce rates. Every invalid or risky address you send to weakens that reputation. This process ensures you never risk your domain's trust with unverified recipients.

How Catch-All Domains and Role Accounts Break Deliverability

When Mailgun reports 5xx errors but HubSpot shows emails as sent, the issue often lies with catch-all domains or role accounts. These addresses accept all messages—even invalid ones—leading to hard bounces that hurt sender reputation. Role accounts like sales@ or support@ rarely have actual inbox space and are frequently flagged by spam filters. You can avoid this by validating your list before sending.

Catch-All Domains Mask Invalid Emails

Catch-all domains are configured to accept any email address, even if it doesn’t exist. This means Mailgun may deliver your message, but the email is never actually received—it’s treated as a hard bounce. These fake deliveries inflate your bounce rate, trigger spam traps, and degrade your sender reputation over time. According to the Messaging, Malware, and Mobile Anti-Abuse Working Group (M3AAWG), catch-all practices are a known source of email abuse and are often associated with poor deliverability.

Role Accounts Are Not Real Inboxes

Role accounts like info@, admin@, or help@ aren’t tied to individual users. They’re often monitored by teams, auto-responders, or never checked at all. Spam filters recognize patterns in role account usage—especially when they’re in large volumes or lack replies—and label them as low-value or high-risk. Even if the email appears to send, it won’t get opened, and repeated sends to these addresses signal poor list hygiene to mailbox providers.

Using Email List Validation helps by identifying both catch-all domains and role accounts before you send. Our tool checks each address against live SMTP servers and analyzes patterns that suggest a risk. Valid emails pass through. Catch-all domains and suspicious role accounts are flagged as "risky" or "invalid," so you can clean them out. This reduces bounces, improves inbox placement, and protects your sender reputation.

Let’s say you’re sending to a list with 3,000 addresses. A single catch-all can absorb 100 emails and return no feedback. Over time, dozens of these can trigger blacklist warnings. With verification, you’ll see exactly which addresses are problematic before your campaign runs. This level of insight is critical when Mailgun logs 5xx codes but HubSpot still marks the send as successful—because one system sees delivery, the other sees a delivery that never lands.

Use our bulk email list cleaning tool to scan your full list and remove unreliable addresses. You’ll catch these hidden issues before they damage your deliverability.

The Hidden Cost of Sending to Invalid Emails

You’re sending emails through Mailgun, getting 5xx errors, but HubSpot shows them as "sent." That disconnect means you’re likely transmitting to invalid addresses. Each of those undeliverable messages slowly damages your sender reputation. Over time, even with good content, your inbox placement drops, your emails get throttled, or worse — blocked entirely. The cost isn’t just wasted sends; it’s eroded credibility with inbox providers.

Why Invalid Emails Hurt Your Reputation

When you send to non-existent or unverifiable emails, you trigger hard bounces. Most SMTP servers don’t just reject the mail — they log the failure and share it with other providers via feedback loops or blocklists like Spamhaus (Spamhaus). Even one failed delivery can register, but high bounce rates over time signal to ISPs that you’re either negligent or malicious.

Providers like Gmail, Outlook, and Apple Mail use reputation systems that weigh bounce rates, engagement, and complaint volumes. A consistent pattern of 5xx errors — especially from Mailgun — often points to a list with many dead addresses. If your bounce rate climbs beyond 2% (a commonly cited threshold in deliverability best practices), you risk being flagged as a low-quality sender.

What Happens When Reputation Deteriorates

Beyond just failing to reach inboxes, you’ll see diminishing returns. ISPs begin throttling your mail — delivering only a fraction of your messages, if any. Some providers will filter your emails into lower-priority folders, or even block them outright without notifying you. This happens even if your content is on-brand and requested.

Let’s say you have a 20,000-person list. If 1,000 of those addresses are invalid, and you send to all of them, you’re generating 5% bounces. That’s within acceptable limits in some industries, but it’s still a red flag if the same recipients are unreachable across multiple campaigns.

Before you send to a large list, run it through a real-time verification system. Tools like real-time email verification or bulk list cleaning filter out invalid, risky, and catch-all addresses before they ever reach your ESP. It’s not a magic fix, but it removes the most avoidable strain on your reputation.

Fixing a bad list takes work. But sending to broken addresses — even with Mailgun saying “sent” — just makes the damage worse. Prevention is the only sustainable strategy.

Email List Validation vs. Other Tools: What You Actually Get

You’re not just checking syntax—you’re testing whether an email will land in the inbox, not the spam folder. Unlike generic tools that only flag invalid addresses, Email List Validation gives you inbox-placement testing, real-time verification at 98.9% accuracy, and direct integrations with HubSpot, Mailchimp, SendGrid, and Klaviyo. You can catch problems before sending, not after. This means fewer 5xx errors in Mailgun and fewer misfires in HubSpot’s "sent" log.

What’s missing from other tools?

Most tools like ZeroBounce, NeverBounce, or Kickbox only verify syntax and basic format. They won’t tell you if an email is accepted by the receiving server or if it’s blocked—common issues when Mailgun reports 5xx errors during delivery.
They often lack inbox-placement testing. An email might be "valid" on their system but still hit a spam filter or get greylisted. That’s why many teams still see low inbox placement even after cleaning lists.
Generic tools don’t integrate directly with your CRM or email platform. You have to export, clean, and re-import—creating delays and opportunities for errors.
They don’t offer real-time verification at scale. You can’t block invalid emails at signup or during list import, which is where deliverability starts.

What you get with Email List Validation

True inbox placement testing—not just delivery status. You see if an email lands in the primary inbox, spam, or gets rejected. This aligns with industry standards like those from Return Path (now Validity), which emphasize that inbox placement is the real metric of success.
Real-time verification with 98.9% accuracy. This isn't just a claim—it’s backed by repeated testing across domains, including catch-all, disposable, and role-based addresses.
Immediate integration with HubSpot, Mailchimp, SendGrid, and Klaviyo. Validate emails at the point of entry or clean large lists in bulk. No more mismatched data between your ESP and your CRM.
Use the inbox placement testing feature to simulate actual sends and verify delivery outcomes before you press send.
For high-volume workflows, use the real-time API to check addresses on sign-up or during data entry.
Start with 100 free verifications, and never lose unused credit—unlike some tools that expire or reset credits.

Deliverability isn’t about sending more—it’s about sending right.

How to Prevent 5xx Errors Before They Happen

You don’t wait for Mailgun to return 5xx errors during a send. You stop them before they happen by verifying emails upfront. Clean your list with real-time validation, automate checks via API, and run periodic inbox placement tests to catch stale or risky addresses early. This reduces bounces, protects your sender reputation, and keeps delivery rates stable.

Prevent 5xx errors with verification as a mandatory step

Run every email through real-time verification before syncing with HubSpot or Mailgun — no exceptions.
Use an API-powered tool to validate addresses on-the-fly during signups, list imports, or campaign launches.
Check for syntax, domain existence, and mailbox responsiveness in a single scan, not after sends fail.

Automate and audit to sustain long-term deliverability

Integrate email verification into your workflow using the real-time verification API to validate every new subscriber instantly.
Run monthly inbox-placement tests to see where your messages land — in inbox, spam, or undelivered — and flag drift early.
Use inbox placement testing to catch reputation issues before they hurt your overall deliverability.
Regularly audit your subscriber list using bulk verification tools to remove invalid, catch-all, or risky addresses.

When Mailgun returns a 5xx error, it’s already too late. The fix is not in the error log — it’s in the list before the send. Tools like bulk email list cleaning help identify dead domains, disposable emails, and role accounts before they cause delivery failures.

Deliverability is not a one-time setup. It’s continuously maintained.

Industry best practices emphasize verification at source — not after. The SMTP RFC states that sending to invalid or non-responsive mailboxes creates unnecessary load on infrastructure. Avoiding these sends preserves your sender reputation and reduces the risk of being throttled or blocked.

Let’s be clear: no campaign should go out without a clean list. No integration should sync a raw list without validation. No team should be surprised by 5xx errors in production. The most reliable path to consistent delivery starts with verification, not reaction.

What to Do If You Already Sent to 5xx-Blocked Addresses

If Mailgun reports 5xx errors but HubSpot says your emails were sent, you’ve likely delivered to invalid, blocked, or non-existent addresses. This can hurt your sender reputation and trigger spam filters. The fix starts with identifying exactly which emails failed, re-validating the entire list, filtering out risky addresses, and resending only to confirmed valid ones. Let’s walk through the steps.

Step 1: Pull and Analyze Mailgun’s Delivery Reports

You can’t fix what you don’t see. Export your delivery logs from Mailgun and filter for 5xx errors—these indicate permanent delivery failures like "550 User unknown" or "554 Message rejected." These aren’t temporary bounces; they’re hard rejects. You should also check HubSpot’s activity logs for the same campaign to confirm which emails are marked as "sent" but may never reached an inbox.

Step 2: Re-Validate the Full List with a Trusted Tool

Once you have the list of failing addresses, re-validate them using a service like Email List Validation’s bulk verification. This isn’t a guess—it checks DNS, MX records, SMTP connectivity, and real-time blacklists. A 98.9% accuracy rate means you’re not pulling out false positives. This step separates truly valid addresses from those that were never deliverable.

Identify 5xx errors in Mailgun’s logs and export them into your CRM or CSV.
Run the list through Email List Validation for a fresh, real-time assessment of deliverability. It will flag catch-alls, role accounts (like admin@, sales@), and disposable domains.
Remove all invalid types from your database. Catch-alls accept any email but rarely engage. Role accounts are often monitored, ignored, or automatically filtered. Disposable domains are temporary and high-risk.
Re-segment your audience to exclude these addresses, and prepare a clean version for re-sending.
Re-send only to confirmed valid emails—this prevents further damage to your sender reputation.

The 5 steps described in “Step 2: Re-Validate the Full List with a Trusted Tool”, in order.

Prevent Recurrence

Don’t wait for a 5xx error to act. Use Email List Validation’s API in your sign-up flow to validate in real time. This stops invalid emails from entering your system at the source. Industry best practices, like those outlined in RFC 5321, confirm that verifying addresses before sending is the foundation of reliable email delivery.

After cleaning, test your new list with an inbox placement tool to confirm it lands in primary inboxes. That’s the final checkpoint before your next campaign.

Conclusion: Stop Trusting 'Sent' Status Alone

A 'sent' status in HubSpot doesn’t mean the email reached a real inbox. It only means the message left your sender system. Bounces, filters, and spam traps can still block delivery.

Mailgun’s 5xx error indicates a server-side failure. This isn’t a soft fail—it’s a hard block. Relying on this status alone leads to wasted sends and damaged sender reputation.

Use real-time verification before sending. With Email List Validation, you catch invalid, risky, and catch-all emails upfront. This reduces bounces, protects sender reputation, and ensures actual inbox placement.

Sources

HubSpot's list-health benchmarks show an average bounce rate of 2.48% and an average unsubscribe rate of 0.22% across industries. — HubSpot (2025)

Keep reading

Ready to put this into practice? Email List Validation verifies emails with 98.9% accuracy — start with 100 free verifications.

Frequently asked questions

Why does HubSpot say 'sent' but Mailgun says 5xx?

HubSpot records a successful SMTP handshake, while Mailgun detects a server-level rejection. The message was accepted but not delivered.

Can I trust an email address that passes syntax check but fails deliverability?

No. Syntax validity doesn't guarantee inbox delivery. Catch-alls, role accounts, and graylisted domains can still fail delivery.

How accurate is Email List Validation’s deliverability check?

It achieves 98.9% accuracy by using real-time SMTP, MX, and DNS checks across multiple criteria.

Does Email List Validation work with Mailgun and HubSpot?

Yes. It integrates directly with both platforms, allowing bulk verification and real-time validation before sending.

What’s the difference between a catch-all and a valid email?

A catch-all accepts any address, even invalid ones, leading to hard bounces and spam reputation damage. Valid emails are unique and deliverable.

How do I test if an email actually lands in the inbox?

Use Email List Validation’s inbox-placement test feature to send a sample message and confirm reception.

Can I use Email List Validation for cold outreach?

Yes. Use the email finder and verification tools to build and validate a clean, deliverable prospect list.

Are there any limits on how many emails I can verify?

No. You get 100 free verifications to start, and purchased credits never expire.

What is a 550 error in SMTP?

A 550 error means the recipient mailbox is not found or was rejected by the server. It’s a hard bounce.

Why are role accounts bad for deliverability?

They're often unmonitored, have high spam rates, and are flagged by filters. Sending to them harms sender reputation.

How often should I verify my email list?

Verify before each campaign, and periodically during list maintenance to remove outdated or invalid addresses.

Can disposable email domains affect my sender score?

Yes. Disposable domains are frequently used for spam and abuse, so sending to them can trigger filters or lower your sender reputation.