On 3/12/2015 4:23 AM, E.B. wrote: > I'll check on 0.4.6 and report if I see anything interesting, > but I will assume for the moment that since personal scripts > work in 0.4.6 that this log info won't be there. It is correct that > there is no "sieve" file or directory in the user's home dir. This > wasn't a problem in 0.4.6. Is it a requirement? >> Well, since your config says the following: >> >> sieve = file:~/sieve;active=~/.dovecot.sieve >> >> It expects a sieve storage directory at ~/sieve (created when >> ManageSieve is used to upload a script). >> Also, a symbolic link pointing to the active script will be located at >> ~/.dovecot.sieve once a script is activated (i.e. through ManageSieve or >> doveadm sieve). >> >> I wonder how this would have worked before with 0.4.6. Is the >> ~/.dovecot.sieve a normal script file perhaps (rather than a symlink)? >> This would mean that the following config would work (e.g. if you don't >> use ManageSieve): >> >> sieve = file:~/.dovecot.sieve > The configuration for that was not of my doing (doesn't that mean > it shouldn't have shown up in doveconf -n?). Yes, the .sieve scripts > in user home are regular files. Strange 0.4.6 didn't mind this > situation, but seems easy to put the configuration right and move on.
Well, even though your config is a bit strange, Pigeonhole should recognize this rather than fail. I will fix this. Regards, Stephan.
