September 2006 - dovecot

[Dovecot] Restricting Services (POP or IMAP)
by Odhiambo WASHINGTON 15 Oct '06

15 Oct '06

It would be great to have a HOWTO in the wiki, on how to restrict services by username in dovecot, so some users are allowed IMAP and others not allowed. As concerns restricting users by IP, I believe that is a bad idea. It's almost a useless idea, imnsho, because they can connect from another IP. It's easy to restrict services by IP using a firewall or by using inetd. -Wash http://www.netmeister.org/news/learn2quote.html DISCLAIMER: See http://www.wananchi.com/bms/terms.php -- +======================================================================+ |\ _,,,---,,_ | Odhiambo Washington <wash(a)wananchi.com> Zzz /,`.-'`' -. ;-;;,_ | Wananchi Online Ltd. www.wananchi.com |,4- ) )-,_. ,\ ( `'-'| Tel: +254 20 313985-9 +254 20 313922 '---''(_/--' `-'\_) | GSM: +254 722 743223 +254 733 744121 +======================================================================+ Don't take life too seriously -- you'll never get out of it alive.

5 8

[Dovecot] request to have dovecot authenticator driver 'officially' included/supported
by OpenMacNews 14 Oct '06

14 Oct '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi all, per the exim docs @: http://exim.org/exim-html-4.62/doc/html/spec_html/ch36.html a cyrus_sasl authenticator driveer is 'included' in exim core. given that Dovecot has become a very attractive alternative for an increasing number of folks, and there's a patch against exim 4.43 here: http://www.exim.org/eximwiki/AuthenticatedSmtpUsingDovecot that allows use of Dovecot's native sasl implementation as an authenticator, and that is _seems_ to apply against 4.63 ok, might it be possible to get this integrated into exim core, and have it become 'official'? thanks, richard - -- /"\ \ / ASCII Ribbon Campaign X against HTML email, vCards / \ & micro$oft attachments [GPG] OpenMacNews at gmail dot com fingerprint: 50C9 1C46 2F8F DE42 2EDB D460 95F7 DDBD 3671 08C6 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iEYEARECAAYFAkUC+eIACgkQlffdvTZxCMbG4wCgnczsi9zX6Xkg5MLi6JTez5d+ a+YAn0MIYI7gHW//8N5bxani1CoEAcJm =ZN2w -----END PGP SIGNATURE-----

5 16

[Dovecot] fcntl Bad file descriptor
by Bill Boebel 13 Oct '06

13 Oct '06

I've seen a couple of these in the log while testing the proxy too. Do you know what would cause this? Aug 10 23:30:29 director5 dovecot: imap-login: fcntl(-1, F_GETFL) failed: Bad file descriptor Aug 10 23:30:29 director5 dovecot: imap-login: fd_set_nonblock(-1) failed: Bad file descriptor Aug 10 23:30:29 director5 dovecot: child 14016 (login) returned error 89

2 1

[Dovecot] you got chocolate in my peanut butter?!
by Logan Shaw 13 Oct '06

13 Oct '06

