- dovecot - dovecot.org

[Dovecot] v2.0.21 released
by Timo Sirainen 12 Jun '12

12 Jun '12

http://dovecot.org/releases/2.0/dovecot-2.0.21.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.21.tar.gz.sig + dict: file backend supports now also fcntl/flock locking optionally - imap-login: Memory leak fixed - imap: Non-UTF8 input on SEARCH command parameters could have crashed - auth: Fixed crash with DIGEST-MD5 when attempting to do master user login without master passdbs. - sdbox: Don't use more fds than necessary when copying mails. - mdbox kept the user's storage locked a bit longer than it needed to

4 3

[Dovecot] 2.1.7 shared folder index issued
by Alex Crow 12 Jun '12

12 Jun '12

Hi, Sorry to bother the list again so soon after fixing my own problem, but I now have this issue when clients try to view shared folders in Thunderbird (v12). They can see the shared folder, but the first time they click on in nothing happens. The second time they get an authentication failure. The third or fourth time it finally loads the shared mailbox, and I see this a few times in the logs: Jun 11 19:57:43 alsace dovecot: imap(sharedviewer(a)integrafin.co.uk): Error: mdbox map /home/indexes/integrafin.co.uk/t/sharedviewer/shared/sharedviewee(a)integrafin.co.uk/storage/dovecot.map.index corrupted: U nexpectedly lost shared/viewee(a)integrafin.co.uk/INBOX uid=73129 map_uid=74192 Jun 11 19:57:43 alsace dovecot: imap(sharedviewer(a)integrafin.co.uk): Disconnected: Internal error occurred. Refer to server log for more information. [2012-06-11 19:57:43] in=308 out=820 Jun 11 19:57:43 alsace dovecot: auth: Debug: auth client connected (pid=1957) Ideally I'd like shared mailboxes to work in the first click - any ideas? Cheers Alex

2 4

[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] auth_krb5_keytab ignored ?
by Leon Meßner 12 Jun '12

12 Jun '12

Hi list, i noticed that when doing imap gssapi authentication with kerberos, dovecot (here 2.1.7) always searches /etc/krb5.keytab although i have auth_krb5_keytab = /etc/mail3.krb5.keytab in my etc/dovecot/dovecot.conf and doveconf -n also show this setting. If i combine the keytabs in krb5.keytab it works. Is there another location where i should put my configuration regarding gssapi/kerberos ? Thanks, Leon logs: 18:48_root@mail3:/root# cat /var/log/dovecot.log | tail -n 8 Jun 08 18:48:16 auth: Debug: client in: AUTH 1 GSSAPI service=imap secured session=gexTxPjBZACClTqR lip=130.149.58.164 rip=130.149.58.145 lport=993 rport=31076 Jun 08 18:48:16 auth: Debug: gssapi(?,130.149.58.145,<gexTxPjBZACClTqR>): Obtaining credentials for imap(a)mail3.physik-pool.tu-berlin.de Jun 08 18:48:16 auth: Debug: client out: CONT 1 Jun 08 18:48:16 auth: Debug: client in: CONT<hidden> Jun 08 18:48:16 auth: Info: gssapi(?,130.149.58.145,<gexTxPjBZACClTqR>): While processing incoming data: Miscellaneous failure (see text) Jun 08 18:48:16 auth: Info: gssapi(?,130.149.58.145,<gexTxPjBZACClTqR>): While processing incoming data: Failed to find imap/mail3.physik-pool.tu-berlin.de(a)PCPOOL.PHYSIK.TU-BERLIN.DE(kvno 1) in keytab FILE:/etc/krb5.keytab (des3-cbc-sha1) Jun 08 18:48:18 auth: Debug: client out: FAIL 1 Jun 08 18:48:23 imap-login: Info: Aborted login (auth failed, 1 attempts in 7 secs): user=<>, method=GSSAPI, rip=130.149.58.145, lip=130.149.58.164, TLS, session=<gexTxPjBZACClTqR> # 2.1.7: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 8.2-RELEASE-p3 amd64 auth_debug = yes auth_gssapi_hostname = mail3.physik-pool.tu-berlin.de auth_krb5_keytab = /etc/mail3.krb5.keytab auth_mechanisms = gssapi plain login auth_verbose = yes auth_worker_max_count = 120 first_valid_gid = 300 first_valid_uid = 200 lda_mailbox_autocreate = yes listen = mail3.physik.tu-berlin.de log_path = /var/log/dovecot.log mail_fsync = always mail_location = maildir:~/maildir mail_nfs_index = yes mail_nfs_storage = yes mail_privileged_group = mail 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 mmap_disable = yes namespace { inbox = yes location = prefix = separator = / type = private } namespace { location = mbox:~/mail prefix = mail/ separator = / type = private } passdb { args = session=yes failure_show_msg=yes max_requests=100 dovecot driver = pam } plugin { quota = fs sieve = ~/.dovecot.sieve sieve_dir = ~/.sieve } protocols = imap pop3 service auth { unix_listener auth-client { mode = 0660 } unix_listener auth-master { mode = 0600 } user = root } service imap-login { inet_listener imap { port = 0 } process_limit = 256 process_min_avail = 6 } service managesieve-login { process_limit = 256 process_min_avail = 6 } service pop3-login { inet_listener pop3 { port = 0 } process_limit = 256 process_min_avail = 6 } ssl_cert = </etc/private/mail3.physik.tu-berlin.de.pem ssl_key = </etc/private/physik.tu-berlin.de_privatekey.pem userdb { args = blocking=yes driver = passwd } verbose_proctitle = yes protocol lda { info_log_path = /var/log/dovecot-lda.log log_path = /var/log/dovecot-lda.log mail_plugins = " sieve quota" }

