- dovecot - dovecot.org

[Dovecot] patch for UID 0 problem
by Kai Arif 15 Nov '11

15 Nov '11

Hi all, attached you'll find a patch for cmd-thread.c which addresses a problem with certain clients in conjunction with the use of the UID THREAD REFS command: TAG5 UID THREAD REFS us-ascii SINCE 14-May-2011 * THREAD (0)(246)(247)(248)(249)(250)(252)(253)(254)(255)(256)(257)(258)(259)(260)(261)(262)(263)(264)(265)(266)(267)(268) TAG5 OK Thread completed. The first UID delivered (0) is invalid, some clients - @mail for instance - then try to fetch the invalid UID 0 subsequently and run into problems. The patch actually disables the return of (0) and seems to work for us. Please review and - if OK - incorporate it in the next version. Best Regards Kai -- Kai Arif - System Administrator Inter.net Germany GmbH Knesebeckstraße 59-61 10719 Berlin Germany Fon +49 30 25430 0 Fax +49 30 25430 499 arif(a)team.de.inter.net www.de.inter.net Legal-Information: Inter.net Germany GmbH, HRB #79136, Amtsgericht Berlin Charlottenburg, UST-IdNr:: DE 813 165 159 FA für Körperschaften I Berlin, Geschäftsführer: Jörn Lubkoll Zuständige Regulierungsbehörde: Bundesnetzagentur Chemnitz, Liselotte-Herrmann-Str. 20a, 09127 Chemnitz, Registriernummer: 06/164

2 1

[Dovecot] Managing public folder ACL files
by Keith Edmunds 14 Nov '11

14 Nov '11

