On 2024-08-13 at 15:06:13, Konstantin Ryabitsev wrote: > On Mon, Aug 12, 2024 at 09:16:56PM GMT, brian m. carlson wrote: > > Gmail and Yahoo have both set up new requirements for senders[0]. This > > requires that all senders have SPF and DKIM, and senders sending more > > than 5000 messages per day have DMARC set up. One-click unsubscribe in > > RFC 8058 is also obligatory, as is TLS for sending messages. These > > changes came into effect in February 2024. > > > > I don't believe vger uses DKIM (at least, it doesn't appear to add DKIM > > headers) and doesn't support RFC 8058 one-click unsubscribe. Perhaps > > adding support for those, as well as any other relevant requirements, > > would improve things. > > These guidelines are only applicable if vger was the origin of the messages, > not a forwarder. For forwarders, it is only required to add ARC signatures: > > https://support.google.com/mail/answer/175365?hl=en The article you linked still recommends DKIM. In addition, the article I linked doesn't appear to limit itself to non-mailing lists in any way. It says, "email senders", and a mailing list sends emails. In fact, it explicitly mentions "[i]f you manage a forwarding service, including mailing lists or inbound gateways," so it still appears to cover both cases and apply to all senders, with only some additional requirements applying to forwarding services. In general, adding DKIM (whether or not ARC is supported) _will_ dramatically improve the deliverability of email in general, so it's a win overall. Adding one-click unsubscribe would also probably keep some of those unsubscribe messages from hitting the list since people could automatically use the functionality of their mail client to unsubscribe. And from a personal point of view, it is definitely useful for me, as someone who manages their own mail server, to heavily negatively score all email without DKIM, but I can't do that because vger doesn't add any. That's the only thing preventing me from doing that. -- brian m. carlson (they/them or he/him) Toronto, Ontario, CA
Attachment:
signature.asc
Description: PGP signature