Hey everyone, Ran into something positively perplexing today. A user came to me and said that this morning when they checked their mail, they got about 120 strange new messages. Upon further inspection, it seems the "new" messages are all addressed to a certain other different user and are all 3 or 4 months old. And looking in that other user's /var/mail/(username) mailbox, I see the same messages that arrived mistakenly. And they're not in the /var/mail mailbox of the user whose desktop computer they ended up on. So it would appear that, possibly, when this user connected to the server, they got someone else's messages! Messages that, in fact, came from an account they don't even have the password to! I'm really curious if anyone has seen something like this before. We're using dovecot-1.0.beta9, and have been since mid-June. I've never seen anything happen like this before. I'm perfectly willing to upgrade to the latest release candidate, but it's hard for me to "upgrade and see if that fixes it", because it happens so rarely and it won't be easy to know empirically. So what I'm really hoping for is confirmation that this is/was a known problem, if in fact it is. Of course, I don't know that this is a dovecot bug, but I could imagine that it might be (maybe a daemon forgets to switch users after one session is closed and another is opened?), so I thought I'd ask. I did see what looked like TLS fixes and login fixes in the changelogs, so it doesn't seem out of the question that such a bug could've existed. Some more information: I checked the user's settings on their desktop computer, where the unexpected messages appear, and sure enough, there is only one POP server account configured there, and it has the correct username. What's more, I asked them what time this happened, and they said probably at 7:00am or maybe a little earlier. Looking at my dovecot logs, I see this (where 'theuser' is the user who received the messages): Sep 28 06:59:49 myhostname dovecot: pop3-login: Disconnected: user=<theuser>, method=PLAIN, rip=192.168.1.245, lip=192.168.1.20, TLS Sep 28 06:59:55 myhostname dovecot: pop3-login: Login: user=<theuser>, method=PLAIN, rip=192.168.1.245, lip=192.168.1.20, TLS Sep 28 06:59:55 myhostname dovecot: POP3(theuser): Disconnected: Logged out top=0/0, retr=0/0, del=0/9, size=130585 So, it would seem that the user did login at the time they claimed and it was at that time (or close to it) that the weird messages appeared. Also, I checked the logs for logins from the person whose messages accidentally got downloaded, and it doesn't show them logging in until several hours later. Oh, and there are no log entries for either of the two users in question before that, at least not for over 12 hours before that. The user is running Outlook 2003, with POP3 + TLS access to the mailbox. My dovecot.conf has nothing fancy in it: base_dir = /var/run/dovecot/ ssl_cert_file = /etc/mail/certs/server.crt ssl_key_file = /etc/mail/certs/server.key protocols = imap imaps pop3 pop3s disable_plaintext_auth = no login_dir = /var/run/dovecot/login syslog_facility = local0 first_valid_uid = 100 protocol imap { } protocol pop3 { pop3_lock_session = yes pop3_uidl_format = %08Xv%08Xu } auth default { mechanisms = plain user = root passdb shadow { } userdb passwd { } } The accounts are all coming out of LDAP via nsswitch (and this is all happening on Slackware 10.2), but I'm fairly sure that's irrelevant since "getent passwd", etc. all show the right stuff. Thanks for any help anyone can give... - Logan

5 9

[Dovecot] parser bug
by DINH Viêt Hoà 13 Oct '06

13 Oct '06

hello Timo (and maybe other Dovecot developers), It looks like the MIME parser won't parse this correctly : Content-type: text/html Note the lower-case '-type' in 'Content-type'. -- DINH V. Hoa

2 1

[Dovecot] Feature req: auth_cache_relookup
by Bill Boebel 13 Oct '06

13 Oct '06

With auth_cache_size set to a value greater than zero, when our users change passwords their accounts stop working for a few minutes, because they are trying to log in with their new password, but Dovecot is comparing that against the cached old password. It would be nice if an option could be added so that if the login password does not match the cached password, the cache value is dropped and dovecot-auth queries the userDB, but only if the previous login was successful (to avoid frequent queries for bad logins). Maybe this option could be called "auth_cache_relookup" Bill

2 1

[Dovecot] How to store Dovecot Logs in SQL DB
by Krzysztof 09 Oct '06

09 Oct '06

Hello! I would like to put user login attempts into SQL DB (PostgreSQL). Any idea how to do it (without manual parsing log files)? Kind regards, Krzysztof Kiszewski

8 10

[Dovecot] Converting UW MBX mail folder
by Anne Hammond 09 Oct '06

09 Oct '06

