Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Collection

Email Marketing Troubleshooting

Each page in this section starts from a symptom a sender can see, such as mail landing in spam or a bounce rate that keeps climbing, separates the plausible causes in a diagnosis table, and gives a check, a fix, a verification step and a prevention habit for each. The mechanism behind every cause is explained in an email guide elsewhere on the site, and every page links to it rather than repeating it.

Looking for how to use this library? Read the guide below the list.

All 12 pages in this collection

How these pages work

Every page follows the same order. It first asks whether the problem is real and where it sits, because a surprising share of email "problems" turn out to be a reading error: a delivered count taken as proof of inbox placement, an open rate compared across a change in how opens are measured, or one provider's behaviour read as the whole list's. A diagnosis table then sets out the symptom as the sender sees it, the check that confirms or rules out each cause, the cause and the fix. Each cause gets its own short section with the fix, a way to verify that it worked, and the habit that stops it returning, followed by a routine that catches the whole family of faults before the next large send.

The pages deliberately do not re-teach the mechanics. How SPF, DKIM and DMARC fit together, what the documented sender requirements ask of bulk senders, and how reputation is earned are explained in the deliverability guide; consent and imports live in the list building guide; engagement tiers and suppression in the segmentation guide. Each troubleshooting page links to the relevant section at the point a cause is confirmed.

Which page to start from

Pick the row that matches what you can see, not the cause you suspect. The pages beneath this introduction are listed automatically, so a new diagnosis appears here once it is published; until then, the guide named in the last column holds the relevant checks.

What you are seeingStart withBackground
The platform says delivered, but subscribers find the mail in spam or never see itEmails going to spamDeliverability
Messages are refused outright and the bounce rate climbsEmail bounce rate too highList hygiene SOP
Aggregate reports show mail failing DMARCDMARC failingFundamentals
One send or one flow loses far more subscribers than usualEmail unsubscribe rate spikingSegmentation
Opens fell sharply while nothing obvious changedEmail open rate dropped suddenlyEmail metrics and testing
A welcome, cart or other automated flow has gone quiet or sends far fewer emails than it has entrantsAutomated email flow not sendingAutomation hub
Clicks from a send hold steady, but orders credited to email fall or never arriveEmail clicks but no salesEmail metrics and testing
Sign-ups have slowed, or the list total stays flat while people keep joiningEmail list not growingList building and consent
Someone who unsubscribed says they are still receiving your emailUnsubscribed contacts still receiving emailList building and consent
A person writes that they did not subscribe to your emailsSubscribers saying they never signed upList building and consent
Customers say an order confirmation, receipt or password reset never arrivedOrder and account emails not arrivingPromotional vs transactional email
Subscribers receive the same email twiceSubscribers receiving duplicate emailsAutomation hub

Delivery, placement and measurement are three different questions

Most wasted effort in email troubleshooting comes from answering the wrong one of three questions. Delivery asks whether the receiving server accepted the message; a refusal comes back as a bounce with a reason, so delivery problems are loud and usually technical. Placement asks where an accepted message went: the inbox, a tab, or the spam folder. The sending platform cannot see placement at all, so placement problems are quiet and show up as falling engagement, customer complaints and movement in a provider's postmaster view. Measurement asks whether the numbers describe what happened; opens in particular stopped meaning "read" once mail clients began fetching images on the reader's behalf, as the metrics guide explains.

A bounce problem is therefore never fixed by rewriting a subject line, and a placement problem is rarely fixed by a DNS change alone. The promotions tab is placement too, and it is not a fault: mail that is marketing has been correctly classified as marketing. Before opening any page in this section, decide which of the three questions the symptom belongs to; the first section of every page helps with that.

When to audit instead

A troubleshooting page answers one question about one symptom, usually under time pressure. When several symptoms arrive together, when nobody can say where the list came from, or when the programme has not been reviewed in a long time, a structured review is the better tool. The email programme audit scorecard checks consent, deliverability, flows and reporting in one pass and scores what it finds, and the fundamentals hub sets out the hygiene routine that keeps most of these symptoms from appearing at all. A list that nobody has mailed in a long time is better restarted with the dormant list tutorial than diagnosed one symptom at a time, and a send that went out with a wrong price, a broken link or to the wrong people is handled by the tutorial on fixing a mistake in a sent email. The email marketing pillar places all of it in the wider system of list, content, automation and measurement.