Spotted on Marc Lou's slide: "Emails: DNS records, avoid spam"
Was at the Indie Hackers x Cognition meetup in Dubai last night. @marclou showed the list of boring stuff every SaaS has to build.
Right next to Stripe and auth: Emails: DNS records, avoid spam.
It stuck with me becuase it's exactly the pattern. you set SPF, DKIM and DMARC once at launch, then never look again. Until the welcome email lands in spam and nobody knows why.
The 3 things that usually break later:
SPF goes over 10 DNS lookups after you add one more tool
the tool that actually sends your emails has no DKIM
DMARC stays at p=none forever, or doesn't exist at all
That's why we built mailX. Type your domain and get SPF, DKIM, DMARC and blocklists checked in a few seconds, free: https://themailx.com
When did you last check your DNS records? At launch and never again?
Replies
The dangerous part is that “configured” feels like “finished,” so nobody checks it again. I’d treat email health like uptime and surface problems before a customer reports them. What usually reveals the issue first for your users?
@yashpanpaliya yes, "configured" is not "monitored". most people only look at it once.
For our users it's almost always one of these: a customer saying "I never got your email", a password reset that doesn't arrive, or open rates quietly dropping for a week before anyone conects it to DNS.
Your uptime comparison is the right way to see it. Nobody would wait for a customer to tell them the site is down???