Amos Gouaux wrote:
>
> >>>>> On Fri, 01 Feb 2002 01:00:22 -0800,
> >>>>> Erik Steffl <[EMAIL PROTECTED]> (es) writes:
>
> es> Q: how do other people cope with troubleshooting problems of cyrus
> es> (and mainly sieve)? Are there any tools that I am not aware of? Is it
> es> getting better (the above is with older cyrus/sieve (test is from
> es> 2.0.16, real sieve from 1.6.x, but says 2.0 in X-sieve header).
>
> In the source distribution you'll find a test.c in the sieve
> directory. Try compiling that and run it with a "-v" against your
> sieve script, as in:
>
> ./test -v default.script
tried that and it's a nightmare - there are no (useful) error messages
in number of cases, sometime it's basically impossible to find out what
the problem is even when debugging (if the problem is in parser).
> I believe there is activity going on at CMU to create a byte
> compiler for Sieve scripts. Perhaps that will be a bit more verbose
> about script errors.
thanks for the hope:-)
erik
