From: <rsbecker@nexbridge.com>
To: "'Mike Castle'" <dalgoda@gmail.com>, "'git'" <git@vger.kernel.org>
Subject: RE: Heads up: GMail regularly marking list messages as spam
Date: Mon, 12 Aug 2024 11:26:34 -0400 [thread overview]
Message-ID: <030501daeccc$0747f210$15d7d630$@nexbridge.com> (raw)
In-Reply-To: <CA+t9iMyT8fAR_fvQXOer=ivLnNKDnH8g_M8iQiq7gdrnfG7aCg@mail.gmail.com>
On Monday, August 12, 2024 11:10 AM, 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.
>
>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?
>
>It would be interesting to see if this affects domain specific users as well (e.g.,
>Google itself).
What I think you will find is that some spammers use this mailing list to send spam.
Most of it gets blocked because it is in HTML or RTF. However, various honey-pots
and organizations like SpamCop detect the mailing list servers as the source of spam
so the servers get black-listed or marked as spam. Unless the servers themselves
filter out spam before redistributing it, this is going to keep happening.
next prev parent reply other threads:[~2024-08-12 15:26 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 [this message]
2024-08-12 16:04 ` Konstantin Ryabitsev
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='030501daeccc$0747f210$15d7d630$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--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).