- dovecot - dovecot.org

Update Kills Dovecot
by Sven Roellig 07 Jun '16

07 Jun '16

Hi,i run Dovecot 2.3.0 Alpha The last two Updates broken dovecot.in the mail.war log i became the error, on every mail, ..........de)<3+RHF1k4VFfDOwAApDKQ5A>: Fatal: master: service(lmtp): child 15299 killed with signal 6 (core dumps disabled) Jun 5 16:39:40 director dovecot: lmtp(roellig(a)*******.org)<1o6JAKw5VFcPPAAApDKQ5A>: Panic: file imem.c: line 60 (i_strconcat): assertion failed: (str1 != NULL) ....dovecot: lmtp(roellig(a)*******.org)<1o6JAKw5VFcPPAAApDKQ5A>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x8cfbe) [0x7f62fe5defbe] -> /usr/lib/dovecot/libdovecot.so.0(+0x8d0ac) [0x7f62fe5df0ac] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f62fe57dd1e] -> /usr/lib/dovecot/libdovecot.so.0(i_strconcat+0x146) [0x7f62fe5e6bb6] -> /usr/lib/dovecot/libdovecot-lda.so.0(duplicate_init+0x5d) [0x7f62feba1dfd] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x3c) [0x7f62feba47bc] -> dovecot/lmtp(+0x6ac8) [0x7f62fefd3ac8] -> dovecot/lmtp(+0x73cf) [0x7f62fefd43cf] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7f62fe5f2ffc] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x101) [0x7f62fe5f4461] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7f62fe5f3085] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f62fe5f3228] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f62fe584273] -> dovecot/lmtp(main+0x165) [0x7f62fefd21a5] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f62fe1c8b45] -> dovecot/lmtp(+0x5293) [0x7f62fefd2293] the errors is from update to dovecot-lmtpd_2%3a2.3.0~alpha0-1~auto+67_amd64.deb on debian 8.3on the morning it came an update to debian 8.4 an dovecot dovecot-lmtpd_2%3a2.3.0~alpha0-1~auto+78_amd64.deb can anyone help Sorry for my english. Sven

3 2

[PATCH v2 0/7] Fixes for lib-mail message-address
by Pali Rohár 05 Jun '16

05 Jun '16

Hello, I borrowed dovecot parser for email addresses and I'm using it in my new perl module Email::Address::XS for parsing & formatting list of email addresses. That perl module is available at github [1]. During implementation and testing I found bugs in dovecot code. So I'm sending my patches (together with tests) which I'm using in my perl module. Lot of other (normal & corner) test cases are part of that perl module [2], so if you are interested feel free to reuse them. Because writing new test cases for dovecot is hard for me, I'm not going to do it. In perl for perl modules it is a lot of easier for me. [1] - https://github.com/pali/Email-Address-XS [2] - https://github.com/pali/Email-Address-XS/blob/master/t/Email-Address-XS.t Changes since v1: * Updated description with test example * Rebased on top of master branch Pali Rohár (7): lib-mail: message_address_write: Fix generating empty group list lib-mail: message_address_write: Fix generating group list with empty name lib-mail: parse_addr_spec: Like in rfc822_skip_comment() check if last_comment is not NULL lib-mail: parse_addr_spec: Email address without local-part is invalid lib-mail: parse_mailbox: Set display name instead mailbox when parsing failed lib-mail: message_address_write: Quote and escape strings if needed lib-mail: Update tests for message address src/lib-mail/message-address.c | 99 +++++++++++++++++++++++++++++++---- src/lib-mail/test-message-address.c | 11 +++- 2 files changed, 98 insertions(+), 12 deletions(-) -- 1.7.9.5

1 7

Shared Mailbox?
by craig 04 Jun '16

04 Jun '16