2 5

[Dovecot] Sieve: Mailbox doesn't exist
by Stefan Fricke 12 Jun '12

12 Jun '12

I have just set up a mail server on Ubuntu, using Postfix and Dovecot 2.0.19. It works well but I can't get Sieve working. I always get the error that the target mailbox doesn't exist. In fact it doesn't but isn'r Dovecot supposed to create it? Here is my doveconf -n: # 2.0.19: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-24-generic x86_64 Ubuntu 12.04 LTS mail_debug = yes 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 ihave passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 sieve service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 } 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 }

3 2

[Dovecot] commercial support -- feedback
by Костырев Александр Алексеевич 12 Jun '12

12 Jun '12

good day! Did anybody in here decide to go for commercial support from Dovecot Solutions Oy ? I'd like to know if you are satisfied with what they provide? if time of support reaction is really as what is stated at their site and stuff like that.

1 0

[Dovecot] Authentication issue
by Emiliano Rago 12 Jun '12

12 Jun '12

Hi, I need to set up a weird dovecot configuration: 1) outside a ssl tunnel I'd like to authenticate only with cram-md5 scheme 2) inside a ssl tunnel I'd like to authenticate only with plain auth The first is easily satisfied with auth_mechanisms = plain cram-md5 disable_plaintext_auth = yes but I don't know how to satisfy the second condition, if it's possible. Thanks for help, Emiliano Rago

2 2

[Dovecot] Getting duplicates despite trying hard to match lock styles
by Richard Walker 12 Jun '12

12 Jun '12

