May 2012 - dovecot - dovecot.org

[Dovecot] namespace from snapshots
by Karl Oulmi 21 Aug '12

21 Aug '12

hi all, I'm trying to give access to snapshots taken from by dell iscsi MD3200i to my maildirs users. snapshot are mounted in read only mode from my FreeBSD box. In my /usr/local/etc/dovecot/conf.d/10-mail.conf, I have : namespace inbox { inbox = yes } namespace da1 { prefix = INBOX.backup.da1. hidden = no list = yes inbox = no location = maildir:/da1/%u/Maildir type = private } I have two problems : - In my log, dovecot complain about the fact that my snapshot filsystem is read only Error: open(/da1/test2(a)toto.com/Maildir/.Trash/dovecot-uidlist) failed: Read-only file system The second problem is that through my thunderbird I can't see the Inbox saved in the snapshot (whereas I see Sent and Trash folders) If anyone could help me, It would be nice. Regard, Karl.

3 7

[Dovecot] Statistics scripts
by Timo Sirainen 08 Aug '12

08 Aug '12

I wrote two scripts, which you can use with the stats plugin enabled to get a better "doveadm stats top" than it currently is: http://dovecot.org/tools/stats-top.pl http://dovecot.org/tools/stats.pl

2 1

[Dovecot] mysql auth failover failing
by Paul B. Henson 29 Jul '12

29 Jul '12

We are running dovecot to provide authentication for postfix, using two mysql servers in a multi-master replication set as the password source: ---------------------------------------- # 2.0.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.37-gentoo-r4 x86_64 Gentoo Base System release 2.0.2 auth_mechanisms = plain login digest-md5 cram-md5 auth_verbose = yes passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocols = none service auth-worker { unix_listener auth-worker { user = postfix } user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = postfix } ssl = no userdb { driver = passwd } --------------------------------------- With an sql config of: ------------------------- driver = mysql connect = host=mysql-1.unx.csupomona.edu host=mysql-2.unx.csupomona.edu dbname=idmgmt user=postfix password=XXXXXXX default_pass_scheme = PLAIN password_query = XXXXXXXXX ------------------------- According to the sample SQL configuration file "HA / round-robin load-balancing is supported by giving multiple host settings, like: host=sql1.host.org host=sql2.host.org". However, as far as I can tell dovecot only connects to the first listed host, and processes all queries through it, there does not appear to be any load-balancing going on. That's not necessarily a dealbreaker; however, high-availability does not appear to be working either. If I shutdown the first mysql server, dovecot starts to log connection failures: Sep 9 15:47:34 tweak dovecot: auth: Error: mysql(mysql-1.unx.csupomona.edu): Connect failed to database (idmgmt): Can't connect to MySQL server on 'mysql-1.unx.csupomona.edu' (111) - waiting for 1 seconds before retry Sep 9 15:47:39 tweak dovecot: auth: Error: mysql(mysql-1.unx.csupomona.edu): Connect failed to database (idmgmt): Can't connect to MySQL server on 'mysql-1.unx.csupomona.edu' (111) - waiting for 25 seconds before retry And postfix starts to fail authentications: Sep 9 15:47:35 tweak postfix/smtpd[5119]: warning: bender.iitsys.csupomona.edu[134.71.250.134]: SASL DIGEST-MD5 authentication failed: Connection lost to authentication server Now and again the authentication process dies: Sep 9 15:47:39 tweak dovecot: auth: Panic: file auth-request-handler.c: line 697 (auth_request_handler_flush_failures): assertion failed: (auth_request->state == AUTH_REQUEST_STATE_FINISHED) Sep 9 15:47:39 tweak dovecot: auth: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x3f71a) [0x7f25822ca71a] -> /usr/lib64/dovecot/libdovecot.so.0(+0x3f766) [0x7f25822ca766] -> /usr/lib64/dovecot/libdovecot.so.0(+0x198ca) [0x7f25822a48ca] -> dovecot/auth() [0x4137f4] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0xd4) [0x7f25822d5fe4] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x5b) [0x7f25822d6bcb] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7f25822d5c48] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f25822c3de3] -> dovecot/auth(main+0x2be) [0x4179de] -> /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f2581898bbd] -> dovecot/auth() [0x40bdc9] Sep 9 15:47:39 tweak dovecot: master: Error: service(auth): child 4154 killed with signal 6 (core dumps disabled) Requests start to pile up: Sep 9 15:51:46 tweak dovecot: auth: Warning: auth workers: Auth request was queued for 25 seconds, 45 left in queue Lookups time out: Sep 9 15:57:22 tweak dovecot: auth: Error: auth worker: Aborted request: Lookup timed out This occasionally pops up: Sep 9 15:58:38 tweak dovecot: auth: Fatal: net_connect_unix(auth-worker) failed: Resource temporarily unavailable And sometimes the auth process gets temporarily disabled: Sep 9 15:58:57 tweak dovecot: master: Error: service(auth): command startup failed, throttling Resulting in more postfix authentication failures: Sep 9 15:58:57 tweak postfix/smtpd[6531]: warning: bender.iitsys.csupomona.edu[134.71.250.134]: SASL DIGEST-MD5 authentication failed: Sep 9 15:59:08 tweak postfix/smtpd[6551]: fatal: no SASL authentication mechanisms To the point where postfix also temporarily throttles smtpd: Sep 9 15:59:21 tweak postfix/master[6526]: warning: /usr/lib64/postfix/smtpd: bad command startup -- throttling Resulting in a complete unavailability of smtp service, not just unavailability of authenticated services. I don't think all authentications fail during the scenario, but I think the majority do. Based on the network traffic, dovecot is almost continuously trying to connect to the first listed server. It sometimes connects to the second listed server, but when it does, the connection does not persist, it goes away almost immediately. Ideally, I would like no authentications to fail if one of the MySQL servers is unavailable. If a few fail just when the server dies, that would be undesirable but acceptable as long as they do not continuously fail while the server is down. Am I doing something wrong? Does the example sql config have incorrect information? We were previously running dovecot 1.2.11, we just recently upgraded to 2. In the previous version, we actually had two different passdb's configured, each one listing only one of the mysql servers. I seem to recall that was the recommendation at the time for high-availability. When that configuration did not seem to work under version 2, I found an updated recommendation to list both servers in the same passdb, which also does not appear to work correctly. I actually went back and tested the older version, and determined it seemed to work okay in the case where the server was up but the service was down, and connections were refused, but also failed a large number of authentication attempts when the server was completely down and connections were timing out. Thanks much... -- Paul B. Henson | (909) 979-6361 | http://www.csupomona.edu/~henson/ Operating Systems and Network Analyst | henson(a)csupomona.edu California State Polytechnic University | Pomona CA 91768

