- dovecot - dovecot.org

Re: Dovecot Oy merger with Open-Xchange AG
by Patrick Coffin 25 Mar '15

25 Mar '15

To Timo and the Dovecot guys - congratulations! I'm sure this merger with OpenXchange is going to provide you with a lot of resources and opportunities. As a longtime user of dovecot, I do have a few concerns. I wonder if you can answer some questions for me. You say that OpenXchange really likes open source and shares your plans for the future. Is this a commitment that future versions core dovecot product will remain free and truly open source? According to Wikipedia (http://en.wikipedia.org/wiki/Open-Xchange#Licensing <http://en.wikipedia.org/wiki/Open-Xchange#Licensing>) , OpenXchange's backend is GPL'd, but the front-end is not - it's released under "Creative Common's Share Alike, Non Commercial, Attribution". The article points out: "The restriction to Non Commercial in the Creative Commons license for the Frontend restricts re-distribution to third parties, i.e. hosted deployments for third parties. However, since the front-end license prohibits commercial re-distribution, the software is neither free software nor open source software since the definitions of both require such re-distribution to be permitted" Do you expect that dovecot is moving in that direction? Here's why I'm asking: As a hosted email provider, I've long used dovecot, and been quite happy with it. But I have some concerns, as is common when any popular open source project gets acquired by a commercial entitiy. The current dovecot license is a mixture of the MIT and LGPL licenses. Will this remain? Or is dovecot going to go the way of OpenXchange licensing? What about other pieces of the dovecot ecosystem, such as the Object Storage plugin - will that remain closed source and proprietary? Or will you follow the lead of companies like RedHat and be truly open source? Is there a possibility that future versions of dovecot that contain what we might consider core features will be available only in the commercial version of the product? If I base a part of my business on a piece of software I've been running for the last 10 years, am I going to find myself in trouble in a year or two, when some new version of dovecot comes out with changes that I need, and I have to move to a commercial product, which I may or may not be able to afford? I'd love to hear that you're going to be following a model like RedHat did when they acquired GlusterFS and created the RedHat Storage Server. Gluster development is still going strong, and still completely open source. But they make money from people like me who know that by buying a contract, we can get the kind of support we need for such a critical part of our infrastructure. Again, congratulations and, as always, thanks for all the hard work creating dovecot in the first place. Patrick

7 13

Upgrading a dovecot director configuration?
by Will Rouesnel 25 Mar '15

25 Mar '15

Is Dovecot Director compatible across Dovecot versions? i.e. 2.0.x to 2.1.x or 2.2.x? I have a 6 host cluster in a director configuration which is getting somewhat aged, but it would be very beneficial if the director hosts could be upgraded seamlessly. Is such a thing possible, or will their be compatibility issues? Would a workaround be possible (i.e. migrate to a user system which enforces proxy destinations by another means, then do an upgrade?)

1 0

Fixing broken UTF-8 handling with MySQL driver
by Felix Zandanel 23 Mar '15

23 Mar '15

Hi, I noticed that dovecot's MySQL driver doesn't play well with UTF-8 encoded strings. I presume this issue has been around for a while. However, it still fails with the current release candidate 2.2.16-rc1. I have been using the sieve extdata plugin with a MySQL-backed dict to retrieve a folder name that is then passed to fileinto: fileinto :create "${extdata.folder_name_drafts}"; Whenever this dict returned a string with non-7byte characters, a line such as the following popped up in sieve.log. (This example query should return "Entwürfe".) error: folder name specified for fileinto command is not utf-8: Entw?rfe. Although my MySQL installation is set up to use UTF-8 as the default charset on every level (config, database, table and field), and the character_set_* runtime variables all yield the value "utf8", it still seems that the mysql client library must be instructed to actually use UTF-8 explicitly. Adding the following statement to driver_mysql_connect() fixes the issue for me: mysql_options(db->mysql, MYSQL_SET_CHARSET_NAME, "utf8"); I checked this against mysql 5.5.41. Regards, Felix

2 2

[PATCH] increase fd_limit to max_client_limit automatically
by Lauri Tirkkonen 23 Mar '15

