- dovecot - dovecot.org

[Dovecot] Unknown password scheme SSHA512
by Patrick Westenberg 24 Jul '10

24 Jul '10

Hello, I installed dovecot via Debians apt package manager. The passwords are stored as SHA256 hash in a PostgreSQL database. default_pass_scheme in dovecot-sql.conf is set to SHA256. However, smtp-auth fails. Jul 24 00:31:07 smtp01 dovecot: auth(default): sql(mail(a)jasbafliesen.de): Unknown password scheme SHA256 Can anybody help me? Regards Patrick

2 2

Re: [Dovecot] SSL / TLS Problem
by Leander S. 23 Jul '10

23 Jul '10

Am 23.07.10 02:59, schrieb Andrew Bruce: > eel free to post this to the running conversation on the list (strip my > email address from this email though please) The issue was a case sensitive typo. When Setting up your Thunderbird don't type in eMail Addresses & Usernames including uppercase letters! DON'T: User(a)Domain.tld BUT therefore: user(a)domain.tld I faced that Problem only when I was using dyndns as domain service provider.

3 5

[Dovecot] Shared folders issue
by Emmanuel Gonzalez Carmona 23 Jul '10

23 Jul '10

Hello guys, I have an issue with shared folders: 1) The USERA shares his INBOX with USERB 2) USERB subscribes the USERA share without problems. 3) USERA deletes all his / or some directories from his INBOX (Trash, Drafts and Sent) 4) USERA logouts and makes login, so dovecot recreates the folders. 5) USERB gains access to subscrive those folders (Trash, Drafts and Sent) this is my namespace configuration: ... namespace private { separator = / prefix = inbox = yes #list = yes #subscriptions = yes } namespace shared { separator = / prefix = "shared/%%u/" location = maildir:/maildirs/%%d/%%u/Maildir subscriptions = no list = children } ... any ideas? Thanx in advance. -- Emmanuel Gonzalez Babel S.r.l. - http://www.babel.it <http://www.babel.it/>

2 1

[Dovecot] Go Away Message after the first successful login on proxy server
by Tomislav Mihalicek 23 Jul '10

23 Jul '10

hello i have a dovecot 1.2.11 and i have implementation of 2 dovecot machines, one proxy one storage part. everything is working fine, i only have one question regarding the message that should go away after the first successful login on proxy server. how to remove it on proxy server? May 7 16:04:19 proxy-server dovecot: pop3-login: proxy(tmihal(a)example.com): started proxying to 192.168.1.100:110: user=<tmihal(a)example.com>, method=PLAIN, rip=192.168.22.222, lip=192.168.1.100:109 [root@dougie:/usr/local/src/dovecot-1.2-managesieve]/etc/init.d/dovecot restart Restarting DovecotIf you have trouble with authentication failures, enable auth_debug setting. See http://wiki.dovecot.org/WhyDoesItNotWork This message goes away after the first successful login. -- View this message in context: http://old.nabble.com/Go-Away-Message-after-the-first-successful-login-on-p… Sent from the Dovecot mailing list archive at Nabble.com.

2 3

[Dovecot] dovecot director service
by Xavier Pons 23 Jul '10

23 Jul '10

hi, we are using the dovecot-rc1 version, and we are testing the director service, as there is little documentation on this service, a pair of questions.. if i'm not wrong, the proxy_maybe it's not implemented, yet? will be soon? this limitation does not allow use the same two directors servers like mail backend servers? the fairlure of one director server it's automatically detected or require manual intervention? thanks and sorry for so many questions... Xavier

4 18

[Dovecot] Doveadm protocol for parallel user processing
by Timo Sirainen 23 Jul '10

23 Jul '10

A lot of doveadm commands process users' mails. They can optionally process either a single user or multiple users (e.g. -A = all, -u '*(a)domain.org'). For example to expunge old mails from everyone's Trash, you'd use: doveadm expunge -A mailbox Trash savedbefore 30d The problem is, this doesn't work with the new director way of doing proxying. Only a single server can access a user's mails safely, so this command can't be run safely if there are multiple mail servers. It's also a bit problematic for regular proxying, but it's especially problematic with director: Since users aren't permanently assigned anywhere, it's not even possible to build a user <-> host mapping and run the command only for those users in their assigned server. First I started thinking about adding another lib-storage backend that supports proxying to another server, maybe via IMAP or maybe via another protocol. Maybe I should do that some day anyway, but it seems a bit complex for this task. Then I also realized that even if all users are on local server, it would probably finish faster if doveadm could handle users in parallel in separate processes (due to disk I/O latencies and maybe other latencies). So, it seems like it would be a good idea to make doveadm internally a client/server architecture. When you start doveadm, it would be only the "brain" part, which connects to the worker doveadms either via local UNIX socket or to remote servers. Admin could configure how many doveadm worker processes the brain should connect per server (could be a per-server setting). So, what's needed to make this happen? 1. The actual client/server split and the protocol. Probably can be really simple and won't be anything interesting. Or maybe it becomes more interesting once I start thinking about it more, we'll see. :) 2. Authentication. 3. TLS-protection? After merging code from dovecot-2.0-sslstream branch this should be pretty easy. Although Dovecot should finally then add support for checking that CommonName/etc match the server name. Authentication -------------- For local UNIX sockets that are 0600 root, the authentication wouldn't be necessary. It could internally check that if the listener socket has these permissions, it would just announce that doveadm is already authenticated. Otherwise, and especially for TCP connections, there should be authentication. I was thinking about using already existing master users for this. Doveadm client says "I'm <masteruser>, my password is <pass>, and I want to access <user>'s mails". Auth process does the authentication and replies either success or failure, just like for similar IMAP/POP3/etc logins. It's possible to restrict what users a master user can log in as, like admin(a)domain.org could only log in as *(a)domain.org. This means that you could also enable doveadm protocol for external users, and let the domain administrators use doveadm directly to manage their own domain's users. PLAIN authentication mechanism would be easy to support. But this might be a good time to also introduce client side SASL library to Dovecot to support other auth mechanisms. But then again, maybe it doesn't really matter.. Privilege dropping ------------------ I hate it that with multiple UIDs doveadm processes currently have to be run as root and they only temporarily drop privileges. With client/server split it would be possible to get rid of this. Each doveadm worker process would then handle only a single user and then exit. This would be optional similar to how login processes are now, e.g.: service doveadm { # 1 = default = one user access per process, 0 = unlimited user accesses service_count = 1 } LMTP privilege dropping ----------------------- Completely unrelated to doveadm, but due to the above doveadm privilege dropping thinking I also started thinking about LMTP. It's also annoying that it runs as root, and only temporarily drops privileges. It could also avoid this by saving a mail only to a single user per process. The problem is that there can be multiple RCPT TO:s in a same session, but this can be handled by treating them similarly than when using LMTP proxying: Just connect to localhost again and proxy the mail there for each user separately. This could also be optionally done only when the process UID differs from the destionation user's UID. When? ----- These are too invasive changes to v2.0, so I guess they'll wait until v2.1. Luckily there won't be any hugely destabilizing changes going into v2.1, so maybe v2.1.0 release won't be too many months after v2.0.0. :)