Hi, I've been doing a lot of reading on this topic, I'm just finding a lot of doco that's potentially out of date now? System: Red Hat Enterprise Linux Server release 7.2 (Maipo) dovecot-2.2.10-5.el7.x86_64 The need: 1. I'd like to create a mailbox called "accounts", email would simply get delivered to the account via "accounts(a)example.com" (Maildir format) 2. Share this mailbox so it appears in three other accounts as an extra folder called "accounts" 3. If a user reads an email in the "accounts" folder, I'd like the other users to know this. Clients: * Latest Thunderbird * Outlook 2013. Any advice welcome ;) Cheers, Craig

3 2

Doveadm HTTP API - Disconnected for inactivity
by Ricardo Machini Barbosa 04 Jun '16

04 Jun '16

Hello, I am doing some calls using doveadm http API and I noticed that when some calls took more than 5 seconds the connection are closed, this happen general with huge mailbox's. There are some kind of timeout that I have to set ? For example: # curl call time curl -v --user doveadm:senha -H "Content-Type: application/json" -d '[["purge",{"user":"email(a)dominio.com.br"},"c01"]]' http://192.168.0.1:8080/doveadm/v1 * About to connect() to 192.168.0.1 port 8080 (#0) * Trying 192.168.0.1... connected * Connected to host (192.168.0.1) port 8080 (#0) * Server auth using Basic with user 'doveadm' > POST /doveadm/v1 HTTP/1.1 > Authorization: Basic XXXXXX > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.19.1 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2 > Host: 192.168.0.1:8080 > Accept: */* > Content-Type: application/json > Content-Length: 69 > * Empty reply from server * Connection #0 to host 192.168.0.1 left intact curl: (52) Empty reply from server * Closing connection #0 real 0m5.432s user 0m0.003s sys 0m0.002s # server log Jun 3 17:11:09 host dovecot: doveadm(192.168.0.2): Executing command 'purge' as 'email(a)dominio.com.br' Jun 3 17:11:14 host dovecot: doveadm: http-server: conn 192.168.0.2:59617 [1]: Disconnected for inactivity Regards, Ricardo

2 1

dovecot-sieve help
by 句号先生。 | 03 Jun '16

03 Jun '16

hi, I have a question hope to get everybody's help, thank you. I write the dovecot sieve rules, use notify:mailto. such as mailto:mymail@dovecot.org, this is ok.but i want to go to a url address,like this,mailto:"http://http://wiki.dovecot.org/".but i don't know how to do it.I hope you can help me.thanks.

3 2

nginx proxy to dovecot servers
by KT Walrus 03 Jun '16

03 Jun '16

I’m trying to understand how the nginx mail proxy and dovecot work. As a I understand it, nginx can listen on a IP:port for IMAP connections. NGINX then can invoke a PHP script to do authorization and backend server selection. Does NGINX than proxy to the backend dovecot IMAP server all subsequent IMAP commands that the user’s mail client requests? Does the backend dovecot IMAP server do its own authentication with another MySQL password lookup? Or, since NGINX has done the authentication, the password_query lookup is skipped on the dovecot server? I assume the dovecot IMAP server still needs to do a MySQL user_query lookup (to find the location of the user’s mailbox on the server), but I am wondering whether the password will be checked twice, once by NGINX and a second time by dovecot IMAP. Kevin

4 6

zlib corrupted data
by Angel L. Mateo 03 Jun '16

03 Jun '16

Hello, We are having performance problems with one of our users. We are having a server (2.1.16) for about 8000 users. This server is a vmware vm with 8 cores and 32GB of RAM. Normally, it is working fine, but when one of our users access his email, then the load increases a lot and this high load is maintained while the user is connected. Looking for problems with this user I have found that trying to move messages from one folder to another I have errors like: doveadm(mctm(a)um.es): Error: zlib.read(/mail/users/mailboxes/um.es/mc/mctm/mdbox/storage/m.1486): corrupted data at 30152376 doveadm(mctm(a)um.es): Error: zlib_istream.seek(/mail/users/mailboxes/um.es/mc/mctm/mdbox/storage/m.1486) failed: Invalid argument doveadm(mctm(a)um.es): Error: zlib.read(/mail/users/mailboxes/um.es/mc/mctm/mdbox/storage/m.1473): corrupted data at 7175520 doveadm(mctm(a)um.es): Error: zlib_istream.seek(/mail/users/mailboxes/um.es/mc/mctm/mdbox/storage/m.1473) failed: Invalid argument but a doveadm dump of these files shows no problem. Is there any way to debug this problem? How could I fix it? -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868887590 Fax: 868888337