23 Mar '15

Hi, with a low soft limit on file descriptors, dovecot 2.2.15 warns on startup: Warning: fd limit (ulimit -n) is lower than required under max. load (256 < 1000), because of default_client_limit It could try increasing the limit first, and only report the warning if that fails. I'm attaching a patch that does just this. Without the patch, the soft fd limit is kept at whatever it was on dovecot startup: % pfexec plimit $(pgrep dovecot) 18737: /opt/niksula/sbin/dovecot resource current maximum time(seconds) unlimited unlimited file(blocks) unlimited unlimited data(kbytes) unlimited unlimited stack(kbytes) 10240 unlimited coredump(blocks) unlimited unlimited nofiles(descriptors) 256 65536 vmemory(kbytes) unlimited unlimited and with patch applied, it's increased to max_client_limit: % pfexec plimit $(pgrep dovecot) 18775: /opt/niksula/sbin/dovecot resource current maximum time(seconds) unlimited unlimited file(blocks) unlimited unlimited data(kbytes) unlimited unlimited stack(kbytes) 10240 unlimited coredump(blocks) unlimited unlimited nofiles(descriptors) 1000 65536 vmemory(kbytes) unlimited unlimited It should probably be increased to higher than that to account for fds other than client sockets, but I don't have insights into that. -- Lauri Tirkkonen Niksula systems specialist

2 2

Re: fast doveadm search results
by Joseph Tam 23 Mar '15

23 Mar '15

Steffen Kaiser writes: > e.g. put message-id into mail_always_cache_fields > > - From http://dovecot.org/pipermail/dovecot-cvs/2013-May/023261.html > > lib-storage: Allow mail_*cache_fields settings to specify any hdr.* fields ... but I belatedly wrote ... > Maybe you can even add these items into the cache upon delivery, > but someone more knowlegable than I would have to help you with that. The drawback of getting thing in digest form -- you look like a boob when answering late. I defer to Steffen's superior knowledge. Joseph Tam <jtam.home(a)gmail.com>

3 3

2.2.16 link failure on FreeBSD 10.1, with patch
by Jan Mikkelsen 22 Mar '15

22 Mar '15

Hi, Compiling on FreeBSD 10.1 gives linker errors when linking test-message-snippet. The underlying problem is that libiconv appears on the actual linker line after libcharset.a, which leads to unresolved libiconv symbols. This build process worked fine with 2.2.15. The patch below to src/lib-charset/Makefile.in resolves the problem for me and seems broadly correct. libcharset.a does depend on libiconv so it should probably be declared that way. There is probably a more correct way to make the patch to Makefile.am, but I don't really use automake. Hopefully helpful to someone. Jan Mikkelsen. Patch: --- dovecot-2.2.16/src/lib-charset/Makefile.in 2015-03-13 02:41:16.000000000 +1100 +++ dovecot-2.2.16.new/src/lib-charset/Makefile.in 2015-03-21 13:58:21.951293274 +1100 @@ -92,7 +92,7 @@ CONFIG_CLEAN_FILES = CONFIG_CLEAN_VPATH_FILES = LTLIBRARIES = $(noinst_LTLIBRARIES) -libcharset_la_LIBADD = +libcharset_la_LIBADD = $(LTLIBICONV) am_libcharset_la_OBJECTS = charset-iconv.lo charset-utf8.lo libcharset_la_OBJECTS = $(am_libcharset_la_OBJECTS) AM_V_lt = $(am__v_lt_@AM_V@) Error messages: libtool: link: cc -std=gnu99 -I/usr/local/include -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wno-duplicate-decl-specifier -Wstrict-aliasing=2 -Wl,--as-needed -o test-message-snippet test-message-snippet.o .libs/message-snippet.o .libs/mail-html2text.o .libs/message-decoder.o .libs/quoted-printable.o .libs/rfc822-parser.o .libs/rfc2231-parser.o /usr/local/lib/libiconv.so -Wl,-rpath -Wl,/usr/local/lib .libs/message-parser.o .libs/message-header-parser.o .libs/message-header-decode.o .libs/message-size.o -L/usr/local/lib ../lib-charset/.libs/libcharset.a ../lib-test/.libs/libtest.a ../lib/.libs/liblib.a ../lib-charset/.libs/libcharset.a(charset-iconv.o): In function `charset_to_utf8_begin': charset-iconv.c:(.text+0x49): undefined reference to `libiconv_open' ../lib-charset/.libs/libcharset.a(charset-iconv.o): In function `charset_to_utf8_end': charset-iconv.c:(.text+0x151): undefined reference to `libiconv_close' ../lib-charset/.libs/libcharset.a(charset-iconv.o): In function `charset_to_utf8_reset': charset-iconv.c:(.text+0x211): undefined reference to `libiconv' ../lib-charset/.libs/libcharset.a(charset-iconv.o): In function `charset_to_utf8_try': charset-iconv.c:(.text+0x425): undefined reference to `libiconv' cc: error: linker command failed with exit code 1 (use -v to see invocation) ../lib-charset/.libs/libcharset.a(charset-iconv.o): In function `charset_to_utf8_begin': charset-iconv.c:(.text+0x49): undefined reference to `libiconv_open' ../lib-charset/.libs/libcharset.a(charset-iconv.o): In function `charset_to_utf8_end': charset-iconv.c:(.text+0x151): undefined reference to `libiconv_close' ../lib-charset/.libs/libcharset.a(charset-iconv.o): In function `charset_to_utf8_reset': charset-iconv.c:(.text+0x211): undefined reference to `libiconv' ../lib-charset/.libs/libcharset.a(charset-iconv.o): In function `charset_to_utf8_try': charset-iconv.c:(.text+0x425): undefined reference to `libiconv'

