Stephan Bosch <step...@rename-it.nl> wrote: > > Oct 20 20:10:39 managesieve-login: Info: Login: user=<anme...@anup.de>, > > method=CRAM-MD5, rip=127.0.0.1, lip=127.0.0.1, mpid=1898, secured > > Oct 20 20:10:39 managesieve(anme...@anup.de): Warning: sieve-storage: > > Active sieve script symlink > > /var/spool/vhosts/anup.de/anmeyer/.dovecot.sieve is broken: invalid/unknown > > path to storage (points to > > /var/spool/vhosts/anup.de/anmeyer/.sieve/banane.sieve). > > Oct 20 20:10:39 managesieve(anme...@anup.de): Warning: sieve-storage: > > Active sieve script symlink > > /var/spool/vhosts/anup.de/anmeyer/.dovecot.sieve is broken: invalid/unknown > > path to storage (points to > > /var/spool/vhosts/anup.de/anmeyer/.sieve/banane.sieve). > > Oct 20 20:10:39 managesieve(anme...@anup.de): Info: Disconnected: Logged > > out bytes=52/1565 > > This looks like a bug to me. Could you try to set: > > sieve_dir = ~/.sieve/ > > (notice the slash at the end) > > Does it stop complaining now?
well allright, that seems to solve the problem. No complains anymore so far about the broken symlink. > Regards, > > Stephan. Thank you so much! Andreas
