Thread

1. gerdesj · 1790887822 · focus · HN ↗

   This was not written by an email admin. Start with the real basics:

   Your MTA should announce itself and DNS should agree. So your MTA says: HELO smtp.example.co.uk

   smtp.example.co.uk will resolve to an A record (say a.b.c.d) and a reverse lookup will also work:

   d.c.b.a.in-addr.arpa PTR smtp.example.co.uk.

   Remember this is all about reputation, so if you also DNSSEC sign example.co.uk, then you will look like you care about your domain reputation.

   Then do SPF, DKIM and DMARC. Note how the example for SPF stops at ~all and not -all. The rest is also superficial.

   Anyway, I run email systems that do the job properly and it is not trivial and certainly not formulaic. There is no shortcut to getting an IP address/range trusted.

   The advice on that page is ... good as far as it goes but woefully inadequate for running an email system. It's a good start.

   1. snowwrestler · 1790910615 · focus · HN ↗

      I’ve never seen evidence that DNSSEC helps email reputation. Always willing to consider new evidence though.

      Reputation, in my experience, is not really based on tech stuff. You can ruin it with bad technical configuration, sure. But the only way to grow it above average is to send a steady stream of emails that readers open and click, sustained over a period of time, with no complaints.

Unofficial Hacker News client; not affiliated with Y Combinator.