Tell HN: Make sure to configure DKIM/SPF with Fastmail

Re:Tell HN: Make sure to configure DKIM/SPF with Fastmail by 2000UltraDeluxe on Sunday March 27, 2022 @04:33PM (#30823820)

Also add DMARC to the list aswell, and make sure to warm up the domain again once you're done.

[ Parent | on HN ]

Re:Tell HN: Make sure to configure DKIM/SPF with Fastmail by ivan_ah on Sunday March 27, 2022 @05:23PM (#30824302)

What does "warm up" mean in this case? Send a few emails?

Also, what policy do you recommend fro DMARC: none, quarantine, or reject?

[ Parent | on HN ]

Re:Tell HN: Make sure to configure DKIM/SPF with Fastmail by boris-ning-usds on Sunday March 27, 2022 @05:43PM (#30824432)

This is what mailgun recommends for warming up email / email reputation. https://www.mailgun.com/blog/domain-warmup-reputation-stretc...

If you're just starting out, start with none. Quarantine or reject needs to be carefully monitored over time.

[ Parent | on HN ]

Re:Tell HN: Make sure to configure DKIM/SPF with Fastmail by johngalt on Sunday March 27, 2022 @06:10PM (#30824664)

DMARC: Set is as p=none and read your reports from the RUA tags.

Once you are confident that all the legitimate mail is aligned, then go straight to p=reject. Many will recommend quarantine, but it's better to have an email bounce back immediately vs silently get lost in a spam folder. Outside of troubleshooting there isn't much use for P=Quarantine in DMARC or '~all' in SPF.

[ Parent | on HN ]

Re:Tell HN: Make sure to configure DKIM/SPF with Fastmail by 2000UltraDeluxe on Monday March 28, 2022 @02:16AM (#30827630)

~all in SPF is a different beast, since -all breaks forwards. There's still an unreasonably large amount of people heavily reliant on forwards, so I'd not go as far as to recommend ~all to people who are not 100% certain of the consequences.

[ Parent | on HN ]