From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Gnus and Outlook and spam?
Date: Mon, 27 Oct 2003 15:59:28 -0500 [thread overview]
Message-ID: <4n1xsycs7j.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <76llraep1k.fsf@newjersey.ppllc.com> (Jake Colman's message of "Fri, 24 Oct 2003 09:35:51 -0400")
On Fri, 24 Oct 2003, colman@ppllc.com wrote:
>>>>>> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:
>
> TZ> On Thu, 23 Oct 2003, colman@ppllc.com wrote:
> >> But spam-stats is not for nnimap, if I read it correctly.
>
> TZ> I think it will work for any backend. If not, we can fix
> TZ> that - report any bugs you find.
>
> I'm glad to hear that but I think the info file for the latest
> official release of gnus (v5.10.2) says otherwise.
Please point that out. You may be referring to the note for IMAP
users, which relates to statistical filters, but that's not a problem
with IMAP per se, it's just a setting (nnimap-split-download-body)
that you need to turn on.
> BTW does 5.10.2 have good support for spam.el or do I need to use
> the latest version from cvs?
spam.el is a work in progress. Don't use CVS if you don't want to -
but the CVS version is always the one with more old bugs fixed and
more features (it may have new bugs, but I try not to repeat the old
ones :)
> If spam-stats works with nnimap should I just use it or would
> bogofilter, if I don't mind installing it, be a better choice?
This is entirely up to you. They are two different tools with
different algorithms and advantages. spam.el tries to accomodate
both, but the choice is yours.
> ;; nnimap split rules
>
> (setq nnimap-split-inbox "INBOX")
> (setq nnimap-split-crosspost nil)
> (setq nnimap-split-rule
> '(
> ; Emacs
> ("INBOX/Emacs/Help"
> "^To:.*help-gnu-emacs\\|^Resent-From:.*help-gnu-emacs\\|^Cc:.*help-gnu-emacs")
> ("INBOX/Emacs/Gnus"
> "^Resent-From:.*info-gnus-english\\|^To:.*info-gnus-english")
> ...
> ...
> ...
> ("INBOX/Misc" "")
> ))
>
> How do I convert from this to what I need to do to use bogofilter?
;; this is a very rough approximation, read the fancy splitting docs
;; if you want to know more
(setq nnimap-split-fancy
'(|
(any "help-gnu-emacs" "INBOX/Emacs/Help")
(any "info-gnus-english" "INBOX/Emacs/Gnus")
...
...
...
...
(: spam-split)
("INBOX/Misc")))
(setq spam-use-bogofilter t)
(spam-initialize)
Ted
next prev parent reply other threads:[~2003-10-27 20:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 20:58 Kai Grossjohann
2003-10-23 0:55 ` Jody Klymak
2003-10-23 16:06 ` Ted Zlatanov
2003-10-23 16:22 ` Jake Colman
2003-10-23 17:38 ` Ted Zlatanov
2003-10-23 17:42 ` Jake Colman
2003-10-23 19:29 ` Ted Zlatanov
2003-10-24 13:35 ` Jake Colman
2003-10-27 20:59 ` Ted Zlatanov [this message]
2003-10-28 15:25 ` Jake Colman
2003-10-28 15:57 ` Ted Zlatanov
2003-10-23 22:31 ` Danny Siu
2003-10-23 19:38 ` spam.el and IMAP (was: Gnus and Outlook and spam?) Reiner Steib
2003-10-23 22:00 ` spam.el and IMAP Ted Zlatanov
2003-10-24 12:53 ` Reiner Steib
2003-10-24 13:55 ` Adrian Lanz
2003-10-26 12:41 ` Adrian Lanz
2003-10-27 7:30 ` Adrian Lanz
2003-10-27 23:34 ` Ted Zlatanov
2003-10-27 8:23 ` Adrian Lanz
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=4n1xsycs7j.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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).