Gnus development mailing list
 help / color / mirror / Atom feed
From: Jody Klymak <jklymak@coas.oregonstate.edu>
Cc: ding@gnus.org
Subject: Re: How to configure the spam mailbox
Date: Wed, 29 Oct 2003 13:38:13 -0800	[thread overview]
Message-ID: <uoevzpvwa.fsf@coas.oregonstate.edu> (raw)
In-Reply-To: <76llr3srgn.fsf@newjersey.ppllc.com> (Jake Colman's message of "Wed, 29 Oct 2003 15:45:44 -0500")

Hi Jake,

Jake Colman <colman@ppllc.com> writes:

> As bogofilter gets trained it is starting to file articles directly into the
> spam mailbox.  How should this box be configured?  Is it already set up to be
> auto-expired?  Or do I have to do that myself?  Do I have set any spam
> variables in the group's config?  I'd assume not since spam.el already knows
> that it is spam.  How do I tell spam.el and bogofilter that a message the
> spam mailbox is really ham?

I do this - mostly using Groups-Customize:

1) Make sure that both gnus-group-spam-exit-processor-bogofilter and
   gnus-group-ham-exit-processor-bogofilter are set.
2) I set Destination for ham articles to be my Inbox.
3) set Ham mark choices to what you feel is appropriate - I use
   gnus-read-mark and gnus-ticked mark.  
4) I set expire wait to immediate.  Umm, maybe thats dumb.  But it
   stops the spam in the group from being bogofiltered every time I
   exit it.  I don't think there is any reason to send a message to
   bogofilter more than once if you can help it.  Maybe the registry
   fixes this now.  
5) I set Total Expire for this group.

This works for me.  

Cheers,  Jody

-- 
Jody Klymak      http://mixing.coas.oregonstate.edu/people/jklymak/
mailto:jklymak@coas.oregonstate.edu   




      reply	other threads:[~2003-10-29 21:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-29 20:45 Jake Colman
2003-10-29 21:38 ` Jody Klymak [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=uoevzpvwa.fsf@coas.oregonstate.edu \
    --to=jklymak@coas.oregonstate.edu \
    --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).