Re: Add hooks to Gnus on move/edit/delete?

[kai.grossjohann@uni-duisburg.de (Kai Großjohann)]

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Sun, 29 Dec 2002, kai.grossjohann@uni-duisburg.de wrote:
>> First of all, ifile-gnus.el now uses a different mechanism for
>> communicating with the backend, and the new mechanism works for more
>> than one backend.
>
> Is this released, and does it work with nnimap?  I haven't followed
> ifile-gnus.el, unfortunately, due to lack of time.

I think it might work if you use nnimap splitting.  If you use Sieve
or procmail, then it could be difficult, since the ifile database
would be on your local host in the home dir, whereas the
Sieve/procmail rules are on the IMAP server.

> So if ifile-spam-filter could and should be replaced with another
> ifile-gnus.el function that returns regular group names, spam.el can
> do all the ifile classification automatically if the user just sets
> spam-use-ifile to t.
>
> Does that sound reasonable?

I'm not sure.  How do I tell spam.el which group a message is in?  If
ifile has chosen the group wrongly, how do I tell it about the error?

ifile-gnus intercepts move and copy operations to see that.  So
designating a message as spam works by moving it to the spam group.

Maybe a two-stage process is better: first decide whether it's spam
or not, then distribute the non-spam to the right groups.

But then, there is Gmane, which makes a lot of splitting unnecessary :-)

-- 
Ambibibentists unite!