From: "isoboroff@gmail.com" <isoboroff@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: Spam configuation and bogofilter
Date: Tue, 17 Jul 2007 12:08:43 -0000 [thread overview]
Message-ID: <1184674123.896182.33790@x35g2000prf.googlegroups.com> (raw)
In-Reply-To: <m2odibjt12.fsf@lifelogs.com>
On Jul 17, 5:09 am, Ted Zlatanov <t...@lifelogs.com> wrote:
> If that's fine, you need to set the spam-process group/topic parameter.
> There is a global variable if you don't want to use the group/topic
> parameter facility: gnus-spam-process-newsgroups. I would recommend
> using Customize on it at least the first time, so you get the format
> right, even if you won't use Customize later.
Some places in the Gnus manual aren't shy about giving the
syntax. ;-)
Also, maybe I just read the documentation wrong, but it seemed to me
that
that was the point of (setq gnus-use-bogofilter t). Why do I do this
at all?
At any rate, I think this was the key problem. Now misclassified
messages
are getting passed to bogofilter for training.
> I would suggest a different workflow:
Here's my implementation of your suggestion, which I think is right:
(spam-initialize)
(gnus-registry-initialize)
(setq spam-split-group "mail.spamgate"
spam-use-spamassassin-headers t
spam-use-bogofilter t
gnus-spam-process-newsgroups
'(("mail\\.*" ((spam spam-use-bogofilter))))
gnus-spam-newsgroup-contents
'(("mail.spamgate" 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 '(("mail\\.spamgate"
"mail.inbox"))
gnus-spam-process-destinations '(("mail\\..*"
"mail.spam.expired"))
spam-log-to-registry t
gnus-registry-max-entries 4000)
Thank you very much for your help!
Ian
next prev parent reply other threads:[~2007-07-17 12:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 18:15 isoboroff
2007-07-17 9:09 ` Ted Zlatanov
2007-07-17 12:08 ` isoboroff [this message]
2007-07-17 18:24 ` 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=1184674123.896182.33790@x35g2000prf.googlegroups.com \
--to=isoboroff@gmail.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).