From: Xavier MAILLARD <zedek@gnu-rox.org>
Cc: ding@hpc.uh.edu
Subject: Re: spam filtering by bayesian classifier and imap - ideas
Date: Mon, 20 Jan 2003 22:19:21 +0100 [thread overview]
Message-ID: <plop8765sjy0x2.fsf@gnu-rox.org> (raw)
In-Reply-To: <m33cno2neo.fsf@mail.contactor.se> (Mats Lidell's message of "Mon, 20 Jan 2003 10:14:39 +0100")
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
On Mon, 20 Jan 2003, Mats Lidell stated:
>>>>> asf wrote:
>
> asf> 2. Use gnus and nnimap-split-fancy to split mail into the
> asf> correct groups.
>
> I use procmail so that the splitting also is done on the server. YMMW
> but it is nice and fast to have the splitting in just one place. No
> need to update the splitting rules on different locations and makes
> it possible to on occasions use other MUAs without to many
> consequences.
IMHO there is absolutely no need to use another MUA :)
zeDek
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2003-01-20 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-19 10:59 Andreas Fuchs
2003-01-19 14:13 ` Kai Großjohann
2003-01-19 20:34 ` Xavier MAILLARD
2003-01-20 9:14 ` Mats Lidell
2003-01-20 21:19 ` Xavier MAILLARD [this message]
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=plop8765sjy0x2.fsf@gnu-rox.org \
--to=zedek@gnu-rox.org \
--cc=ding@hpc.uh.edu \
/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).