Re: should gnus-registry.el be in the manual for Oort Gnus?

[Ted Zlatanov <tzz@lifelogs.com>]

On Fri, 02 Jan 2004, ding@daphne.gnuu.de wrote:

> Also sprach Ted Zlatanov <tzz@lifelogs.com>:
> 
>> - tracking of spam processor invocations
> 
> I know this isn't really spam.el-specific, but does that mean that
> one could force spam.el not to register a mail with bogofilter
> twice?

Yes, with registry tracking.  If you limit the number of registry
entries, however, you will eventually lose that tracking information.

I could add a flag to the registry "preferentially keep messages with
tracking information" if this is a problem.

> I'm still playing around with my spam.el-configuration.
> Actually I'd like to have something like this:
> 
- new mail arrives
- fancy splitting (with spam-split at the beginning)
- spam goes into "nnml:spam", everything else into it's folder
- ham in the spam group is un-registered and moved into a suitable
  nnml-group
- spam in any "normal" group is registered and moved to spam where it
  expires

I think your setup is almost exactly like mine, which is in the latest
Gnus manual.  Check mine out and let me know if something is unclear.

> Am I right about that re-registering of good mails when I classify
> all of my normal mail groups as ham or have I understood something
> wrong?

You're right, you would re-register without the gnus-registry
tracking.

> And that's where your registry comes into play? With that one could
> avoid this and classify almost everything as ham groups?

Yes.  I would advise, however, that you check registrations to make
sure things are working correctly.  They should, but it does not hurt
to be cautious.

> BTW, the spam.el-specific part of my .gnus begins thus:
> 
> (spam-initialize)
> (setq spam-install-hooks t)
> ;(spam-install-hooks-function)
> (setq spam-use-bogofilter t)
> (setq spam-mark-ham-unread-before-move-from-spam-group t)
> (require 'spam)
> 
> I think that the Info indicated that one should put in
> spam-install-hooks (which resulted in an error) before you
> commited your big doc patch.
> 
> So can I leave out everything except spam-initialize and
> spam-use-bogofilter?

This should be sufficient:

(setq spam-use-bogofilter t)
(setq spam-mark-ham-unread-before-move-from-spam-group t)
(spam-initialize)

Ted