5 19

[Dovecot] [PATCH] GSSAPI authorization and virtual users
by Sam Morris 02 Jul '12

02 Jul '12

The attached patch makes it possible for Kerberos principals to be associated with a password database entry by adding a new "k5principals" passdb setting. A client that successfully authenticates using GSSAPI will be able to log in as any user who has been associated with the client's Kerberos principal. This means that users can now use their Kerberos identities to access virtual mail accounts. The patch definitely needs review by someone familiar with Dovecot. It works for me on a small test installation using the passwd-file backend. Things that should probably be improved: 1. The list of authorized principals is stored in struct auth_request. I would prefer to store it in struct gssapi_auth_request, but auth-request.c does not know about structs that are specific to the different authentication plugins. This could be fixed in a more general way by adding a new function to struct mech_module to allow authplugins to read fields during passdb lookups. 2. The gssapi authplugin now does a credential lookup in order to trigger parsing of the k5principals setting. In order for this to work, auth_request_set_username is now called before mech_gssapi_userok. AFAICT the only impact of this is that messages logged by this function (and the functions it calls) will now use the name of the virtual account. 3. The credentials lookup triggers an info log message saying that credentials for GSSAPI were requested, "but we have only (e.g.) MD5-CRYPT". The authplugin doesn't actually want the credential, but I think that the only way the authplugin can trigger a passdb lookup is by requesting it. 4. The final part of the code in mech_gssapi_unwrap was moved to the callback that's triggered when the credentials lookup is complete. The code still needs access to the GSSAPI data, so the buffer pointer & length are now stored in struct gssapi_auth_request, making the inbuf parameter to the mech_gssapi_{sec_context,wrap,unwrap} functions superfluous. The parameters should be removed. 5. The k5principals list won't be processed on Solaris. The code added to the end of mech_gssapi_krb5_userok would have to be moved to a separate function and then be called from the Solaris code. 6. GCC tells me about assignment to incompatible pointer types in the code that iterates through gssapi_k5principals. I must be missing something. The patch is licensed under the MIT license. Please let me know what you think. -- Sam Morris <sam(a)robots.org.uk>

