Your messages leave, nobody receives them. Before rewriting your subject lines or changing sending platform, there is an order of investigation that saves a lot of time.
1. Authentication — the first thing to rule out
A message whose origin the receiving provider cannot verify starts with a handicap that no amount of editorial work will fix. Google and Microsoft now require it explicitly from bulk senders.
Three questions: does SPF authorise the sending server? Does DKIM sign the messages? And above all — is one of the two aligned with the displayed domain? That last point is where it usually fails, and it is invisible without DMARC. What each of the three does.
2. Sender reputation
Domains and IP addresses build a reputation from complaints, non-existent addresses hit, and how regular your volumes are. A sudden spike from a fresh IP is a classic signal: a dedicated IP is warmed up gradually, it does not start at full load.
A domain spoofed by a third party degrades that reputation through no fault of yours — one more reason to know who sends in your name.
3. List quality
Addresses collected without consent, purchased lists, contacts never cleaned: bounce rates and complaints rise, reputation falls. A visible, working unsubscribe link costs far less than a spam complaint, which weighs infinitely more.
4. Content, last
It counts, but less than people think: a properly authenticated message sent to a clean list rarely lands in junk because of an unfortunate word. The real factors are links to domains with poor reputation, image-only messages, and URL shorteners.
What DMARC fixes, and what it does not
To be clear: DMARC does not magically improve deliverability. It says nothing about your content or the quality of your lists.
What it does: eliminate an entire category of cause — failing authentication — and give you the visibility that is missing everywhere else, over every server sending under your name, including the ones you did not know existed. It is the starting point of any serious deliverability diagnosis, not the whole solution.
Clarsend reads those reports for you: compliance rate per domain, identification of every sender, an alert when something degrades.
Laisser un commentaire