1 2

[Dovecot] managesieve login fails
by Leander S. 23 Jul '10

23 Jul '10

Hi, when I try to make use of the managesieve capability maillog always shows: server dovecot: managesieve-login: Panic: file client.c: line 449 (client_set_auth_waiting): assertion failed: (client->to_auth_waiting == NULL) server dovecot: dovecot: child 5926 (login) killed with signal 6 (core not dumped) (ip=192.168.1.233) ... and Thunderbirds remote sieve optimizing plugin won't connect ... Otherwhise IMAP & POP authentication, etc. ... is working proper.

2 2

[Dovecot] dovecot 2.0rc2 [SERVERBUG] When trying to remove a folder which contains a subfolder
by Sven Kirmess 23 Jul '10

23 Jul '10

I'm going to risk to report something stupid again and waste resources... but [SERVERBUG] sounds like it should not happen. :) g create test g OK Create completed. h create test/test2 h OK Create completed. i list "test" "*" * LIST (\HasChildren) "/" "test" * LIST (\HasNoChildren) "/" "test/test2" i OK List completed. j delete "test" j NO [SERVERBUG] Internal error occurred. Refer to server log for more information. [2010-07-17 22:57:48] The log has the following entry: Jul 17 22:57:48 azati dovecot: [ID 583609 mail.error] imap(ski): Error: rmdir(/l/dovecot/ski/dbox/mailboxes/test) failed: File exists Which is correct $ ls /l/dovecot/ski/dbox/mailboxes/test/ test2 Deleting the mailboxes in sync does work. k delete "test/test2" k OK Delete completed. l delete "test" l OK Delete completed. m list "test" "*" m OK List completed. $ dovecot -n # 2.0.rc2: /etc/opt/dovecot/dovecot/dovecot.conf # OS: SunOS 5.10 i86pc zfs first_valid_uid = 100 mail_location = mdbox:/l/dovecot/%u/dbox passdb { driver = pam } protocols = imap service imap-login { inet_listener imap { port = 0 } } service imap { vsz_limit = 1073741824 } ssl = required ssl_cert = </etc/opt/dovecot/dovecot/certs/dovecot.pem ssl_key = </etc/opt/dovecot/dovecot/private/dovecot.pem userdb { driver = passwd } verbose_proctitle = yes protocol imap { imap_client_workarounds = tb-extra-mailbox-sep }

2 2

[Dovecot] Upgrade 1.1 to 1.2 double check
by Roderick A. Anderson 23 Jul '10

23 Jul '10

