- dovecot - dovecot.org

Panic: file istream-zlib.c: ...assertion failed: (ret == -1) / core dump on signal 6 / zlib
by C. Bernard 15 Jan '17

15 Jan '17

Hello! I have several gzip'ed mbox Files in my home dir and the problem occurs when I use one of the gzip'ed files as shown mbox in the gui and want to see one mail of it. It also happens on the extended search from Horde which then such a gzip'ed file. Example file: # file In_2014.gz In_2014.gz: gzip compressed data, was "In_2014", last modified: Wed Dec 2 10:53:22 2015, from Unix This happens with any gz Files. That's why I tried to sort out any problem else before submitting this. Directly connecting to dovecot imap (circumvention imapproxy) shows the same error. This setup was in place for 4 years with another server: It did not occur with dovecot 2.2.25 an up-imapproxy1.2.7 (Horde 5.2.12/imp5.2.16) on FreeBsd9.3-p55 (my old server). (I did not update to 2.2.27 on the last server as the maintainer just removed the ssl option from config I...and I knew I would update anyway soon,so I have no test of 2.2.27 with the old setup) The actual setup as follows: System is 10.3-RELEASE-p15 on amd64 Horde ist 5.2.13 / imp 6.2.17 / php-horde_lz4-1.0.7_1 (which is I guess unused here) Lz4 is liblz4-131 FS is UFS connection: Horde webmail -> 1143:imapproxyd:143 -> dovceot imap (or directly -> same) Jan 15 08:40:58 server dovecot: imap(xxx): Panic: file istream-zlib.c: line 416 (i_stream_zlib_seek): assertion failed: (ret == -1) Jan 15 08:40:59 server kernel: pid 73887 (imap), uid 1000: exited on signal 6 (core dumped) Jan 15 08:40:59 server dovecot: imap(xxx): Fatal: master: service(imap): child 73887 killed with signal 6 (core dumped) Jan 15 08:40:59 server HORDE: [imp] [fetch] IMAP error reported by server. [pid 69574 on line 730 of "/usr/local/www/htdocs/m/imp/lib/Imap.php"] Jan 15 08:40:59 server HORDE: [imp] [status] IMAP error reported by server. [pid 69574 on line 730 of "/usr/local/www/htdocs/m/imp/lib/Imap.php"] and Jan 15 08:40:56 server in.imapproxyd[912]: LOGOUT: 'xxx' from server sd [12] Jan 15 08:40:58 server in.imapproxyd[912]: LOGIN: 'xxx' (127.0.0.1:33269) on existing sd [12] Jan 15 08:40:59 server in.imapproxyd[912]: Get_Server_conn(): Unable to reuse server sd [12] for user 'xxx' (127.0.0.1:50504). Connection closed by server. # dovecot -n # 2.2.27 (c0f36b0): /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 10.3-RELEASE-p11 amd64 auth_mechanisms = plain login disable_plaintext_auth = no first_valid_gid = 100 first_valid_uid = 1000 mail_location = mbox:~/:INBOX=/var/mail/%u mail_plugins = " zlib" mail_privileged_group = mail passdb { args = session=yes dovecot driver = pam } protocols = imap pop3 service auth { unix_listener auth-client { mode = 0660 } unix_listener auth-master { mode = 0600 } user = root } service imap { drop_priv_before_exec = yes } ssl = no userdb { args = blocking=yes driver = passwd } verbose_proctitle = yes protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } protocol lda { sendmail_path = /usr/sbin/sendmail } (gdb) bt full #0 0x000000001115c39a in thr_kill () from /lib/libc.so.7 #1 0x000000001115c386 in raise () from /lib/libc.so.7 #2 0x000000001115c309 in abort () from /lib/libc.so.7 #3 0x0000000010e1c9b4 in default_fatal_handler () from /usr/local/lib/dovecot/libdovecot.so.0 #4 0x0000000010e1d6e1 in i_set_failure_internal () from /usr/local/lib/dovecot/libdovecot.so.0 #5 0x0000000010e1cc59 in i_panic () from /usr/local/lib/dovecot/libdovecot.so.0 #6 0x000000001144ffae in i_stream_create_deflate () from /usr/local/lib/dovecot/lib20_zlib_plugin.so #7 0x0000000010e28051 in i_stream_seek_mark () from /usr/local/lib/dovecot/libdovecot.so.0 #8 0x0000000010ad7f15 in istream_raw_mbox_seek () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #9 0x0000000010ad864d in mbox_file_seek () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #10 0x0000000010ada7ad in mbox_dotlock_touch () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #11 0x0000000010ada367 in mbox_dotlock_touch () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #12 0x0000000010a9d365 in mail_get_hdr_stream_because () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #13 0x0000000010b0cbe5 in index_mail_parse_headers () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #14 0x0000000010b0f9d9 in index_mail_get_special () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #15 0x0000000010b0f7b9 in index_mail_get_special () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #16 0x0000000010a9d49f in mail_get_special () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #17 0x000000000041cf1d in imap_fetch_handlers_deinit () #18 0x000000000041c561 in imap_fetch_more () #19 0x000000000041c1f8 in imap_fetch_more () #20 0x000000000040ff4e in cmd_fetch () #21 0x000000000041a4e6 in command_exec () #22 0x0000000000419573 in clients_destroy_all () #23 0x000000000041974f in clients_destroy_all () #24 0x0000000000418d9e in client_handle_input () #25 0x000000000041786c in client_input () #26 0x0000000010e31619 in io_loop_call_io () from /usr/local/lib/dovecot/libdovecot.so.0 #27 0x0000000010e3338d in io_loop_handler_run_internal () from /usr/local/lib/dovecot/libdovecot.so.0 #28 0x0000000010e31b33 in io_loop_handler_run () from /usr/local/lib/dovecot/libdovecot.so.0 #29 0x0000000010e31908 in io_loop_run () from /usr/local/lib/dovecot/libdovecot.so.0 #30 0x0000000010dbca08 in master_service_run () from /usr/local/lib/dovecot/libdovecot.so.0 #31 0x00000000004253f4 in main () Thanks C.

