Re: spam.el: automatically resplitting ham in a spam group?

[lorentey@elte.hu (Lőrentey Károly)]

Ted Zlatanov <tzz@lifelogs.com> writes:
> That's not necessarily the only problem.  The real issue is that the
> destination is being decided dynamically, so every function in the
> splitting sequence would have to know that returning the name of the
> current group is not OK - we don't want the ham to stay in the spam
> group, no matter what.

Actually, in border cases, putting the ham right back to the spam
group is exactly what I would expect the respooling mechanism to do.

For example, with the following split rule, if I set the ham process
destination of mail.spam.silly-people to 'respool, I expect that all
ham in that group to reappear there after the resplit, each and every
time I exit that group:

	("from" "lorentey@.*elte\\.hu" "mail.spam.silly-people")

I expect the same from non-spam splitting functions.  I know, it's not
very useful, but at least it's not confusing either.

(Actually, the respool already puts ham back in a spam group sometimes
when I manually respool the articles in my mail.ham.proven group.  In
my case, disabling spam-split during the respool takes care of this
from now on, but I have not been bothered by this effect at all.)

-- 
Károly