From: Lawrence Mitchell <wence@gmx.li>
To: ding@gnus.org
Subject: Re: Just shoot me now
Date: Wed, 22 Dec 2010 17:14:01 +0000 [thread overview]
Message-ID: <m3pqsthgrq.fsf@gmx.li> (raw)
In-Reply-To: <0hlj3hwxxz.fsf@news.eternal-september.org>
Richard Riley wrote:
[...]
> Abd just in case anyone is reading this, I still havent got an example
> of fancy splitting working, Here is my setup:-
> ,----
> | (setq spam-use-bogofilter t)
> | (setq spam-use-spamassassin t)
> |
> | (require 'spam)
> | (spam-initialize)
> |
> | (setq nnimap-split-inbox '("INBOX"))
This variable no longer exists in gnus. As of Lars' recent
nnimap rewrite.
You want:
(setq nnimap-split-methods 'nnimap-split-fancy)
> | (setq nnimap-split-fancy '(| (: spam-split) "INBOX"))
> |
> | (setq nnmail-split-inbox '("INBOX"))
Similarly here.
(setq nnmail-split-methods 'nnmail-split-fancy)
> | (setq nnmail-split-fancy '(| (: spam-split) "SYS-INBOX"))
> |
> | (setq spam-split-disabled nil)
> |
> | (setq spam-autodetect-recheck-messages nil)
> | (setq spam-mark-ham-unread-before-move-from-spam-group t)
> | (setq spam-mark-new-messages-in-spam-group-as-spam t)
> | (setq spam-split-group "Gnus-Spam")
> `----
> And no splitting is happening on the INBOX. I cant think what else might
> be inhibiting it so if no one can help I'll try, gulp, to debug it...
The manual hasn't been updated inline with the most recent set of
nnimap changes, maybe?
Cheers,
Lawrence
--
Lawrence Mitchell <wence@gmx.li>
next prev parent reply other threads:[~2010-12-22 17:14 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 22:29 What's wrong with this fancy split? Tommy Kelly
2010-12-21 22:41 ` Andreas Schwab
2010-12-21 23:50 ` Russ Allbery
2010-12-22 0:17 ` Tommy Kelly
2010-12-22 9:32 ` Andreas Schwab
2010-12-22 10:16 ` Steinar Bang
2010-12-22 10:28 ` Andreas Schwab
2010-12-22 10:35 ` Steinar Bang
2010-12-22 10:44 ` Andreas Schwab
2010-12-22 11:44 ` Bjørn Mork
2010-12-22 12:26 ` Tommy Kelly
2010-12-22 12:37 ` Tassilo Horn
2010-12-22 12:59 ` Tommy Kelly
2010-12-22 13:48 ` Steinar Bang
2010-12-22 16:10 ` Tommy Kelly
2010-12-22 17:46 ` Steinar Bang
2010-12-22 18:19 ` Tommy Kelly
2010-12-22 19:15 ` Steinar Bang
2010-12-22 19:53 ` Tommy Kelly
2010-12-22 22:12 ` Steinar Bang
2010-12-22 23:31 ` Tommy Kelly
2010-12-23 19:05 ` Steinar Bang
2010-12-22 15:39 ` Richard Riley
2010-12-22 12:34 ` Tommy Kelly
2010-12-22 0:13 ` Just shoot me now (was Re: What's wrong with this fancy split?) Tommy Kelly
2010-12-22 7:24 ` Just shoot me now Reiner Steib
2010-12-22 13:57 ` Richard Riley
2010-12-22 14:18 ` Tommy Kelly
2010-12-22 15:54 ` Sivaram Neelakantan
2010-12-22 16:30 ` Tommy Kelly
2010-12-22 16:54 ` Richard Riley
2010-12-22 17:12 ` Tommy Kelly
2010-12-22 17:14 ` Lawrence Mitchell [this message]
2010-12-22 17:43 ` Richard Riley
2010-12-22 18:07 ` Tommy Kelly
2010-12-22 22:40 ` Richard Riley
2010-12-22 19:25 ` Eric S Fraga
2010-12-22 7:26 ` Just shoot me now (was Re: What's wrong with this fancy split?) Richard Riley
2010-12-22 9:35 ` Andreas Schwab
2010-12-22 12:53 ` Tommy Kelly
2010-12-22 18:21 ` Adam Sjøgren
2010-12-22 19:12 ` Tommy Kelly
2010-12-22 19:44 ` Adam Sjøgren
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=m3pqsthgrq.fsf@gmx.li \
--to=wence@gmx.li \
--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).