1 0

TLS feature missing
by Tributh 13 Jan '17

13 Jan '17

Hi, i was using dovecot 2.2.25 compiled with opnessl 1.0.2 I realised with a cipherscan utility that i was able to support mulitiple TLS curves. Now i upgraded to 2.2.27 with opnessl1.1.0 and was falling back to historical stages where my server only servers one TLS-curve: secp384r1 right now. One big reason to compile the new ersion with openssl1.1.0 was to bring CHACHA20-POLY1305 ciphers and X25519 curves to modern clients. The ciphers i am estimating are working fine, but X25519 and also secp521r1 ist now longer supported, like it was in dovecot 2.2.25. Is there something broken? Or a new (know missing) config feature? Or is it a bug ? Regards Torsten

1 0

Re: doveadm mailbox cryptokey - not found
by Evgeniy Korneechev 12 Jan '17

12 Jan '17

> > You forgot to load mail_crypt plugin. > > mail_plugins = $mail_plugins mail_crypt > With these settings also. # dovecot -n ..... mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_plugins = " mail_crypt" mbox_write_locks = fcntl ..... # service dovecot restart # doveadm mailbox cryptokey usage: doveadm [-Dv] [-f ......... # ls /usr/lib64/dovecot/modules/* | grep mail_crypt /usr/lib64/dovecot/modules/lib05_mail_crypt_acl_plugin.so /usr/lib64/dovecot/modules/lib10_mail_crypt_plugin.so /usr/lib64/dovecot/modules/libfs_mail_crypt.so /usr/lib64/dovecot/modules/doveadm/libdoveadm_mail_crypt_plugin.so -- WBR, BaseALT/ALTLinux Team

1 1

doveadm mailbox cryptokey - not found
by Evgeniy Korneechev 12 Jan '17

12 Jan '17

Hi, we have a problem. Command "doveadm mailbox cryptokey" does not work: # doveadm mailbox cryptokey usage: doveadm [-Dv] [-f <formatter>] mailbox <command> [<args>] create [-u <user>|-A] [-S <socket_path>] [-s] [-g <guid>] <mailbox> [...] delete [-u <user>|-A] [-S <socket_path>] [-e] [-r] [-s] [-Z] <mailbox> [...] ...... What is the problem? ------------------------------------------------ Install: http://wiki2.dovecot.org/CompilingSource#Compiling_Dovecot_From_Sources : ./configure && make && sudo make install # dovecot -n # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # OS: Linux 4.4.38-std-def-alt0.M80P.1 x86_64 ALT starter kit (Hypericum) mail_location = mbox:~/mail:INBOX=/var/mail/%u mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } ssl = required ssl_cert = </var/lib/ssl/certs/dovecot.pem ssl_key = # hidden, use -P to show it userdb { driver = passwd } -- WBR, BaseALT/ALTLinux Team

3 2

Unable to access apt.dovecot.fi
by Alexandre Ellert 12 Jan '17

12 Jan '17

Hi, I bought a Dovecot Enterprise repository acces in 2013 and since several months, I can't access it anymore. It seem that my credential are broken. When doing an apt-get update : W: Failed to fetch http://apt.dovecot.fi/3rdparty/debian/wheezy/dists/wheezy/main/binary-amd64… 401 Unauthorized W: Failed to fetch http://apt.dovecot.fi/stable-2.2/debian/wheezy/dists/wheezy/main/binary-amd… 401 Unauthorized And here is my sources.list : # cat /etc/apt/sources.list.d/dovecot.list deb http://USER:PASSWORD@apt.dovecot.fi/stable-2.2/debian/wheezy wheezy main # cat /etc/apt/sources.list.d/dovecot-3rdparty.list deb http://USER:PASSWORD@apt.dovecot.fi/3rdparty/debian/wheezy wheezy main Thank you for help. Alexandre

2 1

Broken OS after upgrade
by Odhiambo Washington 11 Jan '17

11 Jan '17

