June 2017 - dovecot - dovecot.org

v2.2.30.1 released
by Timo Sirainen 09 Jun '17

09 Jun '17

https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig Due to some release process changes I didn't notice that one important bugfix wasn't included in the v2.2.30 release branch before I made the release. So fixing it here with v2.2.30.1. Also included another less important fix. - quota_warning scripts weren't working in v2.2.30 - vpopmail still wasn't compiling Also I guess should mention that in v2.2.30+ the "script" service's protocol changed to a new version. If anyone had written their own script services (not using the included "script" binary) they would need some changes. I haven't heard of anyone having done that though.

7 16

[Dovecot] Dovecot stops with "Fatal: kevent(): Invalid argument"
by Henrik Larsson 09 Jun '17

09 Jun '17

# 2.0.11: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 8.2-STABLE amd64 Dovecot stops with the following logged: - master: Fatal: kevent(): Invalid argument I have found that a diff was created for "src/lib/ioloop-kqueue.c" for a similar issue: http://dovecot.org/pipermail/dovecot/2010-November/054855.html I have patched my system with this and haven't seen the problem since, but I don't know if this is a coincidence. Could you please explain if the diff should actually fix anything or just add some more logging in case it stops again? Best regards Henrik Larsson

4 9

Dovecot LDAP using custom field to allow users to connect
by Michael JOIGNY 09 Jun '17

09 Jun '17

Hi all, I'd like to know if it's possible to add a custom field when the authentification is made by users. My boolean custom field will be for example "AllowUser" (false/true). I'm trying to do something like that but it's not working : /user_filter = (&(objectClass=posixAccount)(uid=%u)(objectClass=myclass)(AllowUser=TRUE))/ This is my dovecot/ldap configuration below : /*# dovecot.conf* / /passdb {// // driver = ldap// // args = /etc/dovecot/dovecot-ldap.conf// //}/ *# dovecot-ldap.conf* /hosts = myurl:myport// //dn = cn=myuser,dc=mydomain,dc=com// //dnpass = ********// //a//uth_bind = yes// //auth_bind_userdn = uid=%u,ou=users,dc=mydomain,dc=com// //ldap_version = 3// //base = ou=Users,dc=mydomain,dc=com// //scope = base// //default_pass_scheme = SSHA512 / Do you have an idead ? Kind regards. -- Michael

2 3

lmtp: Error: Temp file creation to /tmp/ ... failed: No such file or directory on incoming mails with attachments
by Lars-Sören Steck 09 Jun '17

09 Jun '17

