At 10:10 30.05.2001 -0400, Ken Murchison wrote:
>Harald Tveit Alvestrand wrote:
> >
> > Hello,
> > this may be naive, obvious or whatever, but here goes:
> >
> > Is there any log that shows the actions a SIEVE script took on my email?
> > The reason is, of course, that my email is business-critical, and I am just
> > going to start using SIEVE now. If I miswrite the filters, I would very
> > much like to know that I've messed up.
> >
> > Thanks for any info!
>
>Aside from putting logging/debugging info directly into the sieve source
>code, you could try using the sieve NOTIFY extension and possibly Jeremy
>Howard's notify_unix code. With this combo, you should (in theory) be
>able to have your sieve script log each action that it takes.
Ack.
It seems that source hackery is the only way to go, then. Not great.
If I do so, I will first fix a simple bug: the "no such mailbox" message
that Sieve logs to the eventlog does not contain the name of the mailbox
that did not exist.....