Hi, I have broken my OS (FreeBSD) after upgrade, making me unable to compile dovecot the usual way so I am seeking a 3rd eye. The config.log is at : http://bit.ly/2jE5djl Hoping someone can help me figure out what is broken. During configure, it fails with: checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... unknown checking for _LARGE_FILES value needed for large files... unknown checking for _Bool... yes checking for uoff_t... no checking type of off_t... unknown configure: error: Unsupported off_t type -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft."

2 2

multiple shared/mail format namespaces
by Michal Soltys 11 Jan '17

11 Jan '17

Hi, Are configurations (with separate formats per namespace) - such as ... namespace { type = shared list = children inbox = no separator = / subscriptions = no prefix = shared1/%%n/ location = maildir:/var/mail1/%%n/ } namespace { type = shared list = children inbox = no separator = / subscriptions = no prefix = shared2/%%n/ location = mdbox:/var/mail2/%%n/ } With separate userdbs serving part of the users with maildirs in /var/mail1/ and the other part with mdboxes in /var/mail2 ... valid in dovecot ? To be more precise: 1) Is current version dovecot expected to work with configuration as above ? E.g. if some user's mail location returned from userdb doesn't match location/format from one of the above namespaces - would it be ignored for it ? A very old version of dovecot I could check quickly (2.1.7) was segfaulting (imap processes) all the time with this kind of config. While I'll be upgrading it and the whole system to modern versions, I'm wondering if this kind of thing is formally allowed at all. An interesting variation of the above setup I tested - with the second namespace "un-variabled" and pointing to single user (with matching passwd-file returning that user) managed to work somehow - but the user itself was still created on the fly for the 1st namespace - having just a directory with empty dovecot-acl-list file. This essentially seemed to have worked like a typical public profile (shared acl db didn't seem to be used either) 2) For shared namespace with variables, would overriding shared namespace location in userdb query work ? For example if we had single namespace such as the first one (maildir) above with explicit share1 name, and then in userdb for some users: userdb_namespace/share1/location=mdbox:/var/mail2/some_user_name Would that override a shared namespace pattern on per user basis correctly ? 3) Is there perhaps a way to constraint which userdbs are considered per which shared namespace ? 4) Not strictly related to the above, but in LDAP part of documentation - namely http://wiki2.dovecot.org/AuthDatabase/LDAP/Userdb - why user_attrs = \ =home=%{ldap:homeDirectory}, \ =uid=%{ldap:uidNumber}, \ =gid=%{ldap:gidNumber} instead of user_attrs = \ homeDirectory=home, \ uidNumber=uid, \ gidNumber=gid Do both are equivalent with differet syntax (opening the way for templates for %{} based syntax), or are there some subtle differences between those ? (aside later example with 'attr=' instead of just '='). Would this kind of syntax also be correct for pass_attrs, such as: pass_attrs = \ =password=%{ldap:uid}, \ =userdb_home=%{ldap:homeDirectory}

3 6

Ban dots in folder names
by Marek Grondecki 11 Jan '17

11 Jan '17

Hello Dovecot Community, I am using Dovecot 2.2.13-12~deb8u1 (Debian Jessie). separator = / listescape plugin is NOT active LAYOUT=fs is NOT active I would like to prohibit/ban the creation of folders with dot "." in the names - so creation of a folder "foo.bar" should NOT be possible. Currently, when I create "foo.bar" in Outlook 2013 it will be created but won't be synchronised with the mail server - Outlook shows it as "foo.bar (Only this computer)". Ideally the user should receive an error message informing that "the folder foo.bar could not be created." Thank you for your help. Regards, Marek Grondecki

2 1

pigeonhole + spamprobe
by Mark Constable 11 Jan '17

11 Jan '17

Would anyone have an example of how to use dovecot-pigeonhole to call spamprobe as an external program in the current 2.2.25?

1 0

Dovecot and MariaDB/MySQL
by Michael A. Peters 11 Jan '17

11 Jan '17

Howdy - For most of my dovecot servers, they are small and I just use unix accounts. However I am going to be running a new server for more general users, webmail (probably roundcube but I'm hacking roundcube quite a bit, enough that I'm calling it squarepeg instead so users familiar with roundcube will know it is quite different) and it will use MariaDB for account management. I already have it working, following the instructions at https://www.linode.com/docs/email/postfix/email-with-postfix-dovecot-and-my… - those instructions also work in CentOS 7 with the latest Dovecot - but there is something that really bothers me. It makes no provision for salting the password before the crypt function. What I would like to do is when creating a new account, use /dev/urandom to generate a random salt for the account that is stuck in the database along with the account and used when validating the password. That way in the event of a SQL injection attack that dumps the database - yes it is still bad, but 20 accounts that have the same password will have radically different hashes and thus won't be a clue that they are the same, the blackhat that gets the database dump would have to generate a rainbow table for each unique salt. I've looked at at least a dozen different Dovecot / MariaDB howto guides and none of the ones I have looked at supported any kind of individual salting of the user passwords. Can someone point me to a guide that does? I don't mind keeping the salt in the database, I just want to be able to have a different salt for each account. Thank you

2 2