compiled sieve files svbin ?
jeremy ardley
jeremy at ardley.org
Wed Nov 23 12:34:05 UTC 2022
Hi,
I have recently started using claws mail to manage my user sieve scripts
using server dovecot-sieve_1%3a2.3.13+dfsg1-2_arm64.deb
I originally edited ~/.dovecot.sieve to hold my script and I recall that
~/.dovecot.svbin was automatically generated on first use. (either that
or I have forgotten that I had used sievec)
Later I used claws mail to generate sieve scripts but they were written
into directory
~/sieve/
In experimentation I changed ~/.dovecot.sieve into a link to my
principal script ~/sieve/main.sieve
The oddity now is that sieve seems to be working when there is no
compiled version
Should I expect a compiled .svbin version to be generated from claws
client? Or generated by first run of the sieve server on the user
account? Or should I manage the scripts with claws, but log in to the
server later to generate the .svbin versions?
In any event what effect does not having a .svbin version have on
typical small installation?
--
Jeremy
More information about the dovecot
mailing list