From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
Mike Castle <dalgoda@gmail.com>, git <git@vger.kernel.org>
Subject: Re: Heads up: GMail regularly marking list messages as spam
Date: Tue, 13 Aug 2024 11:06:13 -0400 [thread overview]
Message-ID: <20240813-sociable-fresh-whippet-3ee335@meerkat> (raw)
In-Reply-To: <Zrp7yNKMxhPk6Tyt@tapette.crustytoothpaste.net>
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 only thing we aren't doing is we're not adding X-Forwarded-To headers,
because mlmmj doesn't yet support it (should be in 1.5).
-K
next prev parent reply other threads:[~2024-08-13 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 15:10 Heads up: GMail regularly marking list messages as spam Mike Castle
2024-08-12 15:26 ` rsbecker
2024-08-12 16:04 ` Konstantin Ryabitsev
2024-08-12 21:16 ` brian m. carlson
2024-08-13 15:06 ` Konstantin Ryabitsev [this message]
2024-08-13 22:18 ` brian m. carlson
2024-08-14 0:10 ` Konstantin Ryabitsev
2024-08-14 7:32 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240813-sociable-fresh-whippet-3ee335@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=dalgoda@gmail.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).