I'm attempting to replace (a) a very old setup that has POP (qpopper) access to inboxes and a separate UW IMAP server that provides folders, with (b) a shiny new mail setup with dovecot providing both inboxes and IMAP support. For the new mail server I created a virtual machine running a minimal Fedora 16 installation and installed sendmail, MIMEDefang, SpamAssassin, ClamAV, procmail, and dovecot. I have kept installing updates as they become available. For now I'm running the old and new mail setups in parallel; I have configured the original sendmail server to forward copies of incoming messages to the new sendmail running on the virtual machine. I then compare the results (e.g., how spam filtering is working). I've kept as much as possible of the original _style_ of setup as possible, which in particular means using sendmail, and message delivery through procmail to mbox files in /var/spool/mail. The key difference is the use of dovecot to provide IMAP access to the inbox and IMAP folders. Because of the legacy setup, my desktop access to email is via Thunderbird 2.0.0.22 on a very old Mac PowerBook G4 to work with both old and new setups and I have two windows open to make comparison possible. (Yes, both mail servers are on separate computers, not on this notebook.) Mostly this is working fine (after a fair bit of tweaking, including adding custom SELinux rules to get rid of all AVCs). I put the notebook to sleep overnight, and in the morning I open it up and see what happens. After a few minutes, the window with the old setup does its POP fetch; the window with the new setup almost straightaway shows the new messages in its version of the inbox. Not quite: again, for legacy reasons I have some Thunderbird filters, and I have duplicated those (still within Thunderbird) for the new setup. The filters are: 1. Move messages tagged as spam by SpamAssassin to the Junk folder. 2. Move messages from GeoNetwork-related senders to a "GeoNetwork" folder. 3. Move all remaining messages to the "In" folder. Most mornings this works just fine. But not always. Sometimes I get duplicates in the "In" and "GeoNetwork" folders of the new dovecot-based setup. I used to get _garbled_ duplicates (with extra random bits of other messages at the end of the duplicates) in the new setup, which I presumed must be due to a locking configuration mismatch. Having fixed that (see below) I no longer get garbled duplicates, but I do still sometimes (including today) get identical duplicates. This seems to happen when one of the incoming messages has a very large attachment - but you may wish to treat that as hearsay. I attach below: 0. The line from /etc/mtab on the new server that covers the filesystem (i.e., including /var/spool and /home). 1. Output of "doveconf -n" and a note about how I modified locking from the Fedora default. 2. Output of "procmail -v". 3. Sendmail procmail mailer config (for good measure; I don't think you need this). 4. An excerpt from /var/log/maillog on the new server showing the beginning of dovecot processing this morning when I opened my notebook. 5. A link to the dovecot raw log files of my "INBOX" and "In" folder processing from this morning. You'll see from the dovecot log files that Thunderbird sends expunge commands, but the expunged messages hang around -- indeed, the same messages get expunged several times! And eventually they get fetched again -- hence the duplicates I see in Thunderbird. Given that INBOX.out contains: 08:56:53.765423 * 537 EXISTS 08:56:53.765423 * 533 RECENT and then, after many expunges: 08:56:58.441341 * 16 EXPUNGE 08:56:58.441341 * 11 EXPUNGE 08:56:58.441341 * 3 EXPUNGE 08:56:58.441341 * 539 EXISTS 08:56:58.441341 * 536 RECENT 08:56:58.441341 9 OK Expunge completed. it looks like I still have a locking problem. I have tried very hard to understand the locking options in dovecot.conf and to match dovecot with procmail -- apparently, there is more to do. 0. The line from /etc/mtab for the filesystem: ---------- /dev/mapper/vg_f16i386serverbasic-lv_root / ext4 rw,seclabel,relatime,user_xattr,acl,barrier=1,data=ordered 0 0 ---------- 1. doveconf -n says: ---------- # 2.0.20: /etc/dovecot/dovecot.conf # OS: Linux 3.3.6-3.fc16.i686.PAE i686 Fedora release 16 (Verne) mail_debug = yes mail_privileged_group = mail namespace { hidden = yes inbox = yes list = no location = mbox:~/mail:INBOX=/var/spool/mail/%u prefix = "#mbox/" separator = / type = private } namespace { inbox = no location = maildir:~/Maildir prefix = separator = / type = private } passdb { driver = pam } service imap-login { inet_listener imap { address = localhost } } service imap { executable = imap postlogin } service pop3-login { inet_listener pop3 { address = localhost } } service postlogin { executable = script-login -d rawlog -t } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } ---------- Note that the default Fedora installation specifies: mbox_write_locks = fcntl and I commented that out. This seems to restore the default setting of: mbox_write_locks = dotlock fcntl to match procmail. 2. procmail -v (run as me) says: ---------- procmail v3.22 2001/09/10 Copyright (c) 1990-2001, Stephen R. van den Berg <srb(a)cuci.nl> Copyright (c) 1997-2001, Philip A. Guenther <guenther(a)sendmail.com> Submit questions/answers to the procmail-related mailinglist by sending to: <procmail-users(a)procmail.org> And of course, subscription and information requests for this list to: <procmail-users-request(a)procmail.org> Locking strategies: dotlocking, fcntl() Default rcfile: $HOME/.procmailrc It may be writable by your primary group Your system mailbox: /var/spool/mail/rw ---------- (There is no $HOME/.procmailrc or other system-wide procmailrc.) 3. The mailer as defined in sendmail.cf says: ---------- Mlocal, P=/usr/bin/procmail, F=lsDFMAw5:/|@qSPfhn9, S=EnvFromL/HdrFromL, R=EnvToL/HdrToL, T=DNS/RFC822/X-Unix, A=procmail -t -Y -a $h -d $u ---------- 4. The relevant lines from /var/log/maillog: ---------- Jun 12 08:56:53 localhost dovecot: imap-login: Login: user=<rw>, method=PLAIN, rip=192.168.2.200, lip=192.168.2.188, mpid=21618, TLS Jun 12 08:56:53 localhost dovecot: imap(rw): Debug: Effective uid=1000, gid=100, home=/home/rw Jun 12 08:56:53 localhost dovecot: imap(rw): Debug: Namespace : type=private, prefix=#mbox/, sep=/, inbox=yes, hidden=yes, list=no, subscriptions=yes location=mbox:~/mail:INBOX=/var/spool/mail/rw Jun 12 08:56:53 localhost dovecot: imap(rw): Debug: fs: root=/home/rw/mail, index=, control=, inbox=/var/spool/mail/rw, alt= Jun 12 08:56:53 localhost dovecot: imap(rw): Debug: Namespace : type=private, prefix=, sep=/, inbox=no, hidden=no, list=yes, subscriptions=yes location=maildir:~/Maildir Jun 12 08:56:53 localhost dovecot: imap(rw): Debug: maildir++: root=/home/rw/Maildir, index=, control=, inbox=, alt= Jun 12 08:56:58 localhost dovecot: imap-login: Login: user=<rw>, method=PLAIN, rip=192.168.2.200, lip=192.168.2.188, mpid=21625, TLS Jun 12 08:56:58 localhost dovecot: imap(rw): Debug: Effective uid=1000, gid=100, home=/home/rw Jun 12 08:56:58 localhost dovecot: imap(rw): Debug: Namespace : type=private, prefix=#mbox/, sep=/, inbox=yes, hidden=yes, list=no, subscriptions=yes location=mbox:~/mail:INBOX=/var/spool/mail/rw Jun 12 08:56:58 localhost dovecot: imap(rw): Debug: fs: root=/home/rw/mail, index=, control=, inbox=/var/spool/mail/rw, alt= Jun 12 08:56:58 localhost dovecot: imap(rw): Debug: Namespace : type=private, prefix=, sep=/, inbox=no, hidden=no, list=yes, subscriptions=yes location=maildir:~/Maildir Jun 12 08:56:58 localhost dovecot: imap(rw): Debug: maildir++: root=/home/rw/Maildir, index=, control=, inbox=, alt= Jun 12 08:57:03 localhost dovecot: imap-login: Login: user=<rw>, method=PLAIN, rip=192.168.2.200, lip=192.168.2.188, mpid=21632, TLS Jun 12 08:57:03 localhost dovecot: imap(rw): Debug: Effective uid=1000, gid=100, home=/home/rw Jun 12 08:57:03 localhost dovecot: imap(rw): Debug: Namespace : type=private, prefix=#mbox/, sep=/, inbox=yes, hidden=yes, list=no, subscriptions=yes location=mbox:~/mail:INBOX=/var/spool/mail/rw Jun 12 08:57:03 localhost dovecot: imap(rw): Debug: fs: root=/home/rw/mail, index=, control=, inbox=/var/spool/mail/rw, alt= Jun 12 08:57:03 localhost dovecot: imap(rw): Debug: Namespace : type=private, prefix=, sep=/, inbox=no, hidden=no, list=yes, subscriptions=yes location=maildir:~/Maildir Jun 12 08:57:03 localhost dovecot: imap(rw): Debug: maildir++: root=/home/rw/Maildir, index=, control=, inbox=, alt= ---------- 5. dovecot raw logs for "INBOX" and "In". Because I have trouble comparing times in epoch format, I've run the logs through a little filter that replaces the timestamps at the beginning of each line with a timestamp in HH:MM:SS.nanosecond format in local time. I've carefully deleted lots of (what I hope are) lines you don't need from the logs. E.g., I deleted the middle section of a block of FETCH statements, leaving the first few and the last few. Please let me know if I deleted too much -- I was trying to be helpful. And of course I replaced e-mail address/subject lines/etc with XXXXXXXXXX. Although the Thunderbird filters are "supposed" to be run in the order I listed above, it seems that Thunderbird fetches all headers, works out what messages should be filtered to which folders, and then sends corresponding IMAP commands that copy the messages to the other folders in a _different_ order of the filters. (I.e., the INBOX log shows copy/store/expunge operations in the order "In", "Junk", then "GeoNetwork", rather than "Junk", "GeoNetwork", "In".) I have renamed the in/out log files as INBOX.in, INBOX.out, In.in, In.out and uploaded them to: https://sites.google.com/site/rwdownloadssite/dovecot-logs Thanks in advance to anyone who is willing to take a look and advise what I need to do.

1 1

[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