- dovecot - dovecot.org

[Dovecot] Commercial support
by Timo Sirainen 26 Jul '05

26 Jul '05

1.0 release is slowly (but surely :) getting nearer and I'd like to be able to offer commercial support for it for those who want or need it. I have a few different plans for how to do that, but I haven't really decided yet what to do. So I thought I'd ask a few questions here to see how much interest there is currently, which could help me make some decisions sooner. You should probably reply privately to me so this list won't get spammed. So, assume that Dovecot v1.0 will really be stable, will have real documentation, and the support isn't going to be completely in hands of just one or two guys. I think there would basically be two types of support available: 1. Basic support Guaranteed replies to questions within some time interval. - what response times? a few days? - phone support needed? - what would you be willing to pay for it? 2. Mission critical support For those who *really* can't afford any unexpected downtime, and so would be willing to pay more for quick response times. Problems divided to different categories (eg. normal, high, critical) with different response times. - what response times? a few days for normal, about one day for high, less for critical? - sanctions? - customized modifications, kept up-to-date for new Dovecot versions? - what would you be willing to pay for it? I'm not sure if there should be "outsourced email server maintenance" option too. Or maybe some really low cost support for a limited number of questions. Any other ideas, suggestions or tips? Did I miss something important? And finally, would you like to have a job related to Dovecot? :)

2 1

[Dovecot] virtual mailboxes with postfix
by David Cake 26 Jul '05

26 Jul '05

I have set up postfix with virtual mailboxes stored via mysql, and using postfixadmin, and dovecot as pop/imap server My postfix and mysql setup are pretty much standard for postfixadmin, as described here <http://postfixwiki.org/index.php?title=Virtual_Users_and_Domains_with_Couri…> (except for the parts about courier-imap.) Everything appears to be working fine except actually checking and authenticating mail via dovecot. I am fairly sure all I really need is the appropriate incantations in /etc/dovecot/dovecot.conf and dovecot-mysql.conf - does anyone have this set up and working? I should add that I want to allow both virtual mailboxes, and also local accounts, so I presumably need to support two different kinds of authentication. Regards David

2 1

[Dovecot] removing (hopefully) unneeded access to $HOME
by adsmith＠math.duke.edu 25 Jul '05

25 Jul '05

Hi, Thanks for dovecot. It's the best IMAP server ever. Okay, here's my problem: I use mbox INBOXes from /var/spool/mail/%u, and the INDEX lies in /var/spool/mail/dovecot/%d/%u. Users' other folders are found in /%h/mail. Now, I notice that when a user is accessing her INBOX, the imap process cwd's to the user's home, which I'd like to prevent as much as possible. E.g., when the user's client is only watching INBOX, I still see: [root@tock:~]$ lsof | grep home_kt imap 6422 kt cwd DIR 0,17 12288 7602177 /home/kt (other.host:/home/kt) Is there a way I can tweak the dovecot settings so that this cwd isn't holding open the NFS mount? Many thanks, Abe Smith -- # Abraham David Smith, <adsmith(a)math.duke.edu> # # http://fds.duke.edu/db/aas/math/grad/adsmith # # Mathematics Graduate Student, Duke University #

1 1

Re: [Dovecot] pop3 authentication failure - password mismatch
by James Sun 25 Jul '05

25 Jul '05

On 7/22/05, Girish Patangay <girish(a)intoto.com> wrote: > Shouldn't you be using "shadow" instead of passwd for the passdb? > > Just a curious question. > Yes! You are right. "shadow" should work as well. I just give it a try and auth worked! Thanks. However, I am not hitting another problem : no proper permission. If I understand correctly I have set it in dovecot.conf file to use "root" for processing. How come I don't have enough permission? Jul 23 02:26:56 hsiufen dovecot: Dovecot v1.0-stable starting up Jul 23 02:28:10 hsiufen dovecot: pop3-login: Login: jam [24.6.106.170] Jul 23 02:28:10 hsiufen dovecot: POP3(jam): open(/var/mail/.temp.hsiufen.net.15682.f3c4cf83d750e6e4) failed: Permission denied Jul 23 02:28:10 hsiufen dovecot: POP3(jam): file_lock_dotlock() failed with mbox file /var/mail/jam: Permission denied Jul 23 02:28:31 hsiufen dovecot: Killed with signal 2 Any ideas? Jun

3 3

[Dovecot] Re: Bug#319504: Bug in 0.99.14 mbox handling - mail UIDs are renumbered without bumping UIDVALIDITY
by Jaldhar H. Vyas 25 Jul '05

