From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: A spammer, wanting to poison our bayes seems to have found a hole at vger.kernel.org
Date: Mon, 1 Feb 2010 01:30:01 +0200 [thread overview]
Message-ID: <20100131233001.GW3486@mea-ext.zmailer.org> (raw)
In-Reply-To: <201001302313.19206.gene.heskett@verizon.net>
On Sat, Jan 30, 2010 at 11:13:19PM -0500, Gene Heskett wrote:
> Received: from vger.kernel.org ...
> Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand ...
> Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752309Ab0AaENg
> (ORCPT <rfc822;linux-kernel-outgoing>);
> Sat, 30 Jan 2010 23:13:36 -0500
> Received: from vms173007pub.verizon.net ([206.46.173.7]:39289 "EHLO
...
> Greeting;
>
> I just noticed that I have a poison bayes spam in my inbox cuz kmails filters
> haven't a clue what to do with a message addressed like this:
>
> to:linux-kernel-outgoing@vger.kernel.org
>
> Is this a leak in the mailing list server, or a total forgery?
Sharp eyes, thanks.
I quoted above Gene's emails Received headers as it travelled thru
vger.kernel.org. You can have a look at headers of this reply to see,
how many hops it did inside VGER.
There were explicit aliases mapping majordomo output to actual list
expansion. A smart spammer realized that by adding vger's domain on
them was possible to post directly to list system backend.
Now there is no separate backend, and such aliases no longer exist.
> --
> Cheers, Gene
Best Regards, Matti Aarnio, one of <postmaster at vger.kernel.org>
prev parent reply other threads:[~2010-01-31 23:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-31 4:13 Gene Heskett
2010-01-31 15:41 ` Matti Aarnio
2010-01-31 23:30 ` Matti Aarnio [this message]
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=20100131233001.GW3486@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®