September 2010 - dovecot

[Dovecot] Expunged GUID mismatch for UID error
by Xavier Pons 23 Sep '10

23 Sep '10

Hi, we have upgraded from v2.0.1 to v2.0.3 yesterday, trying to solve the "dovecot-uidlist: Duplicate file entry" errors. Now, at the moment, we don't get these errors, but when I try to expunge mails from my trash folder I get a lot of errors: Sep 23 14:24:51 imap1 dovecot: imap(user): Error: Mailbox Trash: Expunged GUID mismatch for UID 20193: 442b5ef0c3d3bf3cf4cb619944dce8e4 vs 0431b9bee05471199fabbc05af3a87a5 (with different GUIDs, and UIDs) and the mails are not expunged from Trash mailbox. Also, I have tried with "doveadm force-resync -u user Trash" and "doveadm expunge -u user mailbox Trash ALL" but not resolve the problem... Thanks Xavier Pons

3 3

Re: [Dovecot] service(imap-login): chiled ... killed with signal 11
by Timo Sirainen 23 Sep '10

23 Sep '10

On Thu, 2010-09-23 at 08:55 +0200, Burckhard Schmidt wrote: > #1 0xfecd750c in free () from /lib/libc.so.1 > No symbol table info available. > #2 0xfefc145c in CRYPTO_free () from /opt/csw/lib/libcrypto.so.0.9.8 > No symbol table info available. > #3 0xff04a13c in sk_free () from /opt/csw/lib/libcrypto.so.0.9.8 > No symbol table info available. > #4 0xff153bf0 in SSL_CTX_free () from /opt/csw/lib/libssl.so.0.9.8 My guess: You have an old and buggy OpenSSL library. I remember someone else also had a similar (same?) problem that went away when upgrading OpenSSL.

2 1

[Dovecot] Auth error
by Thiago Henrique 23 Sep '10

23 Sep '10

Hello, I'm testing Dovecot 2.0. I plan to use Dovecot 2.0 with thousands of domains per server. My user base is under virtual MySQL. I my tests, the authentication fails intermittently, and I could not find what's wrong. Can anyone help me? ################################################################################ Sep 22 16:31:16 box5 dovecot: last message repeated 9 times Sep 22 16:31:16 box5 dovecot: auth: Debug: auth client connected (pid=9249) Sep 22 16:31:20 box5 dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011lip=1.2.3.4#011rip=1.2.3.4#011lport=143#011rport=45348#011resp=AHRoaWFnbz1hZG1pbmxpbnV4LmNvbS5icgAxcWF6MndzeA== Sep 22 16:31:20 box5 dovecot: auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Sep 22 16:31:20 box5 dovecot: auth: mysql: Connected to mysqlserver.com (database_name) Sep 22 16:31:20 box5 dovecot: auth: Debug: sql(account=domain.com,1.2.3.4): query: SELECT AccountName AS userdb_username, Password AS password, MailLocation AS userdb_mail, concat('*:bytes=', ItQuota, 'M') AS userdb_quota_rule FROM Account WHERE AccountName = 'account=domain.com' Sep 22 16:31:20 box5 dovecot: auth: Debug: client out: OK#0111#011user=account=domain.com Sep 22 16:31:20 box5 dovecot: auth: Debug: master in: REQUEST#0111#0119249#0111#011ba525e3c7ea765255e814a27c5ef8294 Sep 22 16:31:20 box5 dovecot: auth: Error: Master requested auth for nonexistent client 9249 Sep 22 16:31:20 box5 dovecot: imap-login: Internal login failure (auth failed, 1 attempts): user=<account=domain.com>, method=PLAIN, rip=1.2.3.4, lip=1.2.3.4, mpid=9225 ################################################################################ Thank you in advance. Best Regards -- []'s Thiago Henrique Network Administration Digirati Networks K8 Networks

2 1

[Dovecot] Sieve force SSL
by Lukas Haase 23 Sep '10

23 Sep '10

Hi, I have activated only imaps and managesieve. As sieve is running on a different port/protocol: Can I make sure that sieve can ONLY be used with SSL/TLS? As the credentials are transmitted I only offer services with SSL (IMAPS, SMTP over SSL, ...). For sieve I am not sure about this. If there is the possibility that user's credentials are transmitted in plain text I would block the port from the firewall, else I would offer my users the feature to change their rules with their own client (e.g. Thunderbird sieve). Regards, Luke

2 3

[Dovecot] Dovecot LDA, virtual users, multiple uids: No luck
by Toni Mueller 23 Sep '10

23 Sep '10

Hi, I'm trying to get Dovecot's deliver to create and use mailboxen with one uid per user. Reading the wiki, I decided to go with the sudo attempt, but I'm stuck because deliver fails to create the intermediate directories. The auth.log has this on the matter: sudo: dovelda : TTY=unknown ; PWD=/var/spool/postfix ; USER=root ; COMMAND=/usr/lib/dovecot/deliver -f toni(a)bogus.oeko.net -d dick(a)example.com Using strace on 'deliver', I get this: # su - dovelda $ echo "blubber" |sudo strace /usr/lib/dovecot/deliver -f toni(a)bogus.oeko.net -d dick(a)example.com ... geteuid() = 0 getgid() = 0 setgid(2000) = 0 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ setgroups(1, [2000]) = 0 setuid(2100) = 0 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ setuid(0) = -1 EPERM (Operation not permitted) getgid() = 2000 getegid() = 2000 setgid(0) = -1 EPERM (Operation not permitted) close(6) = 0 geteuid() = 2100 geteuid() = 2100 and subsequently, creating the directories fails. The values in the underlined lines above, 2100 and 2000, are from the database entry of the user I want to deliver the email to. My /etc/sudoers has this for dovelda: dovelda ALL=NOPASSWD:/usr/lib/dovecot/deliver dovelda ALL=NOPASSWD:/usr/bin/strace I'm using a Debian/Lenny system with amd64 and this package for Dovecot: # dpkg -l 'dovecot*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-==============-==============-============================================ ii dovecot-common 1:1.2.13-1~bpo secure mail server that supports mbox and ma ii dovecot-imapd 1:1.2.13-1~bpo secure IMAP server that supports mbox and ma Kind regards, --Toni++

