- dovecot - dovecot.org

Re: [Dovecot] Bug in Dovecot 1.0.5 - CRYPT-MD5 not working
by Timo Sirainen 31 Dec '08

31 Dec '08

On Dec 31, 2008, at 1:50 AM, Jim Salter wrote: > Hrm. OK, not arguing, just curious: where is the MD5-CRYPT standard > defined? I don't think it's a real standard. It's just something that libcs started implementing. I think OpenBSD did it first and then others started copying. > Worth noting that the (Apache?) standard in question is also the one > used in vpopmail vpasswd.cdb files (authdb vpopmail, userdb vpopmail). Would it work if you simply changed $apr1$ to $1$? I can't really see why $apr1$ would otherwise work in glibc. I just checked its sources and also Ubuntu patches. There's no mention of apr1 in them.

2 1

[Dovecot] Bug in Dovecot 1.0.5 - CRYPT-MD5 not working
by Jim Salter 31 Dec '08

31 Dec '08

Problem: Using MySQL storage for the user and password db with MD5-CRYPT hashes, Dovecot fails to successfully authenticate when the MD5-CRYPT or MD5 settings are specified as default_pass_scheme in dovecot-mysql.conf. Dovecot /does/ successfully authenticate against MD5-CRYPT hashes when default_pass_scheme is set to CRYPT, which according to the docs should be DES encryption. (I do not know whether or not CRYPT actually works with DES hashes.) I am positive that I am using MD5-CRYPT hashes, as I have dropped in hashes from a Qmail/Vpopmail vpasswd file and they work with the CRYPT setting in Dovecot, as do hashes generated using htpasswd -nmb. Test system: Ubuntu Server 7.10, amd64 Dovecot 1.0.5 (from Ubuntu repositories) Postfix 2.4.5 (from Ubuntu repositories) Demonstration: # cat /etc/dovecot/dovecot-mysql.conf driver = mysql connect = dbname=redacted user=redacted host=127.0.0.1 password=redacted default_pass_scheme = MD5-CRYPT password_query = SELECT password FROM mailbox WHERE username = '%u' user_query = SELECT maildir, 105 AS uid, 114 AS gid FROM mailbox WHERE username = '%u' # htpasswd -nmb user password user:$apr1$bZQl//..$2IPoOibTBaqpG7pPFigOy/ # mysql -u postfix -p mysql> use redacted; Database changed mysql> update userdb set password='$apr1$bZQl//..$2IPoOibTBaqpG7pPFigOy/' where username='user'; Query OK, 1 rows affected (0.00 sec) mysql>quit Bye # telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Dovecot ready. a login user password a NO Authentication failed. a logout * BYE Logging out a OK Logout completed. Connection closed by foreign host. # replace MD5-CRYPT CRYPT -- /etc/dovecot/dovecot-mysql.conf # /etc/init.d/dovecot restart * Restarting IMAP/POP3 mail server dovecot [ OK ] # telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Dovecot ready. a login user password a OK Logged in. a logout * BYE Logging out a OK Logout completed. Connection closed by foreign host.

2 1

[Dovecot] admin tool
by Romer Ventura 30 Dec '08

30 Dec '08

Hello, I havent found anything on the topic, but does dovecot has a admin tool like Cyrus..? Thanks ------ Romer Ventura Network administrator

2 1

[Dovecot] SSL cert problems.
by Geoff Sweet 30 Dec '08

30 Dec '08

