-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 16 Aug 2007, Stephan Bosch wrote:
I have updated the MANAGESIEVE patch to (hopefully) fix the compilation issues reported by Robin Breathe. This is a patch against the latest stable release 1.0.3. It currently won't compile with 1.1 due to
I have the problem that, if I do not explicitly set
login_dir = /var/run/dovecot/loginManagesieve-login dies with: dovecot: Aug 17 16:01:18 Error: managesieve-login: chroot(login) failed: No such file or directory dovecot: Aug 17 16:01:18 Error: managesieve-login: chroot(login) failed: No such file or directory dovecot: Aug 17 16:01:18 Error: managesieve-login: chroot(login) failed: No such file or directory dovecot: Aug 17 16:01:18 Error: child 11480 (login) returned error 89 dovecot: Aug 17 16:01:18 Error: child 11481 (login) returned error 89 dovecot: Aug 17 16:01:18 Error: child 11482 (login) returned error 89
There is the default run-directory missing, I guess. If I start the command from command line, it uses /usr/local/dovecot-1.0.3/var/run/dovecot/login - however the base directory does not exists.
I did not explicitly assigned login_dir in the .conf:
Some settings of dovecot -n
# 1.0.3: /usr/local/dovecot-1.0.3/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot/dovecot.log protocols: imap imaps pop3 pop3s managesieve login_dir(default): /var/run/dovecot//login login_dir(imap): /var/run/dovecot//login login_dir(pop3): /var/run/dovecot//login login_dir(managesieve): /var/run/dovecot/login Note the difference of the last two lines (double slash)!
Secondly, I suggest to add to the README.managesieve, that the server is using the CONTROL= directory to store the sieve scripts and that you can set mail_location= to change that, e.g.:
protocol managesieve { # Without the login_dir managesieve-login fails to start up login_dir = /var/run/dovecot/login listen = *:2000 # Otherwise the Sieve scripts would be placed into the CONTROL= dir mail_location = maildir:%h/Maildir }
Bye.
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iQEVAwUBRsWs1C9SORjhbDpvAQKAagf/YQta9xt1iEdzZDL+eUjEsVWX6uWwjFkC Ge8AH85u4AOghBS8GrsVGPTyAGJP7T+wtwLjiPZI+/PVkWnQkVNYcOfMAmQRzcWl vHhWhWgMKCHpZGsRrnmK+IzjK9IYSqQ9ApR5V7YXDHWfag6dhmvUjL4sD287o9EJ Ssl/KkpZ1c3HPFp4GCxepxtoQXoTu9dl+wfUytYleKnh3kBN1zRy0nhxYzEsVkUO B2aJzk0BoAy3DS5E2H3+clB1d013TzbjFotibmIs8kVzSsfkTkqlDPTxodjTUg2c heV8S1ZQFq2+S50uvbCH7Lh4uaAEnr/9UKylqiOEtp1pcS9vMJUIXg== =rgxC -----END PGP SIGNATURE-----