Bug#423221: sieve script error [SOLVED, but possible doc issues]

[Ross Boylan]

On Thu, May 10, 2007 at 08:15:45PM +0200, Sven Mueller wrote:
> Ross Boylan wrote on 10/05/2007 19:51:
> 
> >I tried installsieve -i but got "upload failed."
> >
> >The man page for installsieve notes that "sieve names may not contain
> >a '.'", so I tried a name without a '.'.  It didn't help.  The man
> >page is confusing: the quoted phrase sounds as if all '.' are out, but
> >the immediately preceding discussion is only about names ending in
> >'.script'.
> >  
> >
> 
> In my experience, the sievescript names _should_ not _start_ with a dot.

What problems does that lead to?

> A dot somewhere in
> the script name is no problem though.
> 
> Could you please try compiling your sieve script using sievec?
> 
> /usr/lib/cyrus/bin/sievec <your_script> /tmp/sieve.bc
> 
> If your script doesn't issue an error there, we need to dig into
> sieveshell/installsieve to find
> the problem there. However if sievec returns an error, your script is
> wrong in some aspect.

My script had a stupid typo.  Thank you; all seems to be well now.

There are a couple of possible documentation matters that might help
others:

The error message 
"Unable to parse script: script errors:
line 36: syntax error, unexpected $undefined"
would be clearer if it said "Unable to parse YOUR SIEVE script..."
(uppercase just to indicate addition).  A file name in front of the
line number would help to, though I suppose that might be harder to
track.  The actual undefined token would also be useful output.

The discussion of '.' in script names in installsieve could be
clarified, and that information put elsewhere it is relevant (e.g.,
sieveshell and/or more general documents).  Perhaps it's already there
and I missed it.

Ross