- dovecot - dovecot.org

[Dovecot] dovecot 2.04 broke folder sharing
by Robert Schetterer 02 Oct '10

02 Oct '10

Hi Timo, upgrading from 2.03 to 2.04 broke folder sharing at my setup double checked this with tests reverting versions etc setting acl and subcriptions are working with 2.04, but in difference to 2.03 no shared subfolder is created at acl/subscription set time so subscribing afterwards fail with ignore message by bad subscription the mails store is on drbd with ocfs2 i didnt change any other config parameter during the tests so some patch must have changed folder sharing behavior from 2.03 to 2.04 speculate something with default hardlinks etc? any idea ? -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

2 10

[Dovecot] ACL handling bugs in v1.2.8+ and v2.0
by Timo Sirainen 02 Oct '10

02 Oct '10

I thought I'd write one mail about this, rather than duplicate the whole thing to both v1.2.15 and v2.0.5 release announcements. So, ever since this commit: 2009-11-10 Timo Sirainen <tss(a)iki.fi> * src/plugins/acl/acl-backend-vfile.c: acl: Merge group rights if user belongs to more than one. [76ff6831c9ae] The ACLs were being merged, rather than fully replaced, a bit too often. Since this is about merging, the problem could have happened only when using more than one entry in the ACL file. The main problems created by this were: a) If admin wanted to remove some rights from mailboxes in user's private namespace (e.g. symlinked shared mailboxes), they may not have gotten removed. b) When mixing up multiple ACL entries, such as groups/users the more specific entry may not have replaced the previous entry (e.g. group-override may not have worked as expected). The bug happened when two or more ACL entries of same "type" existed. The first entry was handled correctly, but the next ones may have only been adding ACLs rather than replacing them. For example if you had the following ACL file: group=people lrwi user=foo lr user=bar lr So basically everyone in "people" group should have "lrwi" rights, but foo and bar users should have only "lr" rights. If foo and bar didn't belong to people group, everything would work as expected. If they did, then what would happen is: * foo would work correctly, because it was the first entry of user type. * bar would keep "lrwi" rights, because the previous entry (user=foo) was of the same type (both are "user" type), so Dovecot decided to add the rights on top of group=people entry rather than replace them. BTW. The other ACL bug/"feature" of automatically adding admin rights that was fixed in v1.2.15 was already fixed in v2.0.beta2.

1 0

[Dovecot] Outlook 2010 Delayed Emails
by Munroe Sollog 02 Oct '10

02 Oct '10

dovecot --version = 1.2.11 dovecot -n: http://pastebin.com/ahCpdC0F I have a user that has no problem viewing email from roundcube (webmail) but Outlook 2010 doesn't seem to download random messages for a day or two, then they suddently show up. I saw the wiki had some suggestions for older versions of Outlook to fix other problems, but I didn't really see anything like this. Any help would be appreciated. Thanks. -- Munroe Sollog Digirati Consulting www.digiraticonsulting.com 610-332-7234 x805

2 2

[Dovecot] zlib plugin weirdness
by Kyle Wheeler 01 Oct '10

01 Oct '10