1 0

AD query timeout might be result size limit exceeded
by Julien Lambot 03 Jun '16

03 Jun '16

Hello list I've been struggling for a while trying to configure multiple domain ldap authentication with full e-mail address authentication. Which in fact was not the issue. There where some discrepancies between the doc and our actual configuration (see appendix A/ ) Seems that pass_filters and user_filters don't need much special settings for our setup. Now it's working correctly at the sole exception that when an OU contains "lots" of users (>200) i suspect that the ldapseach query fails. We can well authenticate when we have 50 users in an OU, but not when the number raises (I don't have the exact number above which it locks). Is there a parameter that we can set to increase the result size limit (as i suspect this to be the cause of this possible bug)? If I query manually it's ok (ldapsearch) if I use "doveadm auth user.name(a)domain.tld", it succeed also but I wonder if it doesn't use the winbind authentication instead. Here is our ldap-auth configuration hosts = master.domain.local:389 dn = DOMAIN\ro-user dnpass = password debug_level = 2 auth_bind = yes #auth_bind_userdn = cn=%u,OU=_myou,OU=Utilisateurs,OU=ouname,DC=domain,DC=local (tried with and without with no better results) ldap_version = 3 #deref = never #base = OU=InfrastructureManagement,DC=domain,DC=local (works has a few users) base = OU=_myou,OU=Utilisateurs,OU=ouname,DC=domain,DC=local scope = subtree user_filter = (&(objectclass=person)(mail=%u)) pass_filter = (&(objectclass=person)(mail=%u)) and some logs in appendix B/ Thanks for any hints on this. Have a nice day appendix A/ # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.7 auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-userdb default_vsz_limit = 1 G disable_plaintext_auth = no first_valid_gid = 5000 first_valid_uid = 5000 last_valid_gid = 50000 last_valid_uid = 50000 mail_gid = 5000 mail_home = /var/vmail/%d/%n mail_location = maildir:~/mail mail_privileged_group = virtmail mail_uid = 5000 namespace inbox { hidden = no 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 = subscriptions = yes } passdb { args = scheme=plain-md5 username_format=%u /etc/dovecot/users driver = passwd-file } passdb { args = scheme=plain-md5 username_format=%u /etc/dovecot/users driver = passwd-file } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } passdb { args = /etc/dovecot/pirisusers-ldap.conf.ext driver = ldap } protocols = imap service auth { unix_listener auth-userdb { mode = 0666 user = virtmail } } ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } userdb { args = /etc/dovecot/dovecot-ldap-users.conf.ext driver = ldap } userdb { args = /etc/dovecot/pirisusers-ldap-users.conf.ext driver = ldap } protocol lda { postmaster_address = postmaster(a)domain.tld } protocol imap { mail_plugins = } appendix B/ May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: ldap_int_select May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: read1msg: ld 0x7fcc0a585fa0 msgid 14 all 1 May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: read1msg: ld 0x7fcc0a585fa0 msgid 11 message type search-reference May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: ldap_chase_v3referrals May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: ldap_url_parse_ext(ldap://ForestDnsZones.domain.local/DC=ForestDnsZones,DC=domain,DC=local) May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: re_encode_request: new msgid 15, new dn <DC=ForestDnsZones,DC=domain,DC=local> May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: re_encode_request new request is: May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: ldap_chase_v3referral: msgid 11, url "ldap://ForestDnsZones.domain.local/DC=ForestDnsZones,DC=domain,DC=local" May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: ldap_send_server_request May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: ldap_new_connection 0 1 1 May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: ldap_int_open_connection May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: ldap_connect_to_host: TCP ForestDnsZones.domain.local:389 May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: ldap_new_socket: 21 May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: ldap_prepare_socket: 21 May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: ldap_connect_to_host: Trying 10.1.2.34:389 May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: ldap_pvt_connect: fd: 21 tm: -1 async: 0 May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: anonymous rebind via ldap_sasl_bind("") May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: ldap_sasl_bind May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: ldap_send_initial_request May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: ldap_send_server_request May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: ldap_result ld 0x7fcc0a585fa0 msgid 16 May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: wait4msg ld 0x7fcc0a585fa0 msgid 16 (timeout 100000 usec) May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: wait4msg continue ld 0x7fcc0a585fa0 msgid 16 all 1 May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: ** ld 0x7fcc0a585fa0 Connections: May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: * host: ForestDnsZones.domain.local port: 0 May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: refcnt: 2 status: Connected May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: last used: Thu May 19 12:57:36 2016 May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: rebind in progress May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: queue is empty May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: * host: DomainDnsZones.domain.local port: 0 May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: refcnt: 2 status: Connected May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: last used: Thu May 19 12:57:36 2016 May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: rebind in progress May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: queue is empty May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: * host: master.domain.local port: 389 (default) May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: refcnt: 4 status: Connected May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: last used: Thu May 19 12:57:36 2016 May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: ** ld 0x7fcc0a585fa0 Outstanding Requests: May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: * msgid 16, origid 16, status InProgress May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: outstanding referrals 0, parent count 0 May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: * msgid 14, origid 14, status InProgress May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: outstanding referrals 0, parent count 0 May 19 12:57:36 iftstpupimap1 dovecot: auth: Error: * msgid 11, origid 11, status InProgress May 19 13:00:06 iftstpupimap1 dovecot: auth: Error: PLAIN(): Request 0.1 timeouted after 150 secs, state=1