25 Jul '05

On Fri, 22 Jul 2005, David McBride wrote: > Package: dovecot-imapd > Version: 0.99.14-1 > Severity: important > > Hi, > > I think I've identified a bug in Dovecot 0.99.14 as packaged and > distributed by Debian Sarge. I believe the bug lies in the original > Dovecot source, not with any modifications made by Debian. > > Specifically, this bug deals with Dovecot's handling of message unique > identifiers (UIDs) for IMAP clients when using the mbox mailbox storage > format. > David, can you check if the problem persists with 0.99.20050712-1 which is in sid? This is actually the 1.0stable branch of dovecot and has many fixes not included in 0.99.x The package should work correctly on sarge (a proper sarge backport is forthcoming) but you will also need libpq4 from sid and you'll need to make sure dovecot-common is also upgraded to 0.99.20050712-1 also. -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/

2 1

[Dovecot] dovecot permission denied problems.
by John Mc Donald 25 Jul '05

25 Jul '05

I am trying to setup dovecot on a FC4 machine. Access to the machine is provided through pam. When I login to the machine my home directory is mounted over nfs from a central file server. I have dovecot installed and running but it can't seem to access my home directory. When I try and access my mail I get the following three lines in /var/log/maillog: > Jul 25 12:46:04 escher imap-login: Login: ###### [::ffff:###.###.###.###] > Jul 25 12:46:04 escher dovecot: chdir(/home/######) failed with uid > ####: Permission denied > Jul 25 12:46:04 escher dovecot: child 13182 (imap) returned error 89 The uid that is used is the one associated with my home directory. As far as I understand it when you connect to dovecot the imap connection setuid's to the uid of the authenticated user so there should be no permission problems. To try and help in the debugging process I also setup a local user "testimap" using > /usr/sbin/useradd -d /tmp/testimap testimap I then try to use thunderbird to connect to it and I get the following in /var/log/maillog > Jul 25 12:54:54 escher imap-login: Login: testimap > [::ffff:###.###.###.###] > Jul 25 12:54:54 escher imap(testimap): mbox: Can't create root IMAP > folder /tmp/testimap/mail: Permission denied > Jul 25 12:54:54 escher imap(testimap): MAIL environment missing and > autodetection failed (home /tmp/testimap) > Jul 25 12:54:54 escher dovecot: child 13360 (imap) returned error 89 Can anyone tell me what I am doing wrong here? TIA, John. -- ================================== John Mc Donald, Dept. of Computer Science, National University of Ireland, Maynooth, Co. Kildare, Ireland. Email : johnmcd(a)cs.nuim.ie Tel: +353-1-7084589 Fax: +353-1-7083848 Web: http://www.cs.nuim.ie/~johnmcd GnuPG Key: http://www.cs.nuim.ie/~johnmcd/public_key.asc ==================================

2 2

[Dovecot] inotify support in dovecot
by Reuben Farrelly 25 Jul '05

25 Jul '05

Hi, I note that dovecot supported inotify from -test77, and now the Linux kernel supports it starting from linux-2.6.13-rc3. So in theory I should be set to go. I'm using an -mm kernel, and it was built with inotify, on FC4/devel. However when trying to build with it using --with-notify=inotify, I always seem to be getting this message: checking for poll... yes configure: error: inotify requested but not available, check for existence of <linux/inotify.h> /bin/sh ./config.status --recheck What is required for inotify to be recognised and built into dovecot? I've tried copying the header from linux-2.6/include/linux/inotify.h to the /usr/include/linux directory, but that didn't help - and seems wrong to do anyway. Has anyone else had any experiences with inotify/dovecot? reuben

2 3

[Dovecot] 1.0-test79
by Timo Sirainen 25 Jul '05

25 Jul '05

http://dovecot.org/test/ Now checks that field alignmentations are in indexes as they're expected. test78 crashed if it was wrong, earlier versions ignored the problem (and crashed with 64bit systems). Now if it's wrong, it prints error to log file and recreates the index. That means you probably should delete all dovecot.index files to avoid tons of errors in log files. Only mbox users need to do this. - LSUB: Don't crash if .subscriptions file can't be opened. Also in general give proper "permission denied" error if LIST/LSUB failed because of permission problems. - Maildir: Fix deadlocking when saving messages (noticeable with copying lots of messages with Thunderbird) - LDAP: user_global_uid/gid wasn't working. Also now they support having user/group names from /etc/passwd instead of just numbers. - passwd-file now supports variables in filename, so you can do eg. args = /etc/passwd.%d - Open/close PAM session if -session option is given. Patch by Pasi Sjöholm. - Added tb-extra-mailbox-sep workaround for Thunderbird+mbox problems.

6 9

[Dovecot] dovecot 1.0-stable (050721) rpm for FC3
by James Sun 25 Jul '05

25 Jul '05

OK, thanks for the all the helps I got from the list. I finally managed to get stable 1.0 (050721) built and running. To avoid the same hassels for others, I made an rpm. You can check it out at http://linux.junsun.net/rpms My main motivation to upgrade to this version is to avoid the "Status: O" header re-write bug in 0.99 versions. Cheers. Jun

1 0

[Dovecot] ssl_cipher_list
by Robert Allerstorfer 24 Jul '05

24 Jul '05

Hi, I have noticed the 'ssl_cipher_list' directive in the 1.0-test snapshots which is not in 0.99. It's default value seems to be "all:!low". However, this would not be compatible with openssl's cipher listing format. Thus, I would vote to change it's format to be openssl compatible. To be compatible, it has to be changed to "ALL:!LOW" (just upercased in this case). IMO, this would be helpful because executing openssl ciphers -v 'all:!low' would not return any cipher, but openssl ciphers -v 'ALL:!LOW' would return the expected cipher list such as ADH-AES256-SHA SSLv3 Kx=DH Au=None Enc=AES(256) Mac=SHA1 DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 DHE-DSS-AES256-SHA SSLv3 Kx=DH Au=DSS Enc=AES(256) Mac=SHA1 AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 ADH-AES128-SHA SSLv3 Kx=DH Au=None Enc=AES(128) Mac=SHA1 DHE-RSA-AES128-SHA SSLv3 Kx=DH Au=RSA Enc=AES(128) Mac=SHA1 DHE-DSS-AES128-SHA SSLv3 Kx=DH Au=DSS Enc=AES(128) Mac=SHA1 AES128-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(128) Mac=SHA1 DHE-DSS-RC4-SHA SSLv3 Kx=DH Au=DSS Enc=RC4(128) Mac=SHA1 EXP1024-DHE-DSS-RC4-SHA SSLv3 Kx=DH(1024) Au=DSS Enc=RC4(56) Mac=SHA1 export EXP1024-RC4-SHA SSLv3 Kx=RSA(1024) Au=RSA Enc=RC4(56) Mac=SHA1 export EXP1024-DHE-DSS-DES-CBC-SHA SSLv3 Kx=DH(1024) Au=DSS Enc=DES(56) Mac=SHA1 export EXP1024-DES-CBC-SHA SSLv3 Kx=RSA(1024) Au=RSA Enc=DES(56) Mac=SHA1 export EXP1024-RC2-CBC-MD5 SSLv3 Kx=RSA(1024) Au=RSA Enc=RC2(56) Mac=MD5 export EXP1024-RC4-MD5 SSLv3 Kx=RSA(1024) Au=RSA Enc=RC4(56) Mac=MD5 export EXP-KRB5-RC4-MD5 SSLv3 Kx=KRB5 Au=KRB5 Enc=RC4(40) Mac=MD5 export EXP-KRB5-RC2-CBC-MD5 SSLv3 Kx=KRB5 Au=KRB5 Enc=RC2(40) Mac=MD5 export EXP-KRB5-DES-CBC-MD5 SSLv3 Kx=KRB5 Au=KRB5 Enc=DES(40) Mac=MD5 export EXP-KRB5-RC4-SHA SSLv3 Kx=KRB5 Au=KRB5 Enc=RC4(40) Mac=SHA1 export EXP-KRB5-RC2-CBC-SHA SSLv3 Kx=KRB5 Au=KRB5 Enc=RC2(40) Mac=SHA1 export EXP-KRB5-DES-CBC-SHA SSLv3 Kx=KRB5 Au=KRB5 Enc=DES(40) Mac=SHA1 export KRB5-RC4-MD5 SSLv3 Kx=KRB5 Au=KRB5 Enc=RC4(128) Mac=MD5 KRB5-DES-CBC3-MD5 SSLv3 Kx=KRB5 Au=KRB5 Enc=3DES(168) Mac=MD5 KRB5-RC4-SHA SSLv3 Kx=KRB5 Au=KRB5 Enc=RC4(128) Mac=SHA1 KRB5-DES-CBC3-SHA SSLv3 Kx=KRB5 Au=KRB5 Enc=3DES(168) Mac=SHA1 EDH-RSA-DES-CBC3-SHA SSLv3 Kx=DH Au=RSA Enc=3DES(168) Mac=SHA1 EXP-EDH-RSA-DES-CBC-SHA SSLv3 Kx=DH(512) Au=RSA Enc=DES(40) Mac=SHA1 export EDH-DSS-DES-CBC3-SHA SSLv3 Kx=DH Au=DSS Enc=3DES(168) Mac=SHA1 EXP-EDH-DSS-DES-CBC-SHA SSLv3 Kx=DH(512) Au=DSS Enc=DES(40) Mac=SHA1 export DES-CBC3-SHA SSLv3 Kx=RSA Au=RSA Enc=3DES(168) Mac=SHA1 EXP-DES-CBC-SHA SSLv3 Kx=RSA(512) Au=RSA Enc=DES(40) Mac=SHA1 export EXP-RC2-CBC-MD5 SSLv3 Kx=RSA(512) Au=RSA Enc=RC2(40) Mac=MD5 export RC4-SHA SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=SHA1 RC4-MD5 SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=MD5 EXP-RC4-MD5 SSLv3 Kx=RSA(512) Au=RSA Enc=RC4(40) Mac=MD5 export ADH-DES-CBC3-SHA SSLv3 Kx=DH Au=None Enc=3DES(168) Mac=SHA1 EXP-ADH-DES-CBC-SHA SSLv3 Kx=DH(512) Au=None Enc=DES(40) Mac=SHA1 export ADH-RC4-MD5 SSLv3 Kx=DH Au=None Enc=RC4(128) Mac=MD5 EXP-ADH-RC4-MD5 SSLv3 Kx=DH(512) Au=None Enc=RC4(40) Mac=MD5 export DES-CBC3-MD5 SSLv2 Kx=RSA Au=RSA Enc=3DES(168) Mac=MD5 RC2-CBC-MD5 SSLv2 Kx=RSA Au=RSA Enc=RC2(128) Mac=MD5 EXP-RC2-CBC-MD5 SSLv2 Kx=RSA(512) Au=RSA Enc=RC2(40) Mac=MD5 export RC4-MD5 SSLv2 Kx=RSA Au=RSA Enc=RC4(128) Mac=MD5 EXP-RC4-MD5 SSLv2 Kx=RSA(512) Au=RSA Enc=RC4(40) Mac=MD5 export I want dovecot to only accept high encrypted ciphers, thus it should support ssl_cipher_list = ALL:!ADH!LOW:!SSLv2:!EXP:+HIGH:+MEDIUM corresponding to a openssl list such as DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 DHE-DSS-AES256-SHA SSLv3 Kx=DH Au=DSS Enc=AES(256) Mac=SHA1 AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 KRB5-DES-CBC3-MD5 SSLv3 Kx=KRB5 Au=KRB5 Enc=3DES(168) Mac=MD5 KRB5-DES-CBC3-SHA SSLv3 Kx=KRB5 Au=KRB5 Enc=3DES(168) Mac=SHA1 EDH-RSA-DES-CBC3-SHA SSLv3 Kx=DH Au=RSA Enc=3DES(168) Mac=SHA1 EDH-DSS-DES-CBC3-SHA SSLv3 Kx=DH Au=DSS Enc=3DES(168) Mac=SHA1 DES-CBC3-SHA SSLv3 Kx=RSA Au=RSA Enc=3DES(168) Mac=SHA1 DHE-RSA-AES128-SHA SSLv3 Kx=DH Au=RSA Enc=AES(128) Mac=SHA1 DHE-DSS-AES128-SHA SSLv3 Kx=DH Au=DSS Enc=AES(128) Mac=SHA1 AES128-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(128) Mac=SHA1 DHE-DSS-RC4-SHA SSLv3 Kx=DH Au=DSS Enc=RC4(128) Mac=SHA1 KRB5-RC4-MD5 SSLv3 Kx=KRB5 Au=KRB5 Enc=RC4(128) Mac=MD5 KRB5-RC4-SHA SSLv3 Kx=KRB5 Au=KRB5 Enc=RC4(128) Mac=SHA1 RC4-SHA SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=SHA1 RC4-MD5 SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=MD5 This would really make "Dovecot (...) written with security primarily in mind" Thanks for consideration! rob.

2 2