Why are SFMC emails showing as delivered but not received by the subscriber?
Summary
What email marketers say8Marketer opinions
Email marketer from Reddit suggests that even if an email isn't bouncing, it could be landing in the spam folder. They recommend checking spam folder placement across various email providers to diagnose the issue.
Email marketer from MailerQ explains that if you have hard bounces you should immediately remove them from the sendlist to avoid issues with deliverability
Email marketer from Litmus explains that certain keywords, excessive use of images, or poorly formatted HTML can trigger spam filters, preventing delivery even if the sending platform reports 'delivered' status.
Email marketer from Email Hippo explains that an email being marked as spam could be down to the email content - so things like lots of images, spammy language, dodgy links, too many colours etc.
Email marketer from Gmass shares that many of the common deliverability issues occur when a new IP address is used without first warming it up. Warming up is the process of slowly building your reputation with recipients and mailbox providers.
Email marketer from StackOverflow shares that missing SPF, DKIM, or DMARC records can cause emails to be flagged as spam or blocked by recipient servers, even if SFMC reports them as delivered. Verifying these records is crucial.
Email marketer from EmailGeeks explains that B2B recipients may filter/quarantine emails after acceptance (showing as delivered in SFMC). Yahoo rarely discards mail, but if all Yahoo recipients are affected, a ticket with postmaster.verizonmedia.com should be opened. Custom filters may be the issue.
Email marketer from Email on Acid explains that low engagement is one of the key reasons why your subscribers may not be receiving your email, this can mean people don't open them, or engage and mark your emails as important or move them out of the SPAM folder.
What the experts say4Expert opinions
Expert from Email Geeks explains that B2B senders might quarantine mail after acceptance. Yahoo rarely discards mail intentionally. More details are needed for troubleshooting, such as whether the issue affects one or many Yahoo recipients. If it's one, the recipient might have forwarding rules. If it's all, open a ticket with <http://postmaster.verizonmedia.com>. For B2B, identify the filter used. If it affects one business, it's a custom filter; if it affects all, contact the filter maintainer.
Expert from Word to the Wise explains that proper setup of your sending infrastructure, specifically rDNS, SPF, DKIM, and DMARC is essential for deliverability. If these are configured incorrectly, email providers may consider your messages suspicious and filter them into the spam folder or outright block them, regardless of what SFMC reports. Ensure these records are valid and properly configured.
Expert from Spam Resource explains that poor list hygiene (sending to old or unengaged addresses) can significantly impact deliverability. Even if emails are 'delivered' by SFMC, recipient servers may filter them if the sender's reputation is damaged by sending to problematic addresses. Maintaining a clean list and removing inactive subscribers is crucial.
Expert from Email Geeks explains that once an email is accepted by the recipient's MTA (given a 250OK), the recipients can do anything they want with the message.
What the documentation says4Technical articles
Documentation from Mailjet explains that being on a blocklist can cause emails to be silently dropped by recipient servers. They recommend checking blocklist status and taking steps to get removed if listed.
Documentation from Salesforce Help explains that deliverability issues can occur even when emails are marked as 'delivered' in SFMC. This can be due to recipient-side filtering, content issues triggering spam filters, authentication problems, or IP reputation issues.
Documentation from SendGrid explains that reasons emails may not be received include blocklisted IPs, domain reputation problems, spam traps, content issues, missing authentication records (SPF, DKIM, DMARC), and recipient server issues.
Documentation from SparkPost explains that not processing feedback loops (complaints) can hurt sender reputation and lead to emails being filtered or blocked. Implementing feedback loops is crucial for identifying and addressing deliverability issues.