Dear list, I'm currently facing problems when receiving eMails with attachments, at least sometimes. My mailserver is set up with the tool 'Mailcow', and hence is based on Dovecot (2.2.22 (fe789d2)) and Postfix. Usually, there are no problems with receiving mails. If a mail has an attachment, however, it is possible that the following error occurs (extract from /var/log/mail.log): 'Jun 7 12:50:28 mail postfix/lmtp[26827]: 564E68A0515: to=<abc(a)def.ghj>, relay=my.mail.server[private/dovecot-lmtp], delay=0.71, delays=0.67/0.01/0.01/0.02, dsn=4.3.0, status=deferred (host my.mail.server[private/dovecot-lmtp] said: 451 4.3.0 Temporary internal failure (in reply to end of DATA command))' Extract from /var/log/mail.err: 'Jun 7 12:50:28 mail dovecot: lmtp(26828): Error: Temp file creation to /tmp/dovecot.lmtp.mail.26828. failed: No such file or directory' Once this happened the first time after dovecot is running, it will happen for all incoming mails with attachments. This can be solved temporarily by restarting the dovecot service and running postqueue -f, but that obviously does not solve the underlying problem. In this post to this list, it is stated that dovecot sometimes creates temp files to avoid 'excessive memory usage'. I'm guessing that this is the case here, also the error message is similiar: https://dovecot.org/list/dovecot/2016-June/104722.html Should I simply change the configuration variable mail_temp_dir to solve this? Why is dovecot not able to find the /tmp folder? In the list thread, it is stated that this is caused by dovecot running with enabled chrooting. As far as I understand it though (correct me if I'm wrong), chrooting is not enabled in my dovecot configuration. Please find attached the output of 'dovecot -n': # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.0-78-generic x86_64 Ubuntu 16.04.2 LTS auth_mechanisms = plain login dict { sqlquota = mysql:/etc/dovecot/dovecot-dict-sql.conf } listen = * log_timestamp = "%Y-%m-%d %H:%M:%S " login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_home = /var/vmail/%d/%n mail_location = maildir:~/ mail_max_userip_connections = 500 mail_plugins = quota acl fts fts_solr 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 mime foreverypart extracttext namespace { list = yes location = maildir:%%h/:INDEXPVT=~/Shared/%%u prefix = Shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Archiv { special_use = \Archive } mailbox Archive { auto = subscribe special_use = \Archive } mailbox Archives { special_use = \Archive } mailbox "Deleted Messages" { special_use = \Trash } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Entwürfe { special_use = \Drafts } mailbox "Gelöschte Objekte" { special_use = \Trash } mailbox Gesendet { special_use = \Sent } mailbox "Gesendete Objekte" { special_use = \Sent } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Papierkorb { special_use = \Trash } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } plugin { acl = vfile acl_anyone = allow acl_shared_dict = file:/var/vmail/shared-mailboxes.db fts = solr fts_autoindex = yes fts_solr = url=http://127.0.0.1:8983/solr/ quota = dict:Userquota::proxy::sqlquota quota_rule2 = Trash:storage=+100%% sieve = /var/vmail/sieve/%u.sieve sieve_after = /var/vmail/sieve/global.sieve sieve_max_script_size = 1M sieve_quota_max_scripts = 0 sieve_quota_max_storage = 0 } protocols = imap sieve lmtp pop3 service auth { unix_listener /var/spool/postfix/private/auth_dovecot { group = postfix mode = 0660 user = postfix } unix_listener auth-master { mode = 0600 user = vmail } unix_listener auth-userdb { mode = 0600 user = vmail } user = root } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } user = vmail } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 2 service_count = 1 vsz_limit = 128 M } service managesieve { process_limit = 256 } ssl_cert = </etc/ssl/mail/mail.crt ssl_cipher_list = EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH:+CAMELLIA256:+AES256:+CAMELLIA128:+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ECDSA:CAMELLIA256-SHA:AES256-SHA:CAMELLIA128-SHA:AES128-SHA ssl_dh_parameters_length = 2048 ssl_key = </etc/ssl/mail/mail.key ssl_protocols = !SSLv3 !SSLv2 userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } protocol imap { mail_plugins = quota imap_quota imap_acl acl fts fts_solr } protocol lmtp { auth_socket_path = /var/run/dovecot/auth-master mail_plugins = quota sieve acl fts fts_solr postmaster_address = postmaster(a)steck.cc } protocol sieve { managesieve_logout_format = bytes=%i/%o } remote 127.0.0.1 { disable_plaintext_auth = no } Thank you for your help. Lars

2 2

Re: Any documentation around timeout states ?
by Joseph Tam 08 Jun '17

08 Jun '17

> Hi, this has been fixed in more recent release, where the states are > converted to human readable strings, see > > https://git.dovecot.net/dovecot/core/commit/e7d9dd003e6192b294507b9fbe9917a… Internal name I guess. For the rest of us: https://github.com/dovecot/core/commit/e7d9dd003e6192b294507b9fbe9917a514e4… Joseph Tam <jtam.home(a)gmail.com>

1 0

Re: Dovecot login is slow
by Aki Tuomi 08 Jun '17

08 Jun '17

Can you try adding blocking=yes to your dovecot-ldap.conf.ext Aki On 08.06.2017 11:15, Mitocariu Emilian wrote: > No, other servers use the same LDAP and the response is fast. The > weird part is that this morning i played a little with the > configuration, but in the end i came back to the settings i had > previously and now it works better, but from time to time it still > hangs a little > > On Thu, Jun 8, 2017 at 11:07 AM, Aki Tuomi <aki.tuomi(a)dovecot.fi > <mailto:aki.tuomi@dovecot.fi>> wrote: > > > > On 07.06.2017 16:34, Mitocariu Emilian wrote: > > Hi, > > > > I have an Ubuntu 16.04 server with dovecot 2.2.22 configured as > an imap > > server with an LDAP backend for authentication. This is the > output of > > "dovecot -n": > > # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf > > The problem i'm having is that when i try to login it takes more than 10 > > seconds, making my webmail very slow. For testing i login to > imap like this > > "openssl s_client -connect localhost:993" and sometimes i get > this message > > "* OK Waiting for authentication master process to respond..". I > saw at > > other people, one of the problem was because they didn't > disabled pam > > authentication when using another backend (like ldap or sql), > but i already > > did that. > > > > Does anyone know what could cause such long login times and how > to fix it? > > Does your LDAP take long time to respond? > > Aki > >

