From: Mike Galbraith <efault@gmx.de>
To: Zach Brown <zach.brown@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: bogofilter ate 3/5
Date: Wed, 06 Sep 2006 07:22:47 +0000 [thread overview]
Message-ID: <1157527367.6199.9.camel@Homer.simpson.net> (raw)
In-Reply-To: <44FE5019.6010404@oracle.com>
On Tue, 2006-09-05 at 21:35 -0700, Zach Brown wrote:
> What should I have done to avoid the spam regexes and what should I do
> now that I have a patch that makes them angry?
Use language similar to the naughty stuff that is getting through?
Seriously though, a quote from Matti's lkml announcement:
IF we take it into use, it will start rejecting messages
at SMTP input phase, so if it rejects legitimate message,
you should get a bounce from your email provider's system.
(Or from zeus.kernel.org, which is vger's backup MX.)
In such case, send the bounce with some explanations to
<postmaster@vger.kernel.org> -- emails to that address
are explicitely excluded from all filtering!
next prev parent reply other threads:[~2006-09-06 5:12 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 23:57 [RFC 0/5] dio: clean up completion phase of direct_io_worker() Zach Brown
2006-09-05 23:57 ` [RFC 1/5] dio: centralize completion in dio_complete() Zach Brown
2006-09-05 23:57 ` [RFC 2/5] dio: call blk_run_address_space() once per op Zach Brown
2006-09-05 23:57 ` [RFC 3/5] dio: formalize bio counters as a dio reference count Zach Brown
2006-09-05 23:57 ` [RFC 4/5] dio: remove duplicate bio wait code Zach Brown
2006-09-05 23:57 ` [RFC 5/5] dio: only call aio_complete() after returning -EIOCBQUEUED Zach Brown
2006-09-06 4:35 ` bogofilter ate 3/5 Zach Brown
2006-09-06 5:00 ` Willy Tarreau
2006-09-06 7:22 ` Mike Galbraith [this message]
2006-09-08 22:16 ` Matthias Andree
2006-09-06 7:36 ` [RFC 0/5] dio: clean up completion phase of direct_io_worker() Suparna Bhattacharya
2006-09-06 16:36 ` Zach Brown
2006-09-06 14:57 ` Jeff Moyer
2006-09-06 16:46 ` Zach Brown
2006-09-06 18:13 ` Jeff Moyer
-- strict thread matches above, loose matches on Subject: below --
2006-09-06 5:37 bogofilter ate 3/5 Rick Ellis
2006-09-06 18:00 ` Willy Tarreau
2006-09-06 18:04 ` Willy Tarreau
2006-09-06 18:56 ` ellis
2006-09-06 19:15 ` Chase Venters
2006-09-06 20:56 ` Krzysztof Halasa
2006-09-06 22:05 ` Chase Venters
2006-09-07 11:55 ` Krzysztof Halasa
2006-09-07 13:46 ` Chase Venters
2006-09-07 22:33 ` Krzysztof Halasa
2006-09-07 22:37 ` Chase Venters
2006-09-07 22:58 ` Krzysztof Halasa
2006-09-07 23:02 ` Matti Aarnio
2006-09-07 13:58 ` Stuart MacDonald
2006-09-07 14:27 ` Chase Venters
2006-09-07 17:35 ` Stuart MacDonald
2006-09-07 18:25 ` Chase Venters
2006-09-07 21:05 ` Stuart MacDonald
2006-09-07 9:52 ` Matti Aarnio
2006-09-06 20:13 ` 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=1157527367.6199.9.camel@Homer.simpson.net \
--to=efault@gmx.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zach.brown@oracle.com \
/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