2 2

[Dovecot] Sieve error on Quota full (Dovecot 2.0.3)
by Cassidy Larson 23 Sep '10

23 Sep '10

Just switched my storage boxes to 2.0.3 with Pigeonhole. Noticing for those that have quota fulls, my syslog is getting full of errors from sieve: dovecot: lda(user(a)host.com): Error: sieve: script /data/mail/host.com/user(a)host.com//.dovecot.sieve failed with unsuccessful implicit keep (user logfile /data/mail/host.com/user(a)host.com//.dovecot.sieve.log may reveal additional details) Checking the .dovecot.sieve.log I see: sieve: info: started log at Sep 22 00:38:11. error: msgid=<dovecot-1285137490-378260-0(a)storagebox.host.com>: failed to store into mailbox 'INBOX': Quota exceeded ( mailbox for user is full). Any way to suppress these quota full messages from filling up my logs and .dovecot.sieve.log ? I do like the .dovecot.sieve.log for debugging, but regular quota warnings seems excessive. Thanks, Cassidy

4 5

[Dovecot] Vpopmail support broken
by Matt Brookings 23 Sep '10

23 Sep '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 My apologies if I'm posting for information which has already been supplied to the list. I searched and all I found was people talking about the change in 2.0.3, but no details on the commit other than "I was tired of people telling me it crashes". We have not received any reports for the 5.4 or 5.5 branch of vpopmail causing crashes in Dovecot. That being said, if there is a problem, we would like to provide a fix. Again, if details on the specifics of the problem have been supplied, I apologize. Can anyone please provide me some reproduction details for Dovecot 2.0.3's vpopmail plugin compiled against vpopmail 5.4.30+ or 5.5.0? Removing the "vpopmail support broken" line from the configure script, compiling and running seemed to work short-term. I was able to authenticate against the vpopmail plugin. I tested with vpopmail 5.4.32 and 5.5.0 using the cdb authentication module. Thanks! - -- /* Matt Brookings <matt(a)inter7.com> GnuPG Key FAE0672C Software developer Systems technician Inter7 Internet Technologies, Inc. (815)776-9465 */ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyaI6MACgkQIwet2/rgZyz8ugCeOnyz5DfV9FwrHfEmIroeznPv kZYAn0TnbEULiuZqJANoZsfhOahhsA0H =LHP4 -----END PGP SIGNATURE-----

4 12

[Dovecot] xz compression support
by Attila Nagy 23 Sep '10

23 Sep '10

Hello, Just wondering: Dovecot has gzip/bzip2 compression/decompression support. According to this: http://stephane.lesimple.fr/wiki/blog/lzop_vs_compress_vs_gzip_vs_bzip2_vs_… gzip and bzip2 aren't really useful together. While gzip can offer speed and a reasonable amount of compression ratio, bzip2 is slow, especially on decompression, which Dovecot does more frequently than compression (1 vs many). So: is it planned to include xz (liblzma) support? It would be useful especially for compressing old mails in the background (due to the resource intensity of the compression phase). Thanks,

2 1

[Dovecot] Panic: file mailbox-list-fs.c
by Burckhard Schmidt 22 Sep '10

22 Sep '10

Hi, I have dovecot 2.0.3. Mailboxes have been converted with dsync from mbox to maildir last week. There it was still version 2.0.2. A user "produces" now this error: imap(userx): Panic: file mailbox-list-fs.c: line 150 (fs_list_get_path): assertion failed: (mailbox_list_is_valid_pattern(_list, name)) Error: Raw backtrace: follows. And all other imap processes are closing down. dovecot starts again. master: Info: Dovecot v2.0.3 starting up Additional mail_location = maildir:~/maildir:INDEX=/addons/index/%u:CONTROL=~/control:LAYOUT=fs namespace { inbox = yes list = yes location = prefix = separator = / subscriptions = yes type = private } Are there charachters which are not allowed or is there a reached a maximal length? regards -- Mit freundlichen Gruessen --- Burckhard Schmidt

2 3

[Dovecot] "Documentation" link from http://www.dovecot.org/
by William Blunn 22 Sep '10

22 Sep '10

On the Dovecot home page http://www.dovecot.org/ we have a link "Documentation" which links to the Dovecot 1.x wiki ( http://wiki.dovecot.org/ ). There is a question mark in my mind as to whether that is a good idea considering as how the current stable version of Dovecot appears to be 2.0.x. In the Dovecot 1.x wiki, there is a pink stripe across the top of the page which says that the documentation is for Dovecot 1.x. It looks as though the intention was to make that prominent so as to guide visitors to the right documentation, and I think to a certain extent it may work. But I am wondering if perhaps the stripe could be too easily missed. People might start browsing around in the Dovecot 1.x wiki without it even occurring to them that there was a whole another wiki for 2.x. I have an idea: Perhaps the "Documentation" link on the home page could be re-worked to something like Documentation v2.x v1.x where "v2.x" and "v1.x" are links to the two wikis. This would make it obvious that there was different documentation available for v2.x and v1.x, and encourage visitors to choose the appropriate set. Bill

3 8