We have a customer with a large public folder hierarchy. They occasionally make requests to have the public folder ACLs changed; for example: "please give user X access to all public folders" (that's nearly 1700 folders). Worse: "please give user Y access to all sales folders" (there are 1450 sales folders). The problem is that there are (naturally) spaces in the folder names, which makes command line manipulation challenging. We've ended up with some astonishingly hacky Python scripts that enter each folder starting with (for example) ".sales" and replacing the dovecot-acl file to try to fulfil the above requests. One day our script are going to get it wrong, or requests will become more complex ("give X access all sales/CustA folders, Y access to all sales/CustB folders, and Z access to all sales folders). There must be a Better Way. How do others manage divergent ACLs within large public folder hierarchies? Thanks, Keith

5 4

[Dovecot] [re] patching dovecot for managesieve/sieve
by Scott Lewis 14 Nov '11

14 Nov '11

My apologies for the repost yesterday; it was not intentional. I was attempting to post a followup from my mobile, when something went awry with the editing options on my phone. Anyway.. I have managed to download and compile my own patched dovecot/dovecot-sieve/dovecot-managesieve modules from scratch, with Thanks to this page hardc0l2e.wordpress.com/2010/02/26/managesieve-with-dovecot-on-centos-5-4/ But when I run http://mydomain.com/src/configtest.php , I am still getting the following rather non-descriptive error: "I could not determine the capabilities for Sieve Mail Filtering. Perhaps connectivity with ManageSieve server (if backend=ManageSieve) is bad?" Where else can I look to resolve this? should managesieve show up as its own /etc/init.d service? Or does dovecot simply control it? How can I confirm that deliver is being used as my LDA? Thanks again, Scott

2 1

[Dovecot] Restoring Mails from Backup Archive
by Andreas Cieslak 14 Nov '11

14 Nov '11

Hi List, i am trying to restore mails from an backup-archive which was made with rsnapshot. All the mails in the archive look similar like the following: -rw------- 2 1014 1015 3308 8. Aug 13:42 1312803768.V809I266a00aM505178.server:2,ST Now I copy the files from the archive into the Maildir/cur directory of the user. Then I set the permissions etc. and log in with the user account via Squirrelmail. The restored mails aren't in the INBOX, and when I go into the Maildir/cur dir of the user, the restored mails are gone. Possibly deleted after the login. Had anyone some similar experiences ? Any hints ? Kind regards Andreas

2 3

[Dovecot] metadata plugin problems
by Georg Martius 13 Nov '11

13 Nov '11

Hi, I have trouble with the metadata plugin. I compiled dovecot 2.0.15 from source and also the plugin [2] separately. I work on debian/lenny. I had some trouble compiling it (autoconf somehow didn't insert the DOVECOT_IMAP_INCLUDE variable, I have not idea why) Anyway, I did as described in [1]. Do I have to create: the file /var/lib/dovecot/shared-metadata ? The server starts without errors, but I get for instance the following error message: "Failed to write some annotations for 'Contacts' on the IMAP server. SetMetaData failed, server replied: A000076 NO Parsing entry failed" from my KMail. How can I test that the plugin is actually active and working? Any help would be appreciated. Regards, Georg [1]http://www.mail-archive.com/dovecot@dovecot.org/msg38887.html [2] http://hg.dovecot.org/dovecot-metadata-plugin

1 0

[Dovecot] Dovecot v2.0.13 unix_listeners
by Matthew Brown 13 Nov '11

13 Nov '11

Could somebody be able to explain to me what the various unix_listeners do in the Dovecot 2.x configuration (specifically in 10-master.conf). Currently, for postfix to use for local delivery, I have: service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } and for auth I have: service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { mode = 0666 user = vmail } } So what does each one specifically do? Also, does somebody know of a resource that can explain the mode setting? I couldn't seem to find anything on the wiki.. Sorry if these questions seem simple, Im still trying to get a grips with dovecots workings. MDA: Dovecot v2.0.13 MTA: SMTP User & Virtual Domain Management: MySQL Cheers, Matthew

2 1

[Dovecot] TLS Authentication Confusion
by Carlos Mennens 11 Nov '11

11 Nov '11

I asked a user today to make sure his incoming and outgoing email was using TLS. He told me it wasn't possible because my Dovecot / Postfix daemons were only listening on TCP 25 & 143 according to a port scan he did. He told me the only way I could enable encrypted secure sessions between the client & server is to enable port 993 (IMAPs). I told him that TLS is supported on my mail server over the default ports TCP 25 / 143 and that many consider IMAPs to be legacy. I sent him a telnet session of my PC communicating with my server & it shows TLS is available. I just wanted to be sure I was correct with the information above or am I completely wrong and I do indeed need TCP port 993? I know this is the Dovecot mailing list but since Dovecot and Postfix both use and support TLS in their configuration files, I figured I would ask here for your help! carloss@pc1:~$ telnet mail.holyghost.org 25 Trying 192.168.4.100... Connected to mail.holyghost.org. Escape character is '^]'. 220 mail.holyghost.org ESMTP Postfix EHLO pc1.holyghost.org 250-mail.holyghost.org 250-PIPELINING 250-SIZE 20480000 250-VRFY 250-ETRN 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN Below is a snip from my mail logs showing TLS: Nov 9 10:26:39 mail dovecot: imap-login: Login: user=<carlos>, method=PLAIN, rip=::ffff:192.168.4.100, lip=::ffff:192.168.4.100, TLS The above snip from my log means that I'm connecting to Dovecot via TLS, correct?

8 7

[Dovecot] Restarting dovecot periodically fails with "Socket already exists: /var/run/dovecot/anvil"
by James Page 11 Nov '11