1 0

Transitioning from version 1 to version 2
by Steve Matzura 21 Mar '15

21 Mar '15

I'm wrestling with transitioning from a 1.0.15 system to a 2.2.25 system. The old dovecot.conf cannot be dropped into position on the new system because so many config options and symbols have changed. It seems every time I change something to match the new formats, I break something else! Anyone out there have maybe half an hour to spare to look at my old and new files to help me whip them into shape?

1 0

FreeBSD ZFS maildir to mdbox
by Roland van Laar 21 Mar '15

21 Mar '15

Hello, I'm converting my mailbox from Maildir to mdbox.. The Maildir is from an 1.2 server. The new server is a virtual FreeBSD ZFS server. The conversion is not working, I'm getting either segfaults or the sync just quits with errors. I also did set with mmap_disable=yes. This didn't resolve the problem. How can I fix this? The same conversion on a virtual ubuntu 14.04 box works with mentions of "filename has the wrong S value" and Corrupted index errors. The FreeBSD errors and dovecot -n are included below: dsync(vagrant): Error: read(./Maildir/cur/1296038598.29562.mail.micite.net,S=20542:2,Sa) failed: Cached message size smaller than expected (20542 < 20640, box=INBOX, UID=475) dsync(vagrant): Error: Maildir filename has wrong S value, renamed the file from ./Maildir/cur/1296038598.29562.mail.micite.net,S=20542:2,Sa to ./Maildir/cur/1296038598.29562.mail.micite.net,S=20640:2,Sa dsync(vagrant): Error: Corrupted index cache file ./Maildir/dovecot.index.cache: Broken physical size for mail UID 475 dsync(vagrant): Error: write(/home/vagrant/mdbox/storage/m.12) failed: Invalid argument dsync(vagrant): Error: copy: i_stream_read(./Maildir/cur/1296038598.29562.mail.micite.net,S=20542:2,Sa) failed: Cached message size smaller than expected (20542 < 20640, box=INBOX, UID=475) dsync(vagrant): Error: read(./Maildir/cur/1296038598.29562.mail.micite.net,S=20542:2,Sa) failed: Cached message size smaller than expected (20542 < 20640, box=INBOX, UID=475) (uid=475, box=INBOX) dsync(vagrant): Error: Mailbox INBOX: read(msg input) failed: Cached message size smaller than expected (20542 < 20640, box=INBOX, UID=475) dsync(vagrant): Error: read(./Maildir/cur/1296038598.29562.mail.micite.net,S=20542:2,Sa) failed: Cached message size smaller than expected (20542 < 20640, box=INBOX, UID=475) (uid=475, box=INBOX) dsync(vagrant): Panic: file mail-index-transaction-update.c: line 964 (mail_index_update_ext): assertion failed: (seq > 0 && (seq <= mail_index_view_get_messages_count(t->view) || seq <= t->last_new_seq)) Abort (core dumped) (gdb) core doveadm.core Core was generated by `doveadm'. Program terminated with signal 6, Aborted. #0 0x00000008013f8a1a in ?? () (gdb) bt #0 0x00000008013f8a1a in ?? () #1 0x00000008013f7149 in ?? () #2 0x0000000000000000 in ?? () or with no core dump: % doveadm sync maildir:./Maildir dsync(vagrant): Error: read(./Maildir/cur/1296466748.64525.mail.micite.net,S=7629:2,Sa) failed: Cached message size smaller than expected (7629 < 7694, box=INBOX, UID=899) dsync(vagrant): Error: Maildir filename has wrong S value, renamed the file from ./Maildir/cur/1296466748.64525.mail.micite.net,S=7629:2,Sa to ./Maildir/cur/1296466748.64525.mail.micite.net,S=7694:2,Sa dsync(vagrant): Error: Corrupted index cache file ./Maildir/dovecot.index.cache: Broken physical size for mail UID 899 dsync(vagrant): Error: write(/home/vagrant/mdbox/storage/m.11) failed: Invalid argument dsync(vagrant): Error: copy: i_stream_read(./Maildir/cur/1296466748.64525.mail.micite.net,S=7629:2,Sa) failed: Cached message size smaller than expected (7629 < 7694, box=INBOX, UID=899) dsync(vagrant): Error: read(./Maildir/cur/1296466748.64525.mail.micite.net,S=7629:2,Sa) failed: Cached message size smaller than expected (7629 < 7694, box=INBOX, UID=899) (uid=899, box=INBOX) dsync(vagrant): Error: Mailbox INBOX: read(msg input) failed: Cached message size smaller than expected (7629 < 7694, box=INBOX, UID=899) dsync(vagrant): Error: read(./Maildir/cur/1296466748.64525.mail.micite.net,S=7629:2,Sa) failed: Cached message size smaller than expected (7629 < 7694, box=INBOX, UID=899) (uid=899, box=INBOX) % dovecot -n # 2.2.16: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 10.1-RELEASE-p6 amd64 mail_location = mdbox:~/mdbox namespace { inbox = yes location = prefix = separator = . } passdb { args = /usr/local/etc/dovecot/conf.d/dovecot-sql.conf.ext driver = sql } protocols = lmtp imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } user = vmail } ssl = required ssl_cert = </etc/ssl/ec/ec.crt ssl_key = </etc/ssl/ec/ec.key userdb { args = /usr/local/etc/dovecot/conf.d/dovecot-sql.conf.ext driver = sql } protocol lmtp { postmaster_address = postmaster(a)micite.net }

