From: "Jörn Engel" <joern@logfs.org>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: linux-mm@kvack.org
Subject: Re: test
Date: Thu, 18 Dec 2008 12:40:20 +0100 [thread overview]
Message-ID: <20081218114020.GA17966@logfs.org> (raw)
In-Reply-To: <20081218010343.GC23506@kvack.org>
On Wed, 17 December 2008 20:03:43 -0500, Benjamin LaHaise wrote:
>
> > Any chance that kvack can set either X-BeenThere: or X-Mailing-List: as
> > almost every other mailing list (the ppc ones set X-Original-To, alas)
> > does?
>
> I don't see the point in adding it when the Sender: header works fine for
> me. Right now I'm more worried about the state of the spam filtering.
Maybe I'm a special kid. I have two filters for mailing lists. The
first simply tries to detect whether the mail comes from _any_ mailing
list. The second then sorts it into the appropriate mailbox. Anything
left over goes into unsorted (95% spam) or list/unsorted (<1% spam) if
it matched the generic mailing list rule, but no specific one.
list/unsorted usually fills up after subscribing to a new list or when
something changed. Not having all the spam mixed in is nice.
My rule to detect mailing lists is this:
* ^(X-Mailing-List:|X-BeenThere:|X-Original-To:|Original-Recipient:|X-Loop:)
If it weren't for kvack.org and ozlabs.org, it could be just this:
* ^(X-Mailing-List:|X-BeenThere:)
Not exactly the most important issue for humanity, that's for sure. :)
JA?rn
--
There's nothing that will change someone's moral outlook quicker
than cash in large sums.
-- Larry Flynt
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-12-18 11:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 19:23 test Benjamin LaHaise
2008-12-17 15:33 ` test Jörn Engel
2008-12-17 16:52 ` test Benjamin LaHaise
2008-12-17 18:34 ` test Jörn Engel
2008-12-18 1:03 ` test Benjamin LaHaise
2008-12-18 11:40 ` Jörn Engel [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-04 11:29 test bcrl
2013-10-09 15:42 test Johannes Weiner
2012-06-15 9:20 test FuXin Li
2010-08-25 10:36 test Benjamin LaHaise
2008-12-18 0:58 test Benjamin LaHaise
2008-11-24 20:45 test Benjamin LaHaise
2001-08-13 1:45 test Ben LaHaise
2000-12-29 20:28 test foo
1999-08-16 18:47 test Benjamin LaHaise
1999-06-06 17:39 test Benjamin LaHaise
1999-05-04 14:52 test Benjamin LaHaise
1999-01-19 6:47 test blah
1998-12-25 15:45 test Rik van Riel
1997-12-18 16:18 test Benjamin C.R. LaHaise
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=20081218114020.GA17966@logfs.org \
--to=joern@logfs.org \
--cc=bcrl@kvack.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).