Read what I could find on possible upgrade issues and saw only one that might be a problem. I don't think it will but figured it was worth checking. Anything jump out at the more experienced users? dovecot -n (edited to protect the guilty. ie. me) attached. # 1.1.11: /etc/dovecot.conf # OS: Linux 2.6.22.19-vs2.3.0.34.1 i686 CentOS release 5.2 (Final) log_path: /var/log/dovecot/dovecot.log info_log_path: /var/log/dovecot/dovecot-info.log protocols: imap imaps listen: *:143 ssl_listen: *:993 login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login login_greeting_capability: yes valid_chroot_dirs: /var/mail first_valid_uid: 5000 last_valid_uid: 5000 first_valid_gid: 5000 last_valid_gid: 5000 mail_access_groups: mail mail_location: maildir:~/Maildir mail_debug: yes maildir_copy_preserve_filename: yes imap_client_workarounds: outlook-idle auth default: mechanisms: plain login CRAM-MD5 default_realm: example.com master_user_separator: * verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /var/mail/vhosts/%d/passwd.masterusers pass: yes master: yes passdb: driver: passwd-file args: username_format=%n /var/mail/vhosts/%d/passwd userdb: driver: passwd-file args: username_format=%n /var/mail/vhosts/%d/passwd socket: type: listen master: path: /var/run/dovecot/auth-master mode: 432 user: vmail socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix plugin: sieve: /var/mail/vhosts/%d/%n/dovecot.sieve

2 1

[Dovecot] problem mysql and dovecot 1.2
by debian＠robertain.com 23 Jul '10

23 Jul '10

Hi everybody , Since my version 1.2. I have a problem with the management of quotas. select * from virtual_users; +----+-----------+----------------------------------+---------------------------+----------+----------------+ | id | domain_id | password | email | quota_kb | quota_messages | +----+-----------+----------------------------------+---------------------------+----------+----------------+ | 1 | 1 | xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx | xxxxxx(a)domain.com | 10000000 | 0 | .................. Before my time in 1.2. I did this for the quota management: user_query = SELECT CONCAT('/var/vmail/',CONCAT(SUBSTRING_INDEX(email,'@',-1),'/',SUBSTRING_INDEX(email,'@',1))) AS home, 5000 AS uid, 5000 AS gid, CONCAT('maildir:storage=',quota_kb,':messages=',quota_messages) AS quota FROM virtual_users WHERE email='%u'; My configuration dovecot -n # 1.2.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.30-2-686 i686 Debian squeeze/sid ext3 log_path: /var/vmail/dovecot-deliver.log info_log_path: /var/vmail/dovecot-deliver.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps pop3s managesieve ssl_cert_file: /etc/ssl/certs/popimap.crt ssl_key_file: /etc/ssl/private/popimap.key verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_max_userip_connections(default): 10 mail_max_userip_connections(imap): 10 mail_max_userip_connections(pop3): 3 mail_max_userip_connections(managesieve): 10 mail_location: maildir:/var/vmail/%d/%n/Maildir mail_debug: yes mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve namespace: type: private separator: . prefix: INBOX. inbox: yes list: yes subscriptions: yes lda: postmaster_address: postmaster(a)mydomain.com mail_plugins: quota sieve auth_socket_path: /var/run/dovecot/auth-master auth default: mechanisms: plain login passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: static args: uid=5000 gid=5000 home=/var/vmail/%d/%n allow_all_users=yes socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/sieve quota: dict:user::proxy::quotadict quota_rule: *:storage=100M quota_warning: storage=95%% /usr/local/bin/quota-warning.sh 95 dict: quotadict: mysql:/etc/dovecot/dovecot-dict-sql.conf my configuration dovecot-sql.conf cat dovecot-sql.conf #protocols = imap imaps pop3 pop3s # Database driver: mysql, pgsql, sqlite driver = mysql connect = host=127.0.0.1 dbname=mailserver user=mailsuer password=***** default_pass_scheme = PLAIN-MD5 password_query = SELECT email,password FROM virtual_users WHERE email='%u'; #user_query = SELECT home, uid, gid, concat('*:storage=', quota_bytes, 'B') AS quota_rule FROM virtual_users WHERE userid = '%u' #user_query = SELECT maildir, 5000 AS uid, 5000 AS gid, CONCAT('*:storage=', quota_bytes, 'B') AS quota_rule FROM virtual_users WHERE userid = '%u' #user_query = SELECT maildir AS home , 5000 AS uid, 5000 AS gid, CONCAT('*:storage=',quota, 'B') AS quota_rule FROM virtual_users WHERE username = '%u' #user_query = SELECT maildir AS home, 5000 AS uid, 5000 AS gid, CONCAT('*:bytes=', CAST(quota AS CHAR)) AS quota_rule FROM quota WHERE username = '%u' AND active = '1 I used all these configurations but none work. yet but the quotas work through this option: quota_rule: *:storage=100M The problem is that quotas are not personalized. I'm looking for a way to use quotas, but using my mysql database. I galley for some time. So if someone has an idea I am willing

4 6