2 2

imap-login SSLv3 causes signal 11, core dump and DoS. ssl_protocols = ??
by James 21 Mar '15

21 Mar '15

Connecting to dovecot with ssl3 causes imap-login to die: $ openssl s_client -connect localhost:993 -ssl3 CONNECTED(00000003) 4277630796:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:s3_pkt.c:1461:SSL alert number 40 4277630796:error:1409E0E5:SSL routines:ssl3_write_bytes:ssl handshake failure:s3_pkt.c:645: --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 7 bytes and written 0 bytes --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE No ALPN negotiated SSL-Session: Protocol : SSLv3 Cipher : 0000 Session-ID: Session-ID-ctx: Master-Key: Key-Arg : None PSK identity: None PSK identity hint: None SRP username: None Start Time: 1426851034 Timeout : 7200 (sec) Verify return code: 0 (ok) --- syslog: Mar 20 11:30:35 MAILHOST dovecot: [ID 583609 mail.crit] imap-login: Fatal: master: service(imap-login): child 21918 killed with signal 11 (core dumped) [last ip=127.0.0.1] dovecot.conf had: ssl_protocols = !SSLv2 !SSLv3 removing that line stops the core dump and syslog then shows: Mar 20 11:36:25 MAILHOST dovecot: [ID 583609 mail.info] imap-login: Disconnected (disconnected before auth was ready, waited 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, TLS handshaking: SSL_accept() failed: error:14076102:SSL routines:SSL23_GET_CLIENT_HELLO:unsupported protocol, session=<eqr1ubYRWgB/AAAB> the "SSL23_GET_CLIENT_HELLO:unsupported protocol" seems to do what I thought the ssl_protocols setting did. Do I still need, if I ever needed, the "ssl_protocols = " setting? James. # dovecot -n # 2.2.16: /etc/opt/XXXX/dovecot/dovecot.conf # Pigeonhole version 0.4.7 # OS: SunOS 5.10 i86pc auth_mechanisms = plain login digest-md5 cram-md5 base_dir = /var/opt/XXXX/dovecot/ lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_trusted_networks = 111.222.333.444/24 mail_gid = vmail mail_home = /XXXXXX/XXXX/%d/%n mail_location = maildir:/XXXXX/XXXX/%d/%n/Maildir mail_max_userip_connections = 20 mail_plugins = quota mail_uid = vmail mailbox_idle_check_interval = 10 secs 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 index ihave duplicate passdb { args = /etc/opt/XXXX/dovecot/dovecot-sql.conf driver = sql } plugin { fts_autoindex = yes quota = maildir:User quota quota_rule = *:storage=1G quota_rule2 = Trash:storage=+10% quota_warning = storage=90%% quota-warning 90 %u quota_warning2 = storage=95%% quota-warning 95 %u quota_warning3 = storage=99%% quota-warning 99 %u sieve = /XXXXX/XXXX/%d/%n/dovecot.sieve sieve_dir = /XXXXX/XXXX/%d/%n/sieve } protocols = imap lmtp sieve service auth { drop_priv_before_exec = yes unix_listener auth-client { mode = 0660 } unix_listener auth-master { mode = 0600 } user = root } service imap-login { chroot = drop_priv_before_exec = yes executable = imap-login -D service_count = 1 user = dovecot } service lmtp { group = vmail unix_listener lmtp { mode = 0666 } user = vmail } service quota-warning { executable = script /etc/opt/XXXX/dovecot/quota-warning user = vmail } ssl_cert = </etc/opt/XXXX/dovecot/dovecot.pem ssl_cipher_list = AES128+EECDH:AES128+EDH ssl_key = </etc/opt/XXXX/dovecot/dovecot.pem ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 userdb { driver = prefetch } userdb { args = /etc/opt/XXXX/dovecot/dovecot-sql.conf driver = sql } protocol lda { auth_socket_path = /var/opt/XXXX/dovecot/auth-master mail_plugins = quota sieve postmaster_address = postmaster@XXXXXXXX sendmail_path = /opt/XXXX/sbin/exim } protocol pop3 { mail_plugins = quota } protocol imap { mail_plugins = quota imap_quota } protocol lmtp { mail_plugins = quota sieve postmaster_address = postmaster@XXXXXX sendmail_path = /opt/XXXX/sbin/exim }

3 9

Strange empty folders 1 1 1 1 1
by Samuel Williams 20 Mar '15

20 Mar '15

I just updated to the latest dovecot from 1.2 and it has been working great for most of my clients. But one client,who is using Outlook, has found that hundreds of folders have been created, e.g. admin@domain Deleted Items 1 admin@domain Deleted Items 1 1 admin@domain Deleted Items 1 1 1 .... admin@domain Deleted Items 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 This appears to be affecting all folders in his account, across multiple accounts for his domain. It isn't affecting any other user, even other users using outlook. All the folders are empty. Just wondering if anyone has any suggestions or ideas why this is happening. Thanks Samuel

1 0