How to Check Mailgun Logs for a Specific Email
Filter Mailgun's Sending Logs by recipient to find the email, check the quick-view delivery status, then handle bounces, unsubscribes, and unauthenticated-sender errors with the targeted fixes below.
When an email goes missing, Mailgun's Sending Logs show exactly what happened: delivered, deferred, bounced, dropped, or rejected. Filtering by recipient is the fastest way to find a specific message. Here is how, plus fixes for the errors you will hit most often.
Find the email in Mailgun logs
- Log into https://app.mailgun.com/app/dashboard.
- Click Sending.
- Click Logs.
- Confirm the correct domain is selected at the top.
- Click Add Filter.
- Pick Recipient from the dropdown and paste the email address you are looking for.
- Click Filter.
Read the result
- Click the gear icon on the right of the log entry.
- Select Quick view.
- You will see a preview of the email and its delivery status.
If status shows delivered, ask the recipient to check spam and junk folders. If it is consistently delivered but never seen, the recipient's email provider may be filtering or blocking server-side — contact Mailgun support to investigate the receiving end.
Common errors and fixes
Not delivering to a previously bounced address
Mailgun keeps bounced addresses on a suppression list and stops sending until you remove them.
- Click Sending > Suppressions.
- Pick the domain at the top.
- Search for the recipient's email.
- Select the entry and click the trash icon to remove it from the Bounces tab.
Recipient unsubscribed accidentally
Switch to the Unsubscribes tab on the same Suppressions screen and remove the email there. Make sure the unsubscribe was actually accidental — re-mailing someone who genuinely opted out is a compliance issue.
Unauthenticated email from your own custom domain
Cause: DMARC failure. Fix: set DMARC to none on the domain at your DNS provider (or Google Workspace if applicable). Once DNS propagates, Mailgun should accept the message.
Unauthenticated email from yahoo.com, hotmail.com, aol.com, outlook.com
Sending from a yahoo.com or aol.com address through Mailgun fails DMARC because those providers publish strict p=reject policies. Switch the From address to your own custom domain (or to a Gmail address you own) and resend.
// Change
From: name@yahoo.com
// To
From: name@your_domain.comTips for cleaner logs
- Always send from a domain you control with full SPF, DKIM, and DMARC. Sending from public mailbox domains will fail.
- Audit the Suppressions list monthly — bounces accumulate and silently throttle reach.
- If a single recipient is consistently failing, look at their domain's MX, SPF, and DMARC records (mxtoolbox.com is fastest) before assuming Mailgun is at fault.
Frequently Asked Questions
Mailgun shows delivered but the recipient says they never got it. What now?
Why is Mailgun blocking sends to a specific address?
What does unauthenticated email from yahoo.com mean?
How do I fix unauthenticated email from my own custom domain?
Was this article helpful?
Thanks for the feedback.