1 1

Blowfish hashed passwords
by KT Walrus 03 Jun '16

03 Jun '16

The PHP app I’m using on my website uses PHP to generate password hashes to be stored into the user database. These password hashes use Blowfish encryption ("$2y$”). In fact, since PHP 5.3.0, PHP contains its own implementation of the hash types it supports including: - CRYPT_STD_DES - CRYPT_EXT_DES - CRYPT_MD5 - CRYPT_BLOWFISH - CRYPT_SHA256 - CRYPT_SHA512 The C code for these hash types is in https://github.com/php/php-src/tree/master/ext/standard <https://github.com/php/php-src/tree/master/ext/standard> I’m working on adding Dovecot to my site, but Dovecot doesn’t seem to support Blowfish password hashes (at least on Ubuntu 14.04). Would you consider adding built-in “fallback” support for Blowfish and SHA512 (which doesn’t seem to be supported either on Ubuntu 14.04 last time I checked) to an upcoming Dovecot release? You could probably take the source code from the GitHub PHP repo to incorporate support for these hash types in Dovecot. That way, Dovecot could easily use the same hash types that PHP supports regardless of what hash types are installed in the OS running Dovecot. And, I wouldn’t have to deal with a second set of hashes for Dovecot passdb for my existing user accounts. See PHP manual for crypt function: http://php.net/manual/en/function.crypt.php Kevin

2 1

stat .../.dovecot.sieve/tmp failed: Not a directory
by Robert Schetterer 02 Jun '16

02 Jun '16

Hi, i have stat .../.dovecot.sieve/tmp failed: Not a directory using sieve = file:~/sieve;active=~/.dovecot.sieve dovecot_2.2.24-1-auto-38 cause i can subscribe to dovecot sieve cant remember to see this in previous versions any idea ? Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG, 80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

3 5