1 0

mail storage auto detection failed?
by Alef Veld 08 Jun '17

08 Jun '17

Hi everyone. Nice to meet you. I’m new to dovecot and i came across a problem it seems. I setup a new user called sales with useradd, and gave it a password. Although it has a home directory, i set login to /sbin/nologin. When logging into the pop server on port 110 (with telnet) i get this in the logs: dovecot: pop3-login: Login: user=<sales>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=12938, secured, session=<94SotWVRoAB/AAAB> Jun 7 21:49:24 www dovecot: pop3(sales): Error: user sales: Initialization failed: Namespace '': Mail storage autodetection failed with home=/home/sales Jun 7 21:49:24 www dovecot: pop3(sales): Error: Invalid user settings. Refer to server log for more information. Did i have to initialise the mailbox in the homedirectory? What did i forget. I didn't change anything to the default dovecot.conf, i just installed the package with yum install dovecot (so latest version). This error also shows up when logging into port 143. Thanks for your help. My dovecot -n output if that helps is : [ec2-user@www log]$ dovecot -n # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 4.9.20-10.30.amzn1.x86_64 x86_64 mbox_write_locks = fcntl namespace inbox { inbox = yes location = prefix = } passdb { driver = pam } ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem ssl_protocols = !SSLv2 !SSLv3 userdb { driver = passwd } Thanks a lot. -atv

2 1

Any documentation around timeout states ?
by Matt Bryant 08 Jun '17

08 Jun '17

Been seeing a number of proxy timouts recently with errors such as ... timed out in state=4 timed out in state=2 Is there any doco around what state 2/4 actually means ... atm got auth_debug on to see if we can track further information down centos 7 x86_64 dovecot 2.2.19 rgds Matt

2 1

Dovecot login is slow
by Mitocariu Emilian 08 Jun '17

08 Jun '17

Hi, I have an Ubuntu 16.04 server with dovecot 2.2.22 configured as an imap server with an LDAP backend for authentication. This is the output of "dovecot -n": # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.0-77-generic x86_64 Ubuntu 16.04.2 LTS auth_debug_passwords = yes mail_gid = vmail mail_location = maildir:~/ mail_privileged_group = mail mail_uid = vmail 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 { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocols = imap lmtp service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl_cert = </path/to/my/cert ssl_key = </path/to/my/key userdb { args = /etc/dovecot/dovecot-ldap.conf.ext default_fields = home=/var/mail/vmail/%n driver = ldap } The problem i'm having is that when i try to login it takes more than 10 seconds, making my webmail very slow. For testing i login to imap like this "openssl s_client -connect localhost:993" and sometimes i get this message "* OK Waiting for authentication master process to respond..". I saw at other people, one of the problem was because they didn't disabled pam authentication when using another backend (like ldap or sql), but i already did that. Does anyone know what could cause such long login times and how to fix it?

2 1

Segmentation fault in imap_bodystructure_is_plain_7bit
by mihaiush 08 Jun '17

08 Jun '17