I'm really racking my brain trying to figure this one out here. I am running a pop3 server for remote offices on CentOS 5.2. We purchased a SSL cert from Verisign and installed it on our dovecot server, but I continue to get failure problems with the cert and I don't know where to go from here. here is some info about our config: dovecot version: # dovecot --version 1.0.7 hostname: pop.x10.com dovecot.conf: # dovecot -n # 1.0.7: /etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log protocols: pop3 pop3s ssl_ca_file: /etc/pki/verisign/intermediate_ca.cer ssl_cert_file: /etc/pki/dovecot/certs/pop.x10.com.cer ssl_key_file: /etc/pki/dovecot/private/pop.x10.com.key ssl_cipher_list: HIGH:MEDIUM:+TLSv1:!SSLv2:+SSLv3 verbose_ssl: yes login_dir: /var/run/dovecot//login login_executable: /usr/libexec/dovecot/pop3-login mail_executable: /usr/libexec/dovecot/pop3 mail_plugin_dir: /usr/lib/dovecot/pop3 pop3_client_workarounds: outlook-no-nuls auth default: passdb: driver: pam userdb: driver: passwd and last but not least, here is my test from openssl. Mind you this fails as a "BAD" ssl cert in Evolution. :~$ openssl s_client -ssl2 -connect pop.x10.com:995 CONNECTED(00000003) depth=0 /C=US/ST=Washington/L=Renton/O=X10 Wireless Technology, Inc./OU=Information Technology/OU=Terms of use at www.verisign.com/rpa (c)05/CN=pop.x10.com verify error:num=20:unable to get local issuer certificate verify return:1 depth=0 /C=US/ST=Washington/L=Renton/O=X10 Wireless Technology, Inc./OU=Information Technology/OU=Terms of use at www.verisign.com/rpa (c)05/CN=pop.x10.com verify error:num=27:certificate not trusted verify return:1 depth=0 /C=US/ST=Washington/L=Renton/O=X10 Wireless Technology, Inc./OU=Information Technology/OU=Terms of use at www.verisign.com/rpa (c)05/CN=pop.x10.com verify error:num=21:unable to verify the first certificate verify return:1 21568:error:1406D0B8:SSL routines:GET_SERVER_HELLO:no cipher list:s2_clnt.c:450: As you can see, the certificate clearly fails. I don't know how to make this work at this point. Any thoughts or advice would be greatly appreciated. -G

4 11

[Dovecot] another assertion failure in dovecot 1.1.7 mbox-sync-rewrite: (mails[idx].from_offset == start_offset)
by Diego Liziero 29 Dec '08

29 Dec '08

Sorry, this time I've no core file, (I forgot to set ulimit -c unlimited before starting dovecot) Regards, Diego. --- dovecot: Dec 09 08:26:52 Panic: IMAP(user): file mbox-sync-rewrite.c: line 590 (mbox_sync_rewrite): assertion failed: (mails[idx].from_offset == start_offset) dovecot: Dec 09 08:26:52 Error: IMAP(user): Raw backtrace: /usr/libexec/dovecot/imap [0x80f739e] -> /usr/libexec/dovecot/imap [0x80f7c5f] -> /usr/libexec/dovecot/imap(i_fatal+0) [0x80f7518] -> /usr/libexec/dovecot/imap(mbox_sync_rewrite+0x6e8) [0x8094e45] -> /usr/libexec/dovecot/imap [0x809105c] -> /usr/libexec/dovecot/imap [0x8091d77] -> /usr/libexec/dovecot/imap [0x809277e] -> /usr/libexec/dovecot/imap(mbox_sync+0x2b) [0x8092a0a] -> /usr/libexec/dovecot/imap [0x8084ff3] -> /usr/libexec/dovecot/imap(mailbox_close+0x47) [0x80b701c] -> /usr/libexec/dovecot/imap(cmd_close+0xc0) [0x805b5d8] -> /usr/libexec/dovecot/imap [0x80625c4] -> /usr/libexec/dovecot/imap [0x80627f9] -> /usr/libexec/dovecot/imap [0x80628f7] -> /usr/libexec/dovecot/imap [0x8062933] -> /usr/libexec/dovecot/imap(client_input+0xb7) [0x8062ac1] -> /usr/libexec/dovecot/imap(io_loop_handler_run+0x17d) [0x8101ecd] -> /usr/libexec/dovecot/imap(io_loop_run+0x35) [0x8101164] -> /usr/libexec/dovecot/imap(main+0xb0) [0x806df19] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x7a5dec] -> /usr/libexec/dovecot/imap [0x805a2b1]

