Why a well-kept sending domain collects fewer spam reports

Every large receiver — Gmail, Outlook, Seznam, the corporate gateways — keeps a running score on your domain. It is built from what they observe over time: how much of the mail claiming your name authenticates, how consistently it comes from the same places, how often recipients mark it as spam, whether your sending addresses turn up on blocklists. That score decides where your next message lands before anyone reads a word of it. Reputation is not a setting you configure; it is a history you accumulate — which is exactly why hygiene pays and neglect compounds.

Where spam reports against your name actually come from

When people think "spam complaints", they picture their own newsletter annoying someone. That happens — but for most domains the larger, invisible share is mail they never sent. The From line of an email is just text: anyone can put your domain in it. Until receivers have an instruction telling them to refuse unauthenticated mail, some of the forged messages get delivered, recipients hit "report spam" on them, and the complaint is recorded against your domain. You are collecting spam reports for a spammer's output.

A published, enforced DMARC policy cuts that loop. At p=quarantine, mail that fails authentication lands in spam folders instead of inboxes; at p=reject it is refused outright and never reaches a human who could report it. Fewer forged deliveries means fewer complaints attributed to your name — mechanically, not aspirationally. This is why moving off p=none is the single most consequential hygiene step: p=none means "report the spoofing to me but deliver it anyway".

Why authenticated consistency compounds

The positive half of the ledger is consistency. When every legitimate system that sends as your domain — your mailserver, your invoicing tool, your newsletter platform — signs with your DKIM key and is named in your SPF, receivers see one coherent picture: this domain's mail authenticates, from known infrastructure, day after day. Authenticated volume is what reputation systems can safely credit; unauthenticated volume is at best neutral and at worst indistinguishable from forgery. A domain that authenticates 100% of its mail builds reputation with every message it sends. A domain at 80% is teaching receivers to be suspicious of one message in five.

Alignment is the detail that decides whether this credit accrues. Mail must not merely pass SPF or DKIM somewhere — the domain that passes must be the domain in the From line. A newsletter tool signing with its own domain authenticates itself, not you.

The hygiene that leaks silently

Reputation damage rarely announces itself. A DKIM key rotated on one side and not the other, an SPF record pushed past its 10-lookup limit by a marketing tool's include, a sending address that lands on a blocklist over a weekend — each one quietly converts a slice of your authenticated volume into failures, and receivers adjust their score long before a customer mentions that your invoices are in spam. This is why hygiene is a monitoring habit, not a setup task: the records were right on the day you published them; the question is whether they are still right today.

What good hygiene looks like in practice

Publish SPF and DKIM for every system that legitimately sends as you, and check the alignment, not just the pass. Publish DMARC with a reporting address, so receivers tell you what they are seeing. Watch the reports for senders you do not recognize — some are forwarders (harmless: your own mail, relayed with your signature intact), some are tools a colleague connected, some are attacks. Tighten the policy when the data says your own mail is safe — quarantine a slice first, then reject. Keep an eye on blocklists and on the records themselves, because both drift. None of these steps is difficult; the work is noticing when one of them stops being true.

That is the loop Sojka automates: reports decoded into per-sender verdicts, DNS polled for drift, blocklists checked on a schedule, and a push to your phone the moment any of it changes — with a readiness advisor that tells you when tightening the policy is safe. The payoff of the hygiene is cumulative and quiet: fewer spam reports carrying your name, a reputation score that compounds in your favor, and your real mail landing where it was addressed.

Related: What DMARC alignment means for how receivers connect authentication to the From line, and The domain that sends no mail still needs DMARC for the domains you own but never send from.