We converted from uw-imapd to dovecot but are still having problems with MBX mail folders. The user can't access this "MBX mail folder": [root@volt Resume's]# file "Sys Admin" Sys Admin: MBX mail folder [root@volt Resume's]# mailutil copy ./"Sys Admin" '#driver.unix/new' Can't open mailbox ./Sys Admin: no such mailbox [root@volt Resume's]# mailutil copy -debug -verbose./SysAdminSave '#driver.unix/new' Can't open mailbox ./SysAdminSave: no such mailbox Could you tell me what I am doing wrong? Anne M. Hammond - Systems / Network Administration - Tech-X Corp

6 7

[Dovecot] which e-mail client can work with recent dovecot?
by Sergey Ivanov 09 Oct '06

09 Oct '06

Hi, I'm trying to use dovecot-1.0.rc7. Before I've used dovecot-1.0 from nightly cvs build of August 08, 2006. It worked perfectly, on Linux 64-bit, you can see spec and patches at http://www.sisyphus.ru/srpm/dovecot/ When I tried to upgrade to rc7 and to recent nightly cvs builds with the same configuration and patches (provided necessary adaptations), it builds O.K, but can not move messages from folder to folder. I've tried the following mail clients: thunderbird-1.5.0.7, evolution-2.0.2, sylpheed-claws-2.0 and KMail-1.7.1 (all from Centos-4.4). KMail refuses to copy (or to move) multiple selected messages, saying:" Error while copying messages.Connection to Server Closed Unexpectedly ...". Evolution is not able to open folders at 3-rd level (like dovecot/2006/09), or it is so slow that I was not able to test moving/copying messages in it. Sylpheed-claws died whan I tried this message copying. Thunderbird tries to move infinetly in a loop, filling the dovecot's log with lines: --- Sep 28 12:56:25 alt64 dovecot: imap-login: Login: user=<seriv>, method=plain, rip=66.80.117.2, lip=192.168.10.8, TLS Sep 28 12:56:25 alt64 dovecot: IMAP(seriv): file mail-cache-transaction.c: line 709 (mail_cache_add): assertion failed: (fixed_size == (unsigned int)-1 || fixed_size == data_size) Sep 28 12:56:25 alt64 dovecot: child 25177 (imap) killed with signal 6 Sep 28 12:56:25 alt64 dovecot: imap-login: Login: user=<seriv>, method=plain, rip=66.80.117.2, lip=192.168.10.8, TLS Sep 28 12:56:25 alt64 dovecot: IMAP(seriv): file mail-cache-transaction.c: line 709 (mail_cache_add): assertion failed: (fixed_size == (unsigned int)-1 || fixed_size == data_size) Sep 28 12:56:25 alt64 dovecot: child 25183 (imap) killed with signal 6 --- (approximitely 2 cicles per second). And when I reinstalled back the previously worked version of dovecot, the problem remains. -- With best regards, Sergey Ivanov.

3 3

[Dovecot] Maildir++ quota inconsistency
by Anand Buddhdev 09 Oct '06

09 Oct '06

I've found what I think is an inconsistency in the Maildir quota implementation. According to the Maildir++ quota specification at: http://www.inter7.com/courierimap/README.maildirquota.html Maildir++ quota can be specified as maximum size, or maximum number of messages, or even both. The size specification is supposed to be in bytes. So I could use '10000000S' to set a quota of around 10MB. Now, the Exim MTA has an independent Maildir++ quota implementation, and it follows the specification, so if I set the quota in Exim to 10000000, it will work perfectly with sqwebmail and courier-imap. However, it doesn't play well with Dovecot, because Dovecot chooses to interpret the quota as kilobytes, rather than bytes. An example: If I set the quota to 10240 in Dovecot, it creates a maildirsize file with the value 10240000 in it. If I then set the quota to 10M in Exim, Exim calculates that as 10485760. It detects that the value in the maildirsize file is wrong, and recreates the file with a quota of 10485760 bytes. Exim's behaviour is consistent with the courier family of packages, as well as the specification, so I'm venturing to say that Dovecot's implementation is slightly non-standard, and should be fixed so that the quota setting is interpreted as bytes, and not as kilobytes, to avoid a situation like the above. -- Anand

4 4