2 3

[Dovecot] Password field limitations
by Tom Sommer 29 Dec '08

29 Dec '08

Hi, I've searched the WIKI for this information but seem unable to find anything about it. What limitations are imposed on the password for IMAP/POP3 users? I've had a customer saying they can't use passwords which contain "." or ":", and some seem to have problems when the password is 8 characters. I use PLAIN authentication, passwords are stored in a MySQL database. Thanks a lot -- Tom Sommer

4 5

[Dovecot] automounting home dirs
by Roger Hale 29 Dec '08

29 Dec '08

Hi, I'm running dovecot-1.0.10 on a Solaris 10 server with home dirs automounted over NFS. I have set the mail_location configuration option so that nothing should be written to a user's home dir over NFS but, as far as I can tell, dovecot still by default tries to chdir to a user's home dir when reading mail, although this is not required. This creates additional unnecessary load on a heavily-loaded fileserver and generally slows everything down and creates an unnecessary dependency. Is there a way to prevent dovecot from causing the home dirs to be mounted? I found this thread: http://markmail.org/message/umywuppl3vvzfe4p#query:dovecot%20mount%20home%2… which discusses the same problem, but it's quite old and there doesn't seem to be a definitive answer other than hacking the passwd file or the code. Is there a more elegant solution? TIA. _________________________________________________________________ Get a bird’s eye view of the world with Multimap http://clk.atdmt.com/GBL/go/115454059/direct/01/

2 3

[Dovecot] change sender name in Sieve
by Jakob Grießmann 26 Dec '08

26 Dec '08

Hello, the vacation module of Sieve works fine for me, but the sender name (From Header) is always the e-mail address. I'm unable to add a name here. I'd love to have my realname in the From: field. Did I miss something? :-) Thanks, Jakob

5 8

[Dovecot] Logging logs moved/deleted
by Nicolas Letellier 26 Dec '08

26 Dec '08

Hi dovecot list, I'm looking for a possibility to log a moved (or a deleted mail). For example, I have a mailbox, and I read it in IMAP. I have a mail in INBOX. I want to move it to Folder. I want to have this action logged in my dovecot log file (or an other file). Is it possible? I read this: http://wiki.dovecot.org/Logging and I don't find any informations about it. I try to set "mail_debug=yes", but it does not log what I want. Thanks. Best regards (and happy Xmas). -- -Nicolas.

3 4

[Dovecot] /etc/dovecot.conf says mkcert.sh is in doc/mkcert.sh but instead it is in /usr/libexec/dovecot/mkcert.sh
by Michael McNamara 25 Dec '08

25 Dec '08

Perhaps this is an issue unique to installing from an RPM, but: % dovecot -n # 1.1.7: /etc/dovecot.conf # OS: Linux 2.6.27.7-134.fc10.i686 i686 Fedora release 10 (Cambridge) /etc/dovecot.conf says: ... ## ## SSL settings ## # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. #ssl_listen = # Disable SSL/TLS support. #ssl_disable = no # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. *Included doc/mkcert.sh can be used to easily generate self-signed* # certificate, just make sure to update the domains in dovecot-openssl.cnf #ssl_cert_file = /etc/pki/dovecot/certs/dovecot.pem #ssl_key_file = /etc/pki/dovecot/private/dovecot.pem However, installing dovecot from an rpm places mkcert.sh in: % rpm -qv dovecot dovecot-1.1.7-1.fc10.i386 % rpm -V -v dovecot S.5....T c /etc/dovecot.conf ........ c /etc/pam.d/dovecot ........ /etc/pki/dovecot ... ........ /usr/libexec/dovecot/logview ........ /usr/libexec/dovecot/maildirlock *........ /usr/libexec/dovecot/mkcert.sh * ........ /usr/libexec/dovecot/pop3 ........ /usr/libexec/dovecot/pop3-login

2 1