Hi,
Since a few weeks now, we're running DMARC for the mailing lists. So far, we've run with the loosest policy possible ("none"). The other options are "quarantine" and "reject".
I'm thinking we'll want mail sent using our domain (common-lisp.net), failing the DMARC checks (failing SPF and/or DKIM), to be quarantined (moved to SPAM) at the very least. I noticed that fastmail is using an even stricter policy ("reject"), but moving straight from "none" to "reject" seems too much (because "reject" prevents delivery; not just moving to SPAM).
This will affect everybody using an @common-lisp.net mail address with their own mail server.
Does this affect anybody on this mailing list? Any comments with respect to the stricter policy?
Regards,
Erik.
I’m not impacted as a user of a @common-lisp.net email address on a different server, but I fully support increasing to quarantine.
— jb On Aug 26, 2024 at 16:31 -0400, Erik Huelsmann ehuels@gmail.com, wrote:
Hi,
Since a few weeks now, we're running DMARC for the mailing lists. So far, we've run with the loosest policy possible ("none"). The other options are "quarantine" and "reject". I'm thinking we'll want mail sent using our domain (common-lisp.net), failing the DMARC checks (failing SPF and/or DKIM), to be quarantined (moved to SPAM) at the very least. I noticed that fastmail is using an even stricter policy ("reject"), but moving straight from "none" to "reject" seems too much (because "reject" prevents delivery; not just moving to SPAM).
This will affect everybody using an @common-lisp.net mail address with their own mail server.
Does this affect anybody on this mailing list? Any comments with respect to the stricter policy?
Regards,
Erik.
-
Erik Huelsmann -
Jon Boone