Sieve bytecode vs plaintext configuration files

[emdeex]

Thanks! I'll look into this sievec utility.  I've found it in
/usr/lib/cryus-imapd/sievec

I guess I would use it like "sievec ~/.sieve ~/.sievebc"

It appears to generate the bytecode output correctly.  Is there any
way of testing the resulting file, apart from sending test emails to
the account?

On 2/15/07, Thomas Robers <robers at tutech.de> wrote:
> emdeex schrieb:
> [...]
> >
> > Is it that I can't just write plaintext .sieve files, that they have
> > to be bytecode?  If so, how can I do this without sieveshell?
>
> I don't really know, if plain text sieve files can still be used or not, but to
> make bytecode out of the plain text sieve files you can use the program
> sievec:
>
> root at imap:~ # sievec
> Syntax: sievec [-C <altconfig>] <filename> <outputfile>
>
> HTH Thomas
>