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?
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 us
I've been running Cyrus-imapd on Mandriva Linux for a few years now
and all is well with the basic server. But sieveshell has never
worked despite various attempts.
For the new year, I'm making another attempt at getting sieve to work.
Sieveshell has problems, so I want to just manually put the