From: "Peter G" <nyhedsgrupper@gmx.com>
To: info-gnus-english@gnu.org
Subject: Gnus registry permanence and spam-log-to-registry
Date: Mon, 22 Mar 2010 10:01:53 +0100 [thread overview]
Message-ID: <87tys8lofy.fsf@nifty.my-fqdn.de> (raw)
I'm trying to set up the spam.el package in my .gnus.el, so that I'm
going to have simple spam-handling.
My current setup is almost working, save for the simple problem that
everytime I first start up gnus in emacs, I'm being interactively
prompted whether i eant to "enable the gnus registry" and that I have to
look into 'gnus-registry-install' if I want it to be set permanent.
Problem is, I already have set 'gnus-registry-install'. So what am I
missing?
Relevant part of .gnus.el:
(require 'gnus-registry)
(gnus-registry-initialize)
(setq gnus-registry-install t
gnus-registry-max-entries 20000)
(require 'spam)
(spam-initialize)
(setq spam-split-group "nnimap+HOME:INBOX.spam"
spam-use-spamassassin-headers t
spam-use-bogofilter t
spam-log-to-registry t
gnus-spam-process-newsgroups
'(("nnimap+.*" ((spam spam-use-bogofilter))))
gnus-spam-newsgroup-contents
'(("nnimap+HOME:INBOX.spam" gnus-group-spam-classification-spam))
spam-mark-only-unseen-as-spam t
spam-mark-ham-unread-before-move-spam-from-group t
gnus-ham-process-destinations '(("nnimap+HOME:INBOX.spam"
"nnimap+HOME:INBOX"))
gnus-spam-process-destinations '(("nnimap+.*"
"nnimap+HOME:INBOX.Trash")))
(setq nnimap-split-rule 'nnimap-split-fancy
;; understand what this does before you copy it to your own setup!
nnimap-split-fancy '(|
;; trace references to parents and put in their group
(: gnus-registry-split-fancy-with-parent)
;; note that spam by default will go to `nnimap+HOME:INBOX.spam'
(: spam-split)))
--
Mvh./Regards, Peter.
Please, do not toppost.
next reply other threads:[~2010-03-22 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 9:01 Peter G [this message]
2010-03-22 13:05 ` Ted Zlatanov
2010-03-22 14:31 ` Ted Zlatanov
2010-03-22 17:50 ` Peter G
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=87tys8lofy.fsf@nifty.my-fqdn.de \
--to=nyhedsgrupper@gmx.com \
--cc=info-gnus-english@gnu.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).