• Cyrus Sieve server (timsieved) complains about size of Sieve scripts.

    Sieve scripts can get quite large, especially with the metadata that avelsieve saves together with the script.
    In Cyrus, you are advised to make the permitted Sieve script size bigger, in imapd.conf:
     # Maximum size (in kilobytes) any sieve script can be, enforced at
     # submission by timsieved(8).
    sieve_maxscriptsize: 32
    

    Changing the default size of 32 kb to 64 or 128 kb should be OK for most purposes.


  • Using a ManageSieve backend against a non-ManageSieve-enabled server.

    While it is possible to use the file storage backend, to store Sieve scripts in the filesystem, it might be more convenient to use a standalone ManageSieve server as a separate layer, and use the ManageSieve backend in avelsieve.

    You can use pysieved (Python Managesieve Server) to accomplish this.

    This way, you can use a ManageSieve interface to store scripts to be consumed by Exim, Dovecot, Postfix etc.