2 4

[Dovecot] lmtp proxy timeout while waiting for reply to DATA reply
by Daniel Parthey 02 Jul '12

02 Jul '12

Hi, we are experiencing similar sporadic data timeout issues with dovecot 2.0.20 as in http://dovecot.org/pipermail/dovecot/2011-June/059807.html at least once a week. Some mails get temporarily deferred in the postfix queue since dovecot director lmtp refuses them and the mails are delivered at a later time. The problem applies to mails delivered to single users as well as distribution lists where the mails gets delivered to several mailboxes by postfix. The postfix log shows the following output: postfix.log.7.gz:Apr 21 18:48:46 10.129.3.233 postfix/lmtp[15868]: 88062C08E: to=<username(a)example.org>, orig_to=<username(a)example.org>, relay=127.0.0.1[127.0.0.1]:20024, delay=35, delays=5.4/0.01/0/30, dsn=4.4.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.4.0 Remote server not answering (timeout while waiting for reply to DATA reply) (in reply to end of DATA command)) The dovecot.log (mailbox and director log there via syslog) shows the following output: Apr 21 18:46:53 10.129.3.233 dovecot: lmtp(15869): Debug: none: root=, index=, control=, inbox=, alt= Apr 21 18:46:53 10.129.3.233 dovecot: lmtp(15869): Connect from 127.0.0.1 Apr 21 18:46:53 10.129.3.233 dovecot: lmtp(15869): Debug: auth input: user=username(a)example.org proxy port=19024 host=10.129.3.190 proxy_refresh=450 Apr 21 18:46:53 10.129.3.233 dovecot: lmtp(15869): Disconnect from 127.0.0.1: Client quit (in reset) Apr 21 18:47:29 10.129.3.233 dovecot: lmtp(15869): Debug: none: root=, index=, control=, inbox=, alt= Apr 21 18:47:29 10.129.3.233 dovecot: lmtp(15869): Connect from 127.0.0.1 Apr 21 18:47:29 10.129.3.233 dovecot: lmtp(15869): Debug: auth input: user=username(a)example.org proxy port=19024 host=10.129.3.190 proxy_refresh=450 Apr 21 18:47:29 10.129.3.233 dovecot: lmtp(15869): Disconnect from 127.0.0.1: Client quit (in reset) Apr 21 18:48:15 10.129.3.233 dovecot: lmtp(15869): Debug: none: root=, index=, control=, inbox=, alt= Apr 21 18:48:15 10.129.3.233 dovecot: lmtp(15869): Connect from 127.0.0.1 Apr 21 18:48:15 10.129.3.233 dovecot: lmtp(15869): Debug: auth input: user=username(a)example.org proxy port=19024 host=10.129.3.190 proxy_refresh=450 Apr 21 18:48:46 10.129.3.233 dovecot: lmtp(15869): Disconnect from 127.0.0.1: Client quit (in reset) One cannot identify the lmtp log origin from the log_format prefixes, but it seems that the "lmtp($PID)" log originated from the director, since proxy port 19024 is mentioned in the logs, which is our dovecot mailbox backend. Config for dovecot (mailbox) and director (proxy) is attached. mail_debug is yes for both dovecot and director. How can we find out more information? Shall I apply the following patches from http://dovecot.org/pipermail/dovecot/2011-June/059987.html or are they already included with version 2.0.20? Regards, Daniel

3 10

[Dovecot] permissions on auth-userdb
by spamvoll＠googlemail.com 28 Jun '12

