Hi,
Thanks Gavin!
It's a somewhat useful article, but reads like a marketing FUD piece by
Postmark.
Most of these things have been essentially mandatory for Google for quite a
while now. I'm not so sure about Yahoo so perhaps the article conflates the
Google/Yahoo joint announcement with all of these things.
Having said that, your linked article
https://support.google.com/a/answer/81126 says "Use a TLS connection for
transmitting email" has been added to Google's sender guidelines in "Dec.
2023" so some things are definitely changing.
My system does opportunistic TLS, but, as ever, it's worth running the
checking sites you link to every so often.
So I guess, in summary, thanks for the heads up. It's going to take some
work to actually discover the changes that are important to make right now
tho'.
I only found out a few days ago that Gmail and Yahoo
(and
possibly others) will require senders to have SPF, DKIM and
DMARC records (as well as certain other criteria) from February
2024:
https://postmarkapp.com/blog/2024-gmail-yahoo-email-requirements
I'm currently setting this up for a couple of my domains (it's
already working on a test sub-domain) to make sure I do it
right, but thought that I should drop a mail here for anyone
else who isn't already aware.
Some useful links:
https://support.google.com/a/answer/81126
https://senders.yahooinc.com/best-practices/
https://www.linuxbabe.com/mail-server/setting-up-dkim-and-spf
(Postfix and DNS)
https://www.linuxbabe.com/mail-server/create-dmarc-record
https://www.exim.org/exim-html-current/doc/html/spec_html/ch-dkim_spf_srs_a…
Testing:
https://www.mail-tester.com
https://www.mail-tester.com/spf-dkim-check
Emailing check-auth(a)verifier.port25.com from the domain you are testing.
Thanks
Gavin
--
Best wishes,
@ndy
--
andyjpb(a)ashurst.eu.org
http://www.ashurst.eu.org/
0x7EBA75FF