On Fri, 2002-02-01 at 08:33, Earl R Shannon wrote:
> Hello,
>
> You have found what may be the biggest problems with free software.
> Documentation and Support. Sysadmins such as myself must take these
> issues into account when deciding upon a platform to use for delivery
> of services such as e
Lawrence Greenfield wrote:
>
>Date: Sun, 10 Feb 2002 17:20:03 -0800
>From: Erik Steffl <[EMAIL PROTECTED]>
> [...]
>> We currently use yacc (or bison) to parse Sieve scripts; the bytecode
>> work isn't currently expected to change this. We basically report the
>> parse errors
Hello,
You have found what may be the biggest problems with free software.
Documentation and Support. Sysadmins such as myself must take these
issues into account when deciding upon a platform to use for delivery
of services such as email. Using a package such as Cyrus requires a
somewhat higher
> On Sun, 10 Feb 2002 22:06:30 -0500,
> Lawrence Greenfield <[EMAIL PROTECTED]> (lg) writes:
lg> Sieve's formal grammar is not particularly difficult; it really isn't
lg> very hard to write a program that correctly generates scripts.
Speaking of which, I don't suppose anybody has done a
Date: Sun, 10 Feb 2002 17:20:03 -0800
From: Erik Steffl <[EMAIL PROTECTED]>
[...]
> We currently use yacc (or bison) to parse Sieve scripts; the bytecode
> work isn't currently expected to change this. We basically report the
> parse errors that Yacc gives us.
it often does r
Lawrence Greenfield wrote:
>
>From: Amos Gouaux <[EMAIL PROTECTED]>
>Date: Sat, 09 Feb 2002 09:01:15 -0600
> [...]
>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.
>
> We
From: Amos Gouaux <[EMAIL PROTECTED]>
Date: Sat, 09 Feb 2002 09:01:15 -0600
[...]
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.
We currently use yacc (or bison) to parse Sieve s
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
> 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 (
cyrus and related programs are some of the hardest programs to
troubleshoot I ever encountered. I read the docs, asked on the mailing
list (this one) etc. but it seems like there's simply no way to tell
what's going on. I enabled all the logging, I even tried test (from
sieve directory of cyrus
10 matches
Mail list logo
