From: Oleg Verych <olecom@flower.upol.cz>
To: Bj?rn Steinbrink <B.Steinbrink@gmx.de>
Cc: Willy Tarreau <w@1wt.eu>, 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 03:23:53 +0200 [thread overview]
Message-ID: <20070902012353.GC475@flower.upol.cz> (raw)
In-Reply-To: <20070902003936.GA8005@atjola.homenet>
On Sun, Sep 02, 2007 at 02:39:36AM +0200, Bj?rn Steinbrink wrote:
[]
>
> Ehrm, you want everyone who wants to start a new thread to:
>
> - send an email
> - await response from the mail server
> - send the same email again as a reply to the first one
No. Send a ticket request and then organize patch bomb with gotten ticket
in `references:' or `in-reply-to'. New discussion thread: be organized
have a pull of tickets, care about what you post, how you post, etc.
Those new posters will get current footer with more info -- no problem.
People in thread need no work at all. Linus, Andrew, Jeff, DaveM etc.
are likely to be in white list with no additional work also.
It's anti-spam thing, but maybe it can be kind of netiquette, which is
forgotten in modern XML Internet world. I didn't live in that time, but
that's my impression. In case if efficient algo/logic will be implemented
it will save CPU power, because all processing is done in header part of
the message and it's a token lookup. Switch on your imagination and
think, what can be done in another way, why not?
____
next prev parent reply other threads:[~2007-09-02 1:09 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
2007-09-02 0:39 ` Björn Steinbrink
2007-09-02 1:23 ` Oleg Verych [this message]
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=20070902012353.GC475@flower.upol.cz \
--to=olecom@flower.upol.cz \
--cc=B.Steinbrink@gmx.de \
--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