A subscriber says your newsletter never arrived, but Mailchimp shows that the campaign was sent. Another contact receives it in a junk folder, while several people at one company see nothing at all. When Mailchimp emails are not received, those reports can point to different stages of the delivery process.
Quick answer
Trace one affected contact through the campaign’s recipient selection, sending status, bounce evidence, and receiving mailbox. Group similar cases only after you know where each path breaks. Do not resend to the entire audience or change subscription status simply to make the complaint disappear.
Key takeaways
- Trace recipient selection, send status, bounce evidence, and the receiving mailbox separately.
- A sent campaign does not establish that every subscriber can see the message.
- Keep consent intact and retest a small affected group instead of resending broadly.
This guide uses official Mailchimp documentation reviewed on October 9, 2026. It focuses on regular marketing emails, not a separate transactional-email service. The scenarios are illustrative, not results from a hands-on deliverability test. Account features and interface labels should be checked in your own plan.
Start with one campaign and one recipient
Choose a specific reported failure. Record the campaign name, audience, subject, From address, send date, and the affected email address in an approved private workspace. Ask the recipient when they checked and whether they searched other folders.
Keep “not received” separate from “not opened.” A person can receive an email without producing a tracked open. Equally, an apparent open is not conclusive proof that a person read the message. Begin with contact and delivery evidence rather than an aggregate open-rate chart.
Mailchimp’s email-report guide defines recipients, sending status, bounces, and successful deliveries. Its successful-delivery metric counts recipients without a hard or soft bounce; that metric does not itself establish placement in the recipient’s visible inbox. The guide also notes that bot activity can inflate engagement metrics.
Create a case identifier for the investigation. If several colleagues are involved, use that identifier instead of repeatedly copying subscriber addresses into broad chat channels. You need enough evidence to diagnose the case, not a new uncontrolled contact database.
Was the contact included in the actual send?
Open the report for the campaign in question and check the selected audience and recipient information. Do not assume that a contact’s presence somewhere in the account means the campaign was addressed to them.
Compare the campaign’s intended selection with the contact’s status and relevant segmentation data. Review exclusions as well as inclusion rules. A campaign intended for a particular group can legitimately omit another subscribed contact.
For an illustrative membership newsletter, a contact may be subscribed but lack the tag used to select current members. The corrective task is to verify the membership data and intended recipient rule, not to diagnose a mail-server failure that has not yet occurred.
Record the selection as it applied to the affected campaign. Today’s profile can differ from its state at send time. If you cannot establish that historical state, mark it as uncertain rather than asserting the person was definitely selected.
Check contact status without overriding consent
Mailchimp’s contact-status reference distinguishes subscribed, unsubscribed, non-subscribed, cleaned, and pending contacts. Unsubscribed and non-subscribed contacts cannot receive marketing email; cleaned addresses are not deliverable. Pending opt-ins require confirmation, and archived contacts are stored separately.
Use the documented status as evidence about eligibility. If someone is unsubscribed, do not manually label them subscribed because a colleague asks for another newsletter copy. Follow the approved subscription process and the recipient’s choices.
A customer can have an established commercial relationship without having opted into your marketing. Distinguish the purpose of the message from the existence of a customer record. Operational notifications and newsletters should not be treated as interchangeable.
For audiences in the US, Canada, UK, and Australia, involve the person responsible for communications compliance when the status or permission history is unclear. This guide explains software diagnosis; it does not establish a universal legal basis for sending across those countries.
Confirm whether the campaign finished sending
Check the campaign’s actual state rather than the time it was originally scheduled. A scheduled email, an active send, and a completed send represent different checkpoints. Note the status and the time you observed it.
Mailchimp’s Delivery Insights documentation describes delivery-progress information for eligible regular and plain-text campaigns on Premium. It explains Sending and Sent states. If your plan does not expose that feature, use the available campaign report and support route instead of assuming a missing progress panel proves a failure.
Do not promise the recipient immediate arrival while the system is still processing the campaign. Tell them what you have verified and what remains unknown. A useful internal update says “the contact was included; campaign sending is still in progress,” not “the inbox is broken.”
If the state remains unexpected, collect the campaign identifier and observation times for support. Avoid creating several copies of the campaign as a test. Repeated broad sends can create a separate subscriber-experience problem before the original one is understood.
Use bounce reasons to identify the next owner
If the recipient appears in bounced activity, inspect the individual reason. Mailchimp’s bounce-reason guide explains how to open the campaign report, view Bounced, and inspect Bounce Reason for an address. It states that reasons are retained for 30 days and that server replies are not always formatted in a way that permits perfect categorisation.
Preserve the relevant diagnostic wording promptly through an approved process. Remove unnecessary personal details when sharing it with technical colleagues. Do not send your entire audience export merely because one bounce needs investigation.
Distinguish address validity, temporary mailbox problems, and receiving-system policy evidence. A user saying “this is my real address” does not establish that the campaign passed the receiving gateway. Conversely, a category label alone may not explain the exact rejection.
Assign the next action from the evidence. An address typo requires confirmation through the appropriate contact process. A company-domain rejection belongs with the receiving administrator and your email specialist. An unexplained platform error belongs with Mailchimp support and the campaign case details.
If there is no bounce, inspect the receiving side
Mailchimp’s missing-campaign troubleshooting page identifies spam filtering, recipient address-book and filter settings, delivery delays, and corporate gateway issues as possibilities. It also directs corporate recipients to their administrator for appropriate allowlisting review.
Ask the recipient to search by the specific subject and From address across junk, spam, other inbox categories, and archived mail. Confirm that they are checking the same mailbox used for the subscription, especially when forwarding or multiple work addresses are involved.
For corporate recipients, request an administrator’s message trace or quarantine review through the recipient’s normal support process. Supply the campaign time, sender, and affected address securely. The administrator can inspect receiving-side evidence that is not visible in your marketing dashboard.
Do not ask anyone to turn off their spam protection or allow every message from your domain. Any exception should follow the receiving organisation’s security policy and the provider’s current guidance. Delivery troubleshooting should not become a reason to bypass security controls.
Group cases by the broken checkpoint
After reviewing individual examples, group them by evidence. This produces a more useful incident picture than a list of everyone who says they missed the newsletter.
| Case group | Evidence | Likely next investigation |
|---|---|---|
| Not selected | No recipient inclusion established | Audience, segment, exclusion, and status review |
| Still sending | Campaign has not completed its send | Platform progress and support evidence |
| Bounced | Individual bounce reply | Address or receiving-server reason |
| Same corporate domain, no visible inbox copy | Selected recipients and no bounce, with matching complaints | Receiving administrator’s trace and quarantine review |
| Found in another folder | Recipient locates the actual campaign | Folder/filter behaviour and sender practices |
These groups guide ownership; they are not automatic diagnoses. Two recipients at one company can have different mailbox rules. Preserve exceptions rather than forcing every case into the largest group.
Look for a change shared by the affected cases: a new sender address, revised segment, recent contact import, or a different recipient organisation. Treat that change as a hypothesis to test, not proof that it caused the missing email.
Prepare a support packet that avoids another investigation
Include the campaign identifier, audience, observed status, send time and timezone, affected-case count, and a small set of reviewed examples. State which examples were selected, bounced, or found in another folder.
For each example, include only the evidence the authorised support recipient needs. Redact unrelated customer data and internal notes. Use the provider’s authenticated support channel rather than posting raw headers and addresses in a public forum.
Explain what you already checked and what you did not change. For example: “Recipient selection confirmed; no subscription changes or broad resend performed; receiving administrator reviewing quarantine.” This helps the next person continue from evidence instead of restarting with basic questions.
Keep sender authentication investigation separate from recipient selection. If the email specialist identifies an authentication issue, have the domain administrator follow current official setup guidance. Do not paste speculative DNS changes into production simply because several subscribers report non-delivery.
Retest with a small, consented group
Define a controlled test after the identified issue is addressed. Use people who have agreed to receive the test and whose mail environments help check the relevant path. A test at one personal mailbox does not establish delivery at a client’s corporate domain.
Record the test subject, sender, recipient selection, timing, and expected observation. Ask participants to report where they find the actual message. Compare their observation with report activity, remembering that engagement metrics are not a substitute for inbox evidence.
Change one relevant variable at a time where practical. If you change the sender, content, audience, and receiving exception together, a successful test cannot tell you which change mattered. Keep the result modest: this tested path worked under these conditions, not “all future emails will arrive.”
After a successful repair, use your approved resend process only for the appropriate recipients and purpose. Do not resend to all non-openers as proof of delivery; the absence of an open event does not establish non-receipt.
Improve the operating process, not just one send
Maintain a pre-send check for audience selection, subscription eligibility, sender details, and a small reviewed preview. Give campaign owners a clear route for subscriber complaints and a standard case note.
Daily Jade’s email deliverability guide covers the broader sender programme. Use it for continuing improvements after this contact-level diagnosis, not as a reason to replace the specific evidence from the failed campaign.
Keep reporting definitions visible to the team. The email marketing metrics guide helps frame measurement questions. A campaign owner should know which report answers recipient inclusion and which metric describes tracked engagement.
If repeated complaints arise from automated journeys, document selection and timing at each step using the email sequence planning guide. This article concerns a regular campaign; automation-specific entry conditions need a separate investigation rather than being assumed identical.
Frequently asked questions
Does Sent mean every subscriber can see the email?
No. Establish campaign completion, recipient inclusion, and the individual delivery evidence separately. The receiving mailbox or gateway can still require investigation even when the campaign has completed sending.
Should I reimport a cleaned address?
Do not use reimporting as a shortcut around a delivery or permission problem. Review the documented status and bounce evidence, confirm the correct address through an appropriate process, and follow Mailchimp’s guidance and your organisation’s policy.
Can a successful test email prove the campaign is fine?
It proves only what you observed on that test path. Check the actual campaign’s selected recipients and affected receiving systems before drawing a broader conclusion.
Follow the evidence from selection to mailbox
When Mailchimp emails are not received, begin with one campaign and one affected contact. Confirm selection and status, inspect sending and bounce evidence, then involve the receiving administrator when necessary. Document the repair and retest a controlled path. That approach is more reliable than broad resends, forced subscription changes, or guesses based on open rates.
Join the conversation
Share a useful perspective, question, or first-hand experience with other Daily Jade readers.