Re: spam.el - ham in spam groups

["Ted Zlatanov" <tzz@lifelogs.com>]

On Wed, 16 Jun 2004, marcelo@marcelotoledo.org wrote:

> If I have ham in spam the solution I know nowdays is setting
> gnus-ham-process-destinations and moving it to my reclassify group. Like
> this:
> 
> (setq gnus-ham-process-destinations
>       '(("nnml:spam" "nnml:reclassify")))
> 
> normaly I've gone through all spam and marked all ham as read, so when I
> leave the group all the ham goes to nnml:reclassify, great, I get into
> the reclassify group and respool everything and then it should go to the
> correct groups.
> 
> I dont know if there is a reason for this but I think all this steps
> should't exist. If there is ham in spam it must be repooled again and
> not moved to another group that has nothing to do with.

You can do that if you wish by setting the ham-process-destination to
'respool.

A lot of people (including me) like to "clone" misclassified ham in a
"ham training" folder, which is much harder to do with the mechanism
you propose.  So respooling as an option is OK, but as the exclusive
mechanism isn't.

Generally the spam.el approach has been to allow everyone to do what
they want with moving spam/ham around.  The new spam.el is even more
liberal in this regard.  It has the "default" behavior which moves
spam out of everywhere and ham out of spam groups; "move-none" which
never moves anything; "move-all" which moves spam and ham regardless
of the group classification.  It is complicated but so are Gnus users
:)

Ted