Hello, I'm trying to get the zlib plugin working on my 2.0 server. I started with an mbox that Dovecot can read just fine. Then I gzipped it, and now Dovecot complains that it's corrupted: Error: Next message unexpectedly corrupted in mbox file /var/lib/vpopmail/domains/memoryhole.net/kyle/Maildir/Archive/Intellego.gz at 1907 Error: Unexpectedly lost From-line from mbox file /var/lib/vpopmail/domains/memoryhole.net/kyle/Maildir/Archive/Intellego.gz at 1907 Error: zlib.read(/var/lib/vpopmail/domains/memoryhole.net/kyle/Maildir/Archive/Int…: unexpected EOF at 1765954 Error: i_stream_get_size() failed with mbox file /var/lib/vpopmail/domains/memoryhole.net/kyle/Maildir/Archive/Intellego.gz: No such file or directory A similar thing happens when I bzip it. I was worried that it wasn't even using the zlib plugin, but since it makes reference to zlib.read, I assume that it is. Does anyone know what might be going wrong? ~Kyle -- The only way to oppose a bad idea is to replace it with a good idea. -- Jack Kemp

2 5

[Dovecot] LMTP don't accept jobs for system users
by Alejandro Maurich 01 Oct '10

01 Oct '10

Hi, I'm trying to configure Dovecot 2.0.1 to deliver email to users in /etc/passwd using the Dovecot LMTP service. So far, I can sucessufully do POP3 for system users, but when Postfix tries to deliver email to the Dovecot LMTP service the LMTP reject the job with: "User doesn't exist ale(a)centos54.mydomain.com" Any suggestions? The user 'ale' is a valid user: # grep ale /etc/passwd ale:x:500:500:Alex:/home/ale:/sbin/nologin This is the dovecot -n output: # 2.0.1: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-164.el5xen i686 CentOS release 5.4 (Final) disable_plaintext_auth = no mail_location = maildir:~/Maildir mail_privileged_group = mail mbox_write_locks = fcntl passdb { args = session=yes failure_show_msg=yes dovecot driver = pam } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 10050 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } protocol lmtp { mail_plugins = $mail_plugins }

2 1

[Dovecot] IMAP connection timeout value?
by Tamas Kadar 01 Oct '10

01 Oct '10

So we're having some ISP issues lately, meaning we have to reboot our cable modem like 2-3 times a day. An unfortunate side-effect I've found is, once the users max out their connection limit (which I've set to 10, and many people do), if we reboot the cable modem, they can't log in cause their connections get 'stuck' until I `doveadm kick` them, or wait for the connections to timeout which takes ??? minutes. Can I adjust that value to something like 30 seconds? Thanks and best regards, KT

5 8

[Dovecot] SSL strangeness with dovecot-lda in 2.0.4
by Glyn Faulkner 01 Oct '10

01 Oct '10

Hello, First of all, thank you for developing a fantastic IMAP server! I've just upgraded to 2.0.4 (from 2.0.1) and when I try to run /usr/lib/dovecot/deliver (either directly from the commandline, or from within the MTA) I get the following error: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: ssl enabled, but ssl_key not set I converted my old config file settings using "dovecot -c /etc/dovecot/dovecot.orig -n > /etc/dovecot/dovecot.conf" as some of the option names had changed. The computer has been rebooted since the upgrade. The odd thing is that "dovecot -n" says that ssl_key _is_ set: [gerbil@pleione dovecot]$ dovecot -n # 2.0.4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.35-ARCH i686 listen = 127.0.0.1 mail_location = maildir:~/Common/Maildir passdb { driver = pam } service auth { user = root } service imap { process_limit = 5 } service pop3 { process_limit = 5 } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } protocol lda { mail_plugins = sieve postmaster_address = postmaster@localhost } Both of the .pem files do exist (they are unchanged from before the upgrade), and are readable by root: [gerbil@pleione dovecot]$ ls -al /etc/ssl/*/dovecot.pem -rw-r--r-- 1 root root 1005 Nov 2 2009 /etc/ssl/certs/dovecot.pem -rw------- 1 root root 887 Nov 2 2009 /etc/ssl/private/dovecot.pem Any advice you can give would be gratefully received. Many thanks, Glyn

2 2

Re: [Dovecot] dovecot Digest, Vol 90, Issue 3
by arif khwaja 01 Oct '10

01 Oct '10

Dear All, Thanks for all your replied but still I don't know how to install from 1.0.7 to 1.2.14. What should I consider to keep the same configuration during or after upgrade? It is the first time I am trying to upgrade my Dovecot. Thank a lot for your help --- On Fri, 1/10/10, dovecot-request(a)dovecot.org <dovecot-request(a)dovecot.org> wrote: From: dovecot-request(a)dovecot.org <dovecot-request(a)dovecot.org> Subject: dovecot Digest, Vol 90, Issue 3 To: dovecot(a)dovecot.org Date: Friday, 1 October, 2010, 15:25 Send dovecot mailing list submissions to dovecot(a)dovecot.org To subscribe or unsubscribe via the World Wide Web, visit http://dovecot.org/cgi-bin/mailman/listinfo/dovecot or, via email, send a message with subject or body 'help' to dovecot-request(a)dovecot.org You can reach the person managing the list at dovecot-owner(a)dovecot.org When replying, please edit your Subject line so it is more specific than "Re: Contents of dovecot digest..." Today's Topics: 1. Re: Dovecot v0.99.13-3 upgrade to 1.0.15-2 ?? (Noel Butler) 2. Re: how to upgrade dovecot (Noel Butler) 3. Re: Dovecot v0.99.13-3 upgrade to 1.0.15-2 ?? (Jerry) 4. Re: Dovecot v0.99.13-3 upgrade to 1.0.15-2 ?? (Jerry) 5. Re: how to upgrade dovecot (fakessh) 6. Re: Dovecot v0.99.13-3 upgrade to 1.0.15-2 ?? (Stan Hoeppner) 7. v1 ok, v2 not (Alberto) 8. Re: Possible bug with proxy in 2.0.4 (Ed W) ---------------------------------------------------------------------- Message: 1 Date: Fri, 01 Oct 2010 22:37:25 +1000 From: Noel Butler <noel.butler(a)ausics.net> Subject: Re: [Dovecot] Dovecot v0.99.13-3 upgrade to 1.0.15-2 ?? To: dovecot(a)dovecot.org Message-ID: <1285936645.21841.19.camel@tardis> Content-Type: text/plain; charset="utf-8" On Fri, 2010-10-01 at 14:20 +0200, Jakob Curdes wrote: > All true, but there is a current 1.2.14 out there which should probably > be preferred ove a two-and-a-half year old 1.0.15. > Jakob > Indeed, but some people who use certain distros are scared shitless of using source packages and will insist on using a several yo version because thats all <insert distro X or Y here> provides, the 1.2 branch is rock solid stable and time proven, if distro X/Y only oifferes 1.0.x, well, that says a lot about distro X/Y, we all know who X 'n Y are, without mentioning names :)

1 0

[Dovecot] Possible bug with proxy in 2.0.4
by Ed W 01 Oct '10

01 Oct '10

Hi, I *think* there might be an auth/proxy bug in 2.0.4 Specifically I cloned my 1.2 virtual machine, upgraded the clone to 2.0.4 and tested it by trying to login using CRAM-MD5. I get the errors: Sep 29 22:50:23 mail_test dovecot: imap-login: Disconnected (auth failed, 1 attempts): user=<demo(a)abc.com>, method=CRAM-MD5, rip=x.x.x.x, lip=x.x.x.x, mpid=0, TLS Sep 29 22:50:30 mail_test dovecot: auth: mysql: Connected to mysql-local (postfix) Sep 29 22:50:30 mail_test dovecot: imap-login: Error: proxy: password not given: user=<demo(a)abc.com>, method=CRAM-MD5, rip=x.x.x.x, lip=x.x.x.x, mpid=0, TLS Interestingly the config here (accidently as it happens) causes the connection to use the dovecot "proxy" feature back to the original 1.2 machine. I updated my config so that everything stays on the 2.0.4 machine and authentication proceeds normally, messages about generating MD5 hash from the DB, etc, logged in ok. I then change the configuration so that the 2.0.4 machine proxies the connection back to the 1.2 machine (again) and try to login to the 2.0.4 machine and get the same errors as above. Seems like the error is only when proxying (needless to say, the old 1.2 machine works fine with CRAM and that's how it's normally accessed, so also does the 2.0.4 machine, it's only proxying one to the other which isn't apparently working?) It's late and so I haven't managed to probe the 1.2 machine too much, but initially looking at the log files I don't see any evidence of the 2.0.4 machine actually contacting it? Does this make sense? Thanks Ed W

2 4

[Dovecot] v1 ok, v2 not
by Alberto 01 Oct '10

01 Oct '10

hello everybody! This's my very first post in dovecot. I'm installing a new server for backup site, with qmail + vpopmail 5.4.32 + dovecot. Production server, more or less outdated, runs with Couier Imap, but everybody know the history.. I've been fighting for several days...And no luck with version 2.0.4, 2.0.3 neither. My first asumption was to review things thousand of times due to newbie condition... This morning I've tried version 1.2.14 and voila! , it works perfectly! The error log with version 2 was the famous unkown user one: dovecot: auth: vpopmail(test4(a)adomain.com,10.206.16.10): unknown user test4 user worked perfectly with pop3... Just FYI, is this can help. Regards!

1 0