From: Jacques L'helgoualc'h <lhh@free.fr>
Subject: Re: spamassassin and gnus
Date: Fri, 29 Mar 2002 22:11:47 +0100 [thread overview]
Message-ID: <020329221147.gaston@lhh.free.fr> (raw)
In-Reply-To: <87r8m3m8x3.fsf@hackerhue.ddts.net>
Hubert Chan <hackerhue@geek.com> wrote:
[...]
> AFAICT, fancy splitting can call arbitrary functions with a buffer
> narrowed to the current message, so my strategy would be to grab the
> narrowed buffer, pipe it through spamassassin,
FWIW, I use the spam(c|d) client/server pair, which is much quicker
here.
--
Jacques L'helgoualc'h
next prev parent reply other threads:[~2002-03-29 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87g02row5j.fsf@hackerhue.ddts.net>
[not found] ` <m34rj77ynq.fsf@spirg.local>
[not found] ` <87d6xv544h.fsf@nomad.consult-meyers.com>
2002-03-27 14:58 ` Niels Langager Ellegaard
[not found] ` <a7qboa2oak@enews1.newsguy.com>
[not found] ` <87r8m3m8x3.fsf@hackerhue.ddts.net>
2002-03-29 21:11 ` Jacques L'helgoualc'h [this message]
2006-06-18 23:02 Hadron Quark
2006-06-19 14:51 ` Ted Zlatanov
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=020329221147.gaston@lhh.free.fr \
--to=lhh@free.fr \
/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).