Am Sonntag, 20. Juli 2025, 00:07:56 CEST schrieb Helmut K. C. Tessarek via dovecot:

On 2025-07-19 03:38, Paul Zirnik via dovecot wrote:

...

I never created "USER.sieve" or the link ".dovecot.sieve", this was done automatically when i activated my sieve script "mysieve.sieve" via an sieve editor.

This makes partly sense. The link always points to the activated sieve script. The .bin file is a binary "compiled" version of this script and recreated the first time it is accessed after making a change to the plain text sieve script.

The part that does not make sense is the USER.sieve script. You said you activated the mysieve.sieve script, in which case the link should point to it:

.dovecot.sieve -> .sieve/mysieve.sieve

If .dovecot.sieve points to the USER script, it means that this one is active and used.

Yes, but you can have more than one active sieve script. The USER.sieve is some kind of distributor that activates all your active scripts

$ cat .sieve/USER.sieve

USER Management Script

This script includes the various active sieve scripts

it is AUTOMATICALLY GENERATED. DO NOT EDIT MANUALLY!

For more information, see http://wiki.kolab.org/KEP:14#USER

require ["include"];

include :personal "mysieve";

But if i review the header, it looks like it probably is related to KDE (kmail or sieveeditor) which i use. Maybe this is a KDE only thing ? I never digged into this, as it just works since ages :-)

regards, Paul