Hi, I have a lot of errors like this in my log: Fatal: master: service(imap): child 26049 killed with signal 11 (core dumped) Dovecot 2.2.18 build from sources ./configure --prefix=/opt/dovecot2 --with-mysql --with-sqlite --with-solr --with-ssl --disable-rpath --disable-static. Debian Wheezy 3.2.63-2 x86_64. Filesystem is ZFS. All the core files are similar: $ gdb /opt/dovecot2/libexec/dovecot/imap core GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html > This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /opt/dovecot2/libexec/dovecot/imap...done. [New LWP 11635] warning: Can't read pathname for load map: Input/output error. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/opt/dovecot2/libexec/dovecot/imap imap-postlogin'. Program terminated with signal 11, Segmentation fault. #0 imap_bodystructure_is_plain_7bit (part=part@entry=0x234cd50) at imap-bodystructure.c:458 458 if (data->content_subtype != NULL && (gdb) bt #0 imap_bodystructure_is_plain_7bit (part=part@entry=0x234cd50) at imap-bodystructure.c:458 #1 0x00007f920a0fbfaf in index_mail_body_parsed_cache_flags (mail=0x234be60) at index-mail.c:587 #2 index_mail_parse_body_finish (mail=mail@entry=0x234be60, field=field@entry=MAIL_CACHE_IMAP_BODYSTRUCTURE, success=success@entry=true) at index-mail.c:1007 #3 0x00007f920a0fc369 in index_mail_parse_body (mail=mail@entry=0x234be60, field=field@entry=MAIL_CACHE_IMAP_BODYSTRUCTURE) at index-mail.c:1081 #4 0x00007f920a0fc498 in index_mail_parse_bodystructure (mail=mail@entry=0x234be60, field=field@entry=MAIL_CACHE_IMAP_BODYSTRUCTURE) at index-mail.c:1222 #5 0x00007f920a0fcf1c in index_mail_get_special (_mail=_mail@entry=0x234be60, field=field@entry=MAIL_FETCH_IMAP_BODYSTRUCTURE, value_r=value_r@entry=0x7ffc1518fde8) at index-mail.c:1379 #6 0x00007f920a0b29cd in dbox_mail_get_special (_mail=_mail@entry=0x234be60, field=field@entry=MAIL_FETCH_IMAP_BODYSTRUCTURE, value_r=value_r@entry=0x7ffc1518fde8) at dbox-mail.c:229 #7 0x00007f920a0a83f0 in mdbox_mail_get_special (_mail=0x234be60, field=MAIL_FETCH_IMAP_BODYSTRUCTURE, value_r=0x7ffc1518fde8) at mdbox-mail.c:213 #8 0x00007f920a08f96d in mail_get_special (mail=<optimized out>, field=field@entry=MAIL_FETCH_IMAP_BODYSTRUCTURE, value_r=value_r@entry=0x7ffc1518fde8) at mail.c:317 #9 0x0000000000419a6a in fetch_bodystructure (ctx=0x232bbd8, mail=<optimized out>, context=<optimized out>) at imap-fetch.c:690 #10 0x0000000000419f9f in imap_fetch_more_int (ctx=ctx@entry=0x232bbd8, cancel=false) at imap-fetch.c:506 #11 0x000000000041af07 in imap_fetch_more (ctx=0x232bbd8, cmd=cmd@entry=0x232ba00) at imap-fetch.c:558 #12 0x000000000040f0c9 in cmd_fetch (cmd=0x232ba00) at cmd-fetch.c:286 #13 0x0000000000418aec in command_exec (cmd=cmd@entry=0x232ba00) at imap-commands.c:167 #14 0x0000000000417ad0 in client_command_input (cmd=cmd@entry=0x232ba00) at imap-client.c:814 #15 0x0000000000417b64 in client_command_input (cmd=0x232ba00) at imap-client.c:874 #16 0x0000000000417e45 in client_handle_next_command (remove_io_r=<synthetic pointer>, client=0x232ade0) at imap-client.c:912 #17 client_handle_input (client=client@entry=0x232ade0) at imap-client.c:924 #18 0x0000000000418212 in client_input (client=0x232ade0) at imap-client.c:966 #19 0x00007f9209df134b in io_loop_call_io (io=0x232b8f0) at ioloop.c:501 #20 0x00007f9209df1e5b in io_loop_handler_run_internal (ioloop=ioloop@entry=0x22ec790) at ioloop-epoll.c:220 #21 0x00007f9209df13d9 in io_loop_handler_run (ioloop=ioloop@entry=0x22ec790) at ioloop.c:548 #22 0x00007f9209df1458 in io_loop_run (ioloop=0x22ec790) at ioloop.c:525 #23 0x00007f9209d92993 in master_service_run (service=0x22ec620, callback=callback@entry=0x421140 <client_connected>) at master-service.c:581 #24 0x000000000040c60b in main (argc=2, argv=0x22ec390) at main.c:431 (gdb) q I wrote a patch which solved the problem but: - my C is absolutely basic, - dovecot is already at version 2.2.30, maybe problem was already fixed. Anyway I attached my patch, please have a look. Thanks.

1 0