From: Willy Tarreau <willy@w.ods.org>
To: John Bradford <john@grabjohn.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OT] Re: ATTACK TO MY SYSTEM
Date: Wed, 24 Sep 2003 10:46:16 +0200 [thread overview]
Message-ID: <20030924084616.GA16727@alpha.home.local> (raw)
In-Reply-To: <200309240740.h8O7eZNI000474@81-2-122-30.bradfords.org.uk>
On Wed, Sep 24, 2003 at 08:40:35AM +0100, John Bradford wrote:
> RFC 822, section 3.4.7, makes clear that case is _not_ significant for
> these field names. RFC 2822 doesn't change this.
Sorry John about the mis-information. Of course case is not significant,
otherwise we would simply not receive these mails. I should have said
"common usage" and not "protocols", since I really thought the former
eventhough I wrote the later.
> Just because no commonly used E-Mail application seems to generate
> uppercase field names, how do you know something like a password
> auto-responder script won't?
I don't know. It's only an empirical choice based on observations. Many of us
are more concerned by hundreds of mails a day than risking to get a rare
false-positive. But I agree, I should have been clearer.
I have nearly the same .procmailrc as the one Joern Engel proposed :
:0 D
* ^FORM:
spam/swen
And I too agree that I have 0% false positive so far. But just like any filter,
use at your own risk...
Willy
next prev parent reply other threads:[~2003-09-24 8:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 7:40 [OT] Re: ATTACK TO MY SYSTEM John Bradford
2003-09-24 8:46 ` Willy Tarreau [this message]
2003-09-24 8:59 ` Jörn Engel
-- strict thread matches above, loose matches on Subject: below --
2003-09-23 10:01 Mike Galbraith
2003-09-23 13:40 ` J.A. Magallon
2003-09-23 14:43 ` [OT] " Steven Cole
2003-09-23 15:50 ` Wakko Warner
2003-09-23 19:24 ` Wade
2003-09-23 20:06 ` Willy Tarreau
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=20030924084616.GA16727@alpha.home.local \
--to=willy@w.ods.org \
--cc=john@grabjohn.com \
--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