28 Jun '12

Hi.. im still trying to upgrade to 2.0. Im getting: dovecot: lda: Error: userdb lookup: connect(/var/run/dovecot/auth-userdb) failed: Permission denied (euid=10000(vmail) egid=10000(vmail) missing +r perm: /var/run/dovecot/auth-userdb, euid is not dir owner) the error is correct caus its owned by root. My Questions is who should own it ? Im not sure how that works, what process/user calls the auth-userdb ? The auth-userdb returns the args generated in master.conf, right ? i think comment out the user and group setting in master.conf will fix it but im not sure if that is the securest way. the mails come from postfix via dovecot-lda Hans master.conf service auth { # auth_socket_path points to this userdb socket by default. It's typically # used by dovecot-lda, doveadm, possibly imap process, etc. Its default # permissions make it readable only by root, but you may need to relax these # permissions. Users that have access to this socket are able to get a list # of all usernames and get results of everyone's userdb lookups. unix_listener auth-userdb { mode = 0600 #user = vmail #group = vmail } auth-ldap.conf.ext passdb { driver = ldap args = /etc/dovecot/dovecot-ldap.conf.ext } userdb { driver = static args = uid=vmail gid=vmail home=/home/MAILBOXES/%u/ mail=/home/MAILBOXES/%u/mail }

5 8

[Dovecot] Very High Load on Dovecot 2 and Errors in mail.err.
by Urban Loesch 20 Jun '12

20 Jun '12

Hi, I have a DELL PE R610 (32GB RAM 2x Six Core CPU and about 1,4 TB RAID 10) running with 20.000 Mailaccounts behind 2 Dovecot IMAP/POP3 Proxies on a Debian Lenny. The Server was running about 1 year without any problems. 15Min Load was between 0,5 and max 8. No high IOWAIT. CPU Idletime about 98%. But since yesterday morning the Systemload on the Server has been increased over 500. I Think this is very high. The strange thing: there was no IOWAIT and the CPU Idle time was allways the same on about 98%. The total amount of IMAP Sessions is about 300 - 600. Current vmstat and iostat: # vmstat 1 procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu---- r b swpd free buff cache si so bi bo in cs us sy id wa 1 0 0 27040576 635460 3495600 0 0 14 15 2 31 0 0 99 0 0 0 0 27040320 635468 3496064 0 0 804 455 1383 1281 0 0 98 1 0 0 0 27047016 634964 3489312 0 0 216 156 1841 1292 1 0 98 1 0 0 0 27047140 635028 3489012 0 0 240 619 1629 1658 0 0 96 3 0 0 0 27047264 635120 3489172 0 0 92 0 1069 881 0 0 100 0 0 0 0 27047388 635120 3489256 0 0 0 46 1404 1265 0 0 100 0 0 0 0 27047512 635136 3489312 0 0 128 471 1539 1354 0 0 99 1 0 0 0 27047388 635156 3489384 0 0 12 360 1108 952 0 0 99 0 0 0 0 27047516 635160 3489408 0 0 104 12 893 677 0 0 99 0 ^C # iostat -k Linux 3.0.28-vs2.3.2.3-rol-em64t (mailstore4) 16.05.2012 _x86_64_ (24 CPU) avg-cpu: %user %nice %system %iowait %steal %idle 0,08 0,00 0,09 0,34 0,00 99,49 Device: tps kB_read/s kB_wrtn/s kB_read kB_wrtn sda 67,35 636,28 1080,48 31337690 53215361 dm-0 73,53 591,55 893,93 29134837 44027496 dm-1 15,06 42,40 181,79 2088493 8953661 drbd1 51,21 316,06 277,94 15566325 13689004 drbd0 9,22 23,50 80,38 1157641 3958796 Current Load: 08:55:44 up 14:04, 3 users, load average: 19,64, 14,47, 10,49 Load is increasing. The only strange thing I can see is this: # ps -ostat,pid,time,wchan='WCHAN-xxxxxxxxxxxxxxxxxxxx',cmd ax |grep D STAT PID TIME WCHAN-xxxxxxxxxxxxxxxxxxxx CMD D 18713 00:00:00 synchronize_srcu dovecot/imap D 18736 00:00:00 synchronize_srcu dovecot/imap D 18775 00:00:05 synchronize_srcu dovecot/imap D 20330 00:00:00 synchronize_srcu dovecot/imap D 20357 00:00:00 synchronize_srcu dovecot/imap D 20422 00:00:00 synchronize_srcu dovecot/imap D 20687 00:00:00 synchronize_srcu dovecot/imap S+ 20913 00:00:00 pipe_wait grep D There are many imap processes in D State. Amount is increasing. I think they are delayed and are wating for some event. I have no idea on which event they are waiting. And many of this in "mail.err" Log: May 16 08:52:11 dcot-rolmail-1.rolmail.net dovecot: master: Error: service(imap): Process 17468 is ignoring idle SIGINT May 16 08:52:24 dcot-rolmail-1.rolmail.net dovecot: master: Error: service(imap): Process 20307 is ignoring idle SIGINT May 16 08:52:25 dcot-rolmail-1.rolmail.net dovecot: master: Error: service(imap): Process 20318 is ignoring idle SIGINT May 16 08:52:26 dcot-rolmail-1.rolmail.net dovecot: master: Error: service(imap): Process 18964 is ignoring idle SIGINT May 16 08:52:28 dcot-rolmail-1.rolmail.net dovecot: master: Error: service(imap): Process 19244 is ignoring idle SIGINT May 16 08:54:22 dcot-rolmail-1.rolmail.net dovecot: master: Error: service(imap): Process 21177 is ignoring idle SIGINT May 16 08:54:41 dcot-rolmail-1.rolmail.net dovecot: master: Error: service(imap): Process 20647 is ignoring idle SIGINT May 16 08:55:10 dcot-rolmail-1.rolmail.net dovecot: master: Error: service(imap): Process 18836 is ignoring idle SIGINT May 16 08:55:17 dcot-rolmail-1.rolmail.net dovecot: master: Error: service(imap): Process 18857 is ignoring idle SIGINT May 16 08:55:19 dcot-rolmail-1.rolmail.net dovecot: master: Error: service(imap): Process 21176 is ignoring idle SIGINT May 16 08:55:24 dcot-rolmail-1.rolmail.net dovecot: master: Error: service(imap): Process 20688 is ignoring idle SIGINT May 16 08:55:25 dcot-rolmail-1.rolmail.net dovecot: master: Error: service(imap): Process 20973 is ignoring idle SIGINT May 16 08:56:44 dcot-rolmail-1.rolmail.net dovecot: master: Error: service(imap): Process 20326 is ignoring idle SIGINT Have you any Idea ho I can troubleshoot this problem? Some more technical information about the system: # uname -a Linux mailstore4 3.0.28-vs2.3.2.3-rol-em64t #1 SMP Thu May 3 09:31:08 CEST 2012 x86_64 GNU/Linux Dovecot Packages on Backend: installed: # dpkg -l |grep dovecot ii debian-dovecot-auto-keyring 2010.01.30 GnuPG archive keys of the Automatic Dovecot Debian repository ii dovecot-common 2:2.0.13-0~auto+54 secure mail server that supports mbox, maildir, dbox and mdbox mailboxes ii dovecot-imapd 2:2.0.13-0~auto+54 secure IMAP server that supports mbox, maildir, dbox and mdbox mailboxes ii dovecot-lmtpd 2:2.0.13-0~auto+54 secure LMTP server for Dovecot ii dovecot-managesieved 2:2.0.13-0~auto+54 secure ManageSieve server for Dovecot ii dovecot-mysql 2:2.0.13-0~auto+54 MySQL support for Dovecot ii dovecot-pop3d 2:2.0.13-0~auto+54 secure POP3 server that supports mbox, maildir, dbox and mdbox mailboxes ii dovecot-sieve 2:2.0.13-0~auto+54 sieve filters support for Dovecot Dovecot Packages on both Proxies installed: ii debian-dovecot-auto-keyring 2010.01.30 GnuPG archive keys of the Automatic Dovecot ii dovecot-common 2:2.0.17-0~auto+4 Transitional package for dovecot ii dovecot-core 2:2.0.17-0~auto+4 secure mail server that supports mbox, maild ii dovecot-gssapi 2:2.0.17-0~auto+4 GSSAPI authentication support for Dovecot ii dovecot-imapd 2:2.0.17-0~auto+4 secure IMAP server that supports mbox, maild ii dovecot-managesieved 2:2.0.17-0~auto+4 secure ManageSieve server for Dovecot ii dovecot-mysql 2:2.0.17-0~auto+4 MySQL support for Dovecot ii dovecot-pgsql 2:2.0.17-0~auto+4 PostgreSQL support for Dovecot ii dovecot-pop3d 2:2.0.17-0~auto+4 secure POP3 server that supports mbox, maild ii dovecot-sieve 2:2.0.17-0~auto+4 sieve filters support for Dovecot ii dovecot-sqlite 2:2.0.17-0~auto+4 SQLite support for Dovecot # doveconf -n # 2.0.13 (02d97fb66047): /etc/dovecot/dovecot.conf # OS: Linux 3.0.28-vs2.3.2.3-rol-em64t x86_64 Debian 6.0.2 ext4 auth_cache_negative_ttl = 0 auth_cache_size = 40 M auth_cache_ttl = 12 hours auth_mechanisms = plain login auth_username_format = %Lu auth_verbose = yes deliver_log_format = msgid=%m: %$ %p %w disable_plaintext_auth = no login_trusted_networks = 195.254.252.207 195.254.252.208 2a02:2e8:0:2:0:143:0:1 2a02:2e8:0:2:0:143:0:2 mail_gid = mailstore mail_location = mdbox:/home/vmail/%d/%n:INDEX=/home/dovecotindex/%d/%n mail_plugins = " quota zlib" mail_uid = mailstore 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 ihave imapflags notify mdbox_rotate_size = 5 M passdb { args = /etc/dovecot/dovecot-sql-account.conf driver = sql } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size from mail_log_group_events = no quota = dict:Storage used::file:%h/dovecot-quota sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags sieve_max_redirects = 10 zlib_save = gz zlib_save_level = 5 } protocols = imap pop3 lmtp sieve service auth-worker { process_min_avail = 12 service_count = 0 vsz_limit = 512 M } service imap-login { inet_listener imap { port = 143 } process_min_avail = 12 service_count = 0 vsz_limit = 256 M } service imap { process_min_avail = 12 service_count = 0 vsz_limit = 512 M } service lmtp { inet_listener lmtp { address = * port = 24 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } vsz_limit = 512 M } service pop3-login { inet_listener pop3 { port = 110 } process_min_avail = 12 service_count = 0 vsz_limit = 256 M } service pop3 { service_count = 0 vsz_limit = 256 M } ssl = no ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-sql-account.conf driver = sql } protocol lmtp { mail_plugins = " quota zlib sieve zlib" } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_max_userip_connections = 40 mail_plugins = " quota zlib imap_quota imap_zlib" } protocol pop3 { mail_plugins = " quota zlib" pop3_logout_format = bytes_sent=%o top=%t/%p, retr=%r/%b, del=%d/%m, size=%s uidl_hash=%u } Thanks and regards Urban Loesch

4 10

[Dovecot] gnutls support
by Daniel L. Miller 12 Jun '12

12 Jun '12

Other than license issues, is there an advantage to using gnutls vs openssl? Or is openssl superior - at least in the current implementations? -- Daniel

2 3

[Dovecot] Dovecot auth process delays exiting if LDAPS passdb used
by SATOH Fumiyasu 11 Jun '12

11 Jun '12

Hi, I'm using Dovecot 2.1.6 and LDAP server as a backend for Postfix SMTP-Auth (SASL) on Debian GNU/Linux (wheezy), Solaris 10 and AIX 6.1/7.1. If Dovecot passdb is configured with LDAP (no TLS/SSL), it is no problem. But if Dovecot passdb is configured with LDAPS (or LDAP+TLS), Dovecot auth process has a problem that Dovecot auth delays exiting about between 20 and 60 seconds when Dovecot dovecot (master) process is already terminated by an administrator. Is this known problem? On AIX, this problem prevents restart Dovecot service by the following error: May 24 00:42:03 build-aix6 mail:warn|warning dovecot: master: Warning: Killed with signal 15 (by pid=11337890 uid=0 code=kill) May 24 00:42:10 build-aix6 mail:err|error dovecot: master: Error: service(auth): Socket already exists: /opt/osstech/var/run/dovecot/auth-login May 24 00:42:11 build-aix6 mail:crit dovecot: master: Fatal: Failed to start listeners My Dovecot 2.1.6 platforms are: * Debian GNU/Linux wheezy + OpenLDAP 2.4.28 (linked with GNU TLS 2.12.18) * Solaris 10 + OpenLDAP 2.4.26 (linked with OpenSSL 0.9.7) * AIX 6.1 + OpenLDAP 2.4.31 (linked with OpenSSL 1.0.0) * AIX 7.1 + OpenLDAP 2.4.28 (linked with OpenSSL 1.0.0) Because I see the problem on the all of above, there is a bug in Dovecot 2.1.6, I think. Thanks. -- -- Name: SATOH Fumiyasu (fumiyas @ osstech co jp) -- Business Home: http://www.OSSTech.co.jp/ -- Personal Home: http://www.SFO.jp/blog/

2 9

[Dovecot] fts_lucene crashing
by Joe Beaubien 11 Jun '12

11 Jun '12

I found this in mail.err. Anyone ever experience this? May 22 14:51:51 mba dovecot: imap(formulaire): Panic: file lucene-wrapper.cc: line 196: unreached May 22 14:51:51 mba dovecot: imap(formulaire): Error: Raw backtrace: /opt/dovecot-2.1.6-lucene/lib/dovecot/libdovecot.so.0(+0x4200a) [0x7f7e0edfd00a] -> /opt/dovecot-2.1.6-lucene/lib/dovecot/libdovecot.so.0(+0x4204e) [0x7f7e0edfd04e] -> /opt/dovecot-2.1.6-lucene/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f7e0edd43c0] -> /opt/dovecot/lib/dovecot/lib21_fts_lucene_plugin.so(+0x850e) [0x7f7e0d57a50e] -> /opt/dovecot/lib/dovecot/lib21_fts_lucene_plugin.so(+0xa7be) [0x7f7e0d57c7be] -> /opt/dovecot/lib/dovecot/lib21_fts_lucene_plugin.so(+0xa952) [0x7f7e0d57c952] -> /opt/dovecot/lib/dovecot/lib21_fts_lucene_plugin.so(lucene_index_lookup+0x7b) [0x7f7e0d57ce0b] -> /opt/dovecot/lib/dovecot/lib21_fts_lucene_plugin.so(+0x73a7) [0x7f7e0d5793a7] -> /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(fts_backend_lookup+0x63) [0x7f7e0d98ece3] -> /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(+0xa32d) [0x7f7e0d99232d] -> /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(fts_search_lookup+0xa6) [0x7f7e0d992a26] -> /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(+0xba25) [0x7f7e0d993a25] -> /opt/dovecot-2.1.6-lucene/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x27) [0x7f7e0f0c1957] -> dovecot/imap() [0x4158a7] -> dovecot/imap() [0x415c62] -> /opt/dovecot-2.1.6-lucene/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0xc4) [0x7f7e0ee09cd4] -> /opt/dovecot-2.1.6-lucene/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x5b) [0x7f7e0ee0ac2b] -> /opt/dovecot-2.1.6-lucene/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7f7e0ee09998] -> /opt/dovecot-2.1.6-lucene/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f7e0edf6233] -> dovecot/imap(main+0x285) [0x4086e5] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f7e0ea1f76d] -> dovecot/imap() [0x40885d] May 22 14:51:51 mba dovecot: imap(formulaire): Fatal: master: service(imap): child 32761 killed with signal 6 (core dumped) I get these errors very very often. When I look at lucene-wrapper.cc source code I see the following 196: if (uni_utf8_to_ucs4(str, &dest_arr) < 0) i_unreached(); Any ideas? -Joe

2 6