Hi all,

ok, I believe that I may have fixed this in the config file. It looks like there may just be a difference in how the newer pigeonhole software checks for the link. I think in the old version it used the link and did not check it against what the config was...

I simply changed the sieve_dir = ~/Maildir/sieve and it stopped having that error and worked properly...

Maybe the new version is just more picky that everything lines up properly...

Thanks,

Tim.

On 6/14/2010 5:32 PM, Tim Traver wrote:

Hi all,

ok, I am updating to the 2.0 way of doing things and have managed to get everything set up right, except I am getting the following errors when attempting to use managesieve with our webmail client (roundcube) that I didnt get when using dovecot 1.2.11...

Jun 14 17:20:33 managesieve(address@domain.com): Warning: sieve-storage: Active sieve script symlink /home/mailboxes/data/domain/348/address@domain.com/.dovecot.sieve is broken: invalid/unknown path to storage (points to Maildir/sieve/roundcube.sieve).

I checked, and the link appears to be there, and is a proper symlink to the sieve file...

Here is the copy of my dovecot -n :

# 2.0.beta6: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 8.0-RELEASE-p3 i386 auth_username_format = %Lu auth_username_translation = %@ auth_verbose = yes disable_plaintext_auth = no dotlock_use_excl = yes first_valid_uid = 100 listen = * lock_method = dotlock log_path = /local/logs/dovecot.errors mail_gid = 100 mail_location = maildir:%h/Maildir mail_nfs_index = yes mail_nfs_storage = yes mail_uid = 100 mmap_disable = yes passdb { args = /bin/checkpassword_dovecot_auth driver = checkpassword } plugin { quota = maildir sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 managesieve quota_full_tempfail = yes ssl_cert =