Since it took some time to get my dovecot working with sieve i post this note here so people using google/forum-search dont have to debug the whole thing again.
In previous versions (Syscp-Times for me) using server side mail filtering/sorting/... (sieve) and its remote management (managesieve) could easily be configured using the Dovecot-documentation. On my new server authentication on managesieve always failed:
This is related to froxlor's new dovecot<->sql-connection. The newer dovecot-sql.conf now checks if a User is allowed to use the tried protocol:
password_query = ? WHERE (username = '%u' OR email = '%u') AND ((imap = 1 AND '%Ls' = 'imap') OR (pop3 = 1 AND '%Ls' = 'pop3') OR '%Ls' = 'smtp')"
so you have to allow managesieve - in my example for all users:
password_query = "SELECT username AS user, password_enc AS password, homedir AS userdb_home, uid AS userdb_uid, gid AS userdb_gid, CONCAT('*:storage=', quota,'M') AS userdb_quota_rule, concat('maildir:', maildir) AS userdb_mail FROM mail_users WHERE (username = '%u' OR email = '%u') AND ((imap = 1 AND '%Ls' = 'imap') OR (pop3 = 1 AND '%Ls' = 'pop3') OR '%Ls' = 'smtp')"
Question
adlerweb
Since it took some time to get my dovecot working with sieve i post this note here so people using google/forum-search dont have to debug the whole thing again.
In previous versions (Syscp-Times for me) using server side mail filtering/sorting/... (sieve) and its remote management (managesieve) could easily be configured using the Dovecot-documentation. On my new server authentication on managesieve always failed:
Client:
Server:
This is related to froxlor's new dovecot<->sql-connection. The newer dovecot-sql.conf now checks if a User is allowed to use the tried protocol:
so you have to allow managesieve - in my example for all users:
(0.9.16)
Link to comment
Share on other sites
1 answer to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.