From: Oleg Verych <olecom@flower.upol.cz>
To: Willy Tarreau <w@1wt.eu>
Cc: Matti Aarnio <matti.aarnio@zmailer.org>,
David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: Re: [OT] good job guys with the anti-spam !
Date: Sun, 2 Sep 2007 02:36:18 +0200 [thread overview]
Message-ID: <E1IRdRq-00015P-S4@flower> (raw)
In-Reply-To: <20070731214011.GA17735@1wt.eu>
* Tue, 31 Jul 2007 23:40:11 +0200
>
[]
> eventhough people often write only when they have something to complain
> about, I for once would like to congratulate Matti and David, our mail
> admins, for the wonderful job they've done with the spams lately. This
> month, I might have seen maybe one or two instead of perhaps 30 per day
> earlier. While it did not bother me that much earlier, I can say that
> the list is more pleasant to read every day, and I think that's great.
>
> Kudos guys !
>
> Willy
>
> PS: please do not start another one of those long useless threads from now on
>
Instead let me share an idea and see what will happen (if any).
The mailing list policy:
1. sent mails must have in-reply-to (rfc2821 SHOULD) with valid, i.e.
existing in archives, message-id;
2. otherwise sender gets response about creating new thread. Replying
to that message will enable (1).
I don't know how performance of ever increasing anti-spam
rules/software grow vs message-id lookup will be affected.
Gmane shows good performance on load, which is times bigger than LKML's.
News server requires unique ids, so...
Ah, if spammers will become smart and will reply with appropriate headers
set up, everything will fall apart.
Finally. What i see:
* no spam,
* big patch-bombs in one thread (easy to skip)
* more order, if useless/obsolete footers removed, but such info is
sent in (2).
* easy blacklisting if rules are not obeyed since day X
Oh, no, don't say we value bug reports. Reports must be organized in
other way, one of which i've described as development tracking system.
Such e-mail policy is unavoidable part of this it. E-mail is everything
it requires. Of course some html, css, javascript, perl guys will be
free to implement any web-face they like. But story if git-web have
something to learn instead.
--
-o--=O`C
#oo'L O
<___=E M
next prev parent reply other threads:[~2007-09-02 0:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 21:40 Willy Tarreau
2007-09-02 0:36 ` Oleg Verych [this message]
2007-09-02 0:39 ` Björn Steinbrink
2007-09-02 1:23 ` Oleg Verych
2007-09-02 8:18 ` Willy Tarreau
2007-09-02 15:15 ` Oleg Verych
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=E1IRdRq-00015P-S4@flower \
--to=olecom@flower.upol.cz \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.org \
--cc=w@1wt.eu \
/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
Powered by JetHome