11 Nov '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello restarting dovecot regularly fails with version 2.0.13 on Ubuntu 11.10 due to a running child process exiting after the main dovecot process. Oct 13 15:04:58 ubuntu dovecot: master: Error: service(anvil): Socket already exists: /var/run/dovecot/anvil Oct 13 15:04:58 ubuntu dovecot: master: Error: service(anvil): Socket already exists: /var/run/dovecot/anvil-auth-penalty Oct 13 15:04:58 ubuntu dovecot: master: Fatal: Failed to start listeners Oct 13 15:04:58 ubuntu kernel: [11132.825253] init: dovecot main process (8668) terminated with status 89 The dovecot/anvil process appears to be the cause of the problem (snapshot of running dovecot processes just after main dovecot process stops): root 8418 8080 0 15:02 pts/0 00:00:00 stop dovecot root 8419 1 0 15:02 ? 00:00:00 dovecot/anvil root 8422 8420 0 15:02 ? 00:00:00 grep dovecot This is an Ubuntu specific issue as we use upstart to manage dovecot which monitors the status of the main dovecot process; the Debian init script appears to make provision for this happening. I can work around this in the upstart configuration but it does look like a potential bug in the sub-process handling in dovecot. Any help much appreciated - please feel free to comment on https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/873390 as well. Regards - -- James Page Ubuntu Core Developer - ----------------------------------- dovecot -n # 2.0.13: /etc/dovecot/dovecot.conf # OS: Linux 3.0.0-12-generic-pae i686 Ubuntu 11.10 mail_location = maildir:~/Maildir managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 sieve ssl_cert = </etc/ssl/certs/dovecot.pem ssl_cipher_list = ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 10 } protocol pop3 { mail_max_userip_connections = 10 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = postmaster quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r } -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJOlwAJAAoJEL/srsug59jD1e4QAIB0/OhBhgr7HYqJNh3d1f69 8vGl6LSb2jjJb6bI+GX8QRHDDHXs6g3RadpHTEnDngJPLRPJxnnmr/mqcG+sAeYa 92shRyWnZQFEHJkl9hE1t1OS7skpLezWgSl6nOtzkRxm3yB0+w81PyQZVH2QArKf dATww3t0hMd3ybPEJnZwSlIQ/82i79qd8RZd1orERdIKN1wIyhb2uOi1XXBvGHZo hZKhO1sv3vz1RLpJXeWIVUNK8RQHJcvAOdqvTeT7kzx1gdxy3ycr7WOTUFY3Nc83 SYFyV9/miSNc45n+eDnsoknwggn0JWMkMA1jzRQz9OGCWFkJVFIuOE9jwJcFP6HY +8OnWwgdu5qNQ6nrn4+M1dB1MrFV5aFQmSuXsuAFXkCYywajdVhNyTkC8wERUBf1 NMv4PQRP0tA/UOOy9qNnNf9y3kQ1ItJ5ZhBTOO5WctnowYHDTWtnoxD7m0aEM1rA NH1TFolUgeiT6B9xFcreq42qEVYItKV60o2gv8fMDXwtkSjfDfJ2/88/45dcTOuK t+qUZnpI+AgCak7AfYShj1SjYN80BbpPpQ0WtG6MObXBZZl84paNpAUibUfN0tPy cEscYqUhkkptbfenJe3ldz0S2AhlrDTFk3cWGKwwlKY+29vBsoZtbgIamgrOKLX9 AbdvqFx8gnYe5af1k3eL =6Mfk -----END PGP SIGNATURE-----

2 2

[Dovecot] undefined symbol: o_stream_switch_ioloop
by Frank Elsner 11 Nov '11

11 Nov '11

Hi, running dovecot-2.0.14 under Fedora 14 with kernel 2.6.35.14-103.fc14.i686.PA I've found a strange error in log which I've nerver observed before when startung dovecot: auth-worker: Error: dlopen(/usr/local/dovecot/lib/dovecot/auth/libauthdb_imap.so) failed: /usr/local/dovecot/lib/dovecot/auth/libauthdb_imap.so: undefined symbol: o_stream_switch_ioloop Dovecot seems to work normal despite the error message. Any enlightment welcome. --Frank Elsner

2 3

[Dovecot] LDAP expired password
by roberto palmarin 10 Nov '11

10 Nov '11

hi all, I'm using postfix, LDAP, dovecot and horde for webmail. user and password information is stored in LDAP. I'm attempting to get password aging working properly and am not having much luck. even if password has expired user can login, can i tell dovecot to control the LDAP field shadowexpired? or is there some other way to check properly that the password is expired before allowing the user log in? thank's /roby

4 5