sieve: active= doesn't seem to use bindir=

[dovecot at ptld.com]

> I thought active was where to read the active source script from? I'm
> not using managesieve, so I wouldn't expect dovecot to try writing to
> that file. I don't see anything in
> https://doc.dovecot.org/configuration_manual/sieve/configuration/
> about active pointing at a compiled file, just stuff about it pointing
> at a source file.

Well yeah. The active= path tells dovecot to create a symlink pointing 
to the source file. But if you look at hidden files in that directory 
"ll -a" you will see a .svbin file was created with the symlink. I don't 
fully understand what is happening under the hood, i just know setting 
active works.