From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Mike Castle <dalgoda@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Heads up: GMail regularly marking list messages as spam
Date: Mon, 12 Aug 2024 12:04:24 -0400 [thread overview]
Message-ID: <20240812-devout-mindful-dogfish-81cefa@lemur> (raw)
In-Reply-To: <CA+t9iMyT8fAR_fvQXOer=ivLnNKDnH8g_M8iQiq7gdrnfG7aCg@mail.gmail.com>
On Mon, Aug 12, 2024 at 08:10:23AM GMT, Mike Castle wrote:
> If you read the list via GMail, you may want to regularly check your
> Spam label for messages from the git list.
>
> I'm not sure what's up with that. A handful of real spam had made it
> through vger, but GMail seems to be hitting a fair number of false
> positives lately.
Gmail is using internal spam training on all mail that it receives.
Unfortunately, mailing list traffic like that on the git list falls
way outside what is "normal," and this tends to trigger false-positives.
> Sometimes it is just one message in a patch set. Others, it is whole
> sets of patches. I didn't check to see if there was anything in
> common across the messages. Maybe if anyone has a large batch, they
> can check?
Most of the time it's super unhelpful:
Why is this message in spam?
It is similar to messages that were identified as spam in the past.
Sometimes it's something specific:
Why is this message in spam?
Lots of messages from xxxxx.msg.chrl.nc.charter.net were identified as
spam in the past.
This isn't really anything to do with vger.kernel.org -- we are complying with
all Gmail "bulk mail sender" requirements and we try our best to deny spammers
early. Unfortunately, my general recommendation is not to use Gmail for this
kind of work.
-K
next prev parent reply other threads:[~2024-08-12 16:04 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 [this message]
2024-08-12 21:16 ` brian m. carlson
2024-08-13 15:06 ` Konstantin Ryabitsev
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=20240812-devout-mindful-dogfish-81cefa@lemur \
--to=konstantin@linuxfoundation.org \
--cc=dalgoda@gmail.com \
--cc=git@vger.kernel.org \
/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).