- dovecot - dovecot.org

Re: dovecot (2.2.13) panic on imap-login from iphone se
by Andre Hoepner - i.based: Systemhaus GmbH + Co. KG 18 Sep '18

18 Sep '18

here is our config: (doveconf -n) # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.6.11-gentoo x86_64 Gentoo Base System release 2.2 auth_cache_size = 10 M auth_mechanisms = plain login default_client_limit = 1024 default_process_limit = 256 hostname = HOSTNAME imap_client_workarounds = delay-newmail tb-extra-mailbox-sep info_log_path = /var/log/dovecot.log listen = * mail_location = maildir:~/Maildir mail_plugins = quota acl zlib 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 duplicate namespace { list = yes location = maildir:/home/shared/Maildir:CONTROL=~/Maildir/control/shared:INDEX=~/Maildir/index/shared prefix = Shared separator = / subscriptions = no type = public } 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 = separator = / type = private } passdb { args = * driver = pam } passdb { driver = passwd } passdb { driver = shadow } plugin { acl = vfile autocreate = Trash autocreate2 = Junk autocreate3 = Sent autocreate4 = Drafts quota = maildir:User quota quota_rule = *:storage=3800M quota_rule2 = Trash:storage=+500M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=85%% quota-warning 85 %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = ADMIN-EMAIL protocols = imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } service imap-login { inet_listener imaps { ssl = yes } } service managesieve-login { inet_listener sieve { port = 4190 } } service quota-warning { executable = script /usr/bin/dovecot-quota-warning.sh user = dovecot } ssl_ca = </etc/ssl/ssl.pem ssl_cert = </etc/ssl/ssl.crt ssl_key = </etc/ssl/ssl.key ssl_protocols = !SSLv2 !SSLv3 userdb { driver = passwd } protocol lmtp { mail_fsync = optimized } protocol lda { mail_fsync = optimized mail_plugins = sieve quota } protocol imap { mail_plugins = quota acl zlib imap_quota imap_acl } ############## # doveadm user USERNAME field value uid 950 gid 501 home /home/USERNAME mail maildir:~/Maildir system_groups_user USERNAME ############### Hope this helps. Andre Am 18.09.2018 um 18:49 schrieb Aki Tuomi: > Please keep replies on list. Can you provide doveconf -n and output of > doveadm user victim ? > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: "Andre Hoepner - i.based: Systemhaus GmbH + Co. KG" > <a.hoepner(a)ibased.de> > Date: 18/09/2018 19:13 (GMT+02:00) > To: Aki Tuomi <aki.tuomi(a)dovecot.fi> > Subject: Re: dovecot (2.2.13) panic on imap-login from iphone se > > > Sorry. I think upgrade is not possible because it is a very outdated > gentoo installation and im not abe to compile without compiling the > whole source stack of glibc and all other dependencies. > > It is planned to replace the server in the next 8 weeks with a new > system, but this 8 weeks the server must do the work. > > Andre > > > Am 18.09.2018 um 17:09 schrieb Aki Tuomi: >> Can you upgrade to 2.2.36 or 2.3.2.1 and reproduce this issue? 2.2.13 is >> quite old. >> >> >> >> --- >> Aki Tuomi >> Dovecot oy >> >> -------- Original message -------- >> From: "Andre Hoepner - i.based: Systemhaus GmbH + Co. KG" >> <a.hoepner(a)ibased.de> >> Date: 18/09/2018 16:17 (GMT+02:00) >> To: dovecot(a)dovecot.org >> Subject: dovecot (2.2.13) panic on imap-login from iphone se >> >> >> Hi to all, >> >> we have trouble with one user account, when using imap-login with iphone >> se. The user can login and use the account from webmail (roundcube) and >> from thunderbird without any errors and without any restrictions. >> >> But if we use the account on an iphone se and try to use imap based >> emails, there comes the following error (look at the end of the mail). >> I have no idea, what for an error it is. Same account on an iphone 5 >> works without any trouble. >> >> We have delete the homedir of the user and also recreated the user with >> new uid and new password. Webmail and thunderbird are fine, but if we >> use the iphone se we got this error. >> >> Are there any known issues with this combination? >> Thanks for your help. >> >> best regardings >> Andre Hoepner >> >> ---8<---- >> # HOST = hostname of the system; USER = username that gets this error >> >> Sep 18 12:46:02 HOST dovecot: imap(USER): Panic: file mailbox-list.c: >> line 1125 >> (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, >> path, strlen(root_dir)) == 0) >> >> Sep 18 12:46:02 HOST dovecot: imap(USER): Error: Raw backtrace: >> /usr/lib64/dovecot/libdovecot.so.0(+0x6552e) [0x7f4333e0452e] >> -> /usr/lib64/dovecot/libdovecot.so.0(+0x65596) [0x7f4333e04596] >> -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f4333dc423e] >> -> >> > /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_list_try_mkdir_root+0x469) >> [0x7f43340d3a5a] >> -> >> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_list_mkdir_root+0x15) >> [0x7f43340d3ac0] >> -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x570cb) [0x7f43340c40cb] >> -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_set_deleted+0x11a) >> [0x7f43340c465c] >> -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x563d5) [0x7f43340c33d5] >> -> >> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_uidlist_sync_init+0x33) >> [0x7f43340c34f7] >> -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x517ac) [0x7f43340be7ac] >> -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x51c59) [0x7f43340bec59] >> -> >> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xb5) >> [0x7f43340bef35] >> -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x2b) >> [0x7f43340cc405] >> -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) >> [0x7f43340cc4f1] >> -> >> /usr/lib64/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x2f) >> [0x7f43340f1f6a] >> -> /usr/lib64/dovecot/lib01_acl_plugin.so(+0xdff9) [0x7f43335ffff9] >> -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) >> [0x7f43340cd36c] >> -> dovecot/imap(imap_status_get+0x5f) [0x41dc1d] >> -> dovecot/imap() [0x410cf9] >> -> dovecot/imap(cmd_list_full+0x49d) [0x411297] >> -> dovecot/imap(command_exec+0x37) [0x417f20] >> -> dovecot/imap() [0x4170c9] >> -> dovecot/imap() [0x417174] >> -> dovecot/imap(client_handle_input+0x106) [0x417400] >> -> dovecot/imap(client_input+0x72) [0x417768] >> -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x3f) > [0x7f4333e13536] >> -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd1) >> [0x7f4333e142e6] >> -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) >> [0x7f4333e13598] >> >> Sep 18 12:46:02 HOST dovecot: imap(USER): Fatal: master: service(imap): >> child 32253 >> killed with signal 6 (core dumps disabled) >> ---8<---- > > -- > > Sie möchten wissen, warum wir die Richtigen für Ihr > Unternehmen sind? Lesen Sie hier ... > http://www.11-gute-gruende.de > > > i.based: Systemhaus GmbH & Co. KG > Langenstrasse 38 > 18439 Stralsund > Deutschland > > http://www.ibased.de > a.hoepner(a)ibased.de > > fon: 03831-28944-0 > fax: 03831-28944-29 > > Registergericht: > HRA 2072 Amtsgericht Stralsund > > Geschäftsführung: > i.based: Systemhaus Verwaltungs GmbH > > Steuer-Nr: 082/187/38401 > USt.-ID: DE254322988 > > persönlich haftend: > i.based: Systemhaus Verwaltungs- > GmbH, Stralsund > HRB 7189 Amtsgericht Stralsund > > vertreten durch: > André Höpner, Mathias Waldeck > > https://www.linkedin.com/in/andre-hoepner/ > https://www.xing.com/hp/andre_hoepner -- Sie möchten wissen, warum wir die Richtigen für Ihr Unternehmen sind? Lesen Sie hier ... http://www.11-gute-gruende.de i.based: Systemhaus GmbH & Co. KG Langenstrasse 38 18439 Stralsund Deutschland http://www.ibased.de a.hoepner(a)ibased.de fon: 03831-28944-0 fax: 03831-28944-29 Registergericht: HRA 2072 Amtsgericht Stralsund Geschäftsführung: i.based: Systemhaus Verwaltungs GmbH Steuer-Nr: 082/187/38401 USt.-ID: DE254322988 persönlich haftend: i.based: Systemhaus Verwaltungs- GmbH, Stralsund HRB 7189 Amtsgericht Stralsund vertreten durch: André Höpner, Mathias Waldeck https://www.linkedin.com/in/andre-hoepner/ https://www.xing.com/hp/andre_hoepner

2 1

Re: dovecot (2.2.13) panic on imap-login from iphone se
by Aki Tuomi 18 Sep '18

18 Sep '18

Please keep replies on list. Can you provide doveconf -n and output of doveadm user victim ? ---Aki TuomiDovecot oy -------- Original message --------From: "Andre Hoepner - i.based: Systemhaus GmbH + Co. KG" <a.hoepner(a)ibased.de> Date: 18/09/2018 19:13 (GMT+02:00) To: Aki Tuomi <aki.tuomi(a)dovecot.fi> Subject: Re: dovecot (2.2.13) panic on imap-login from iphone se Sorry. I think upgrade is not possible because it is a very outdated gentoo installation and im not abe to compile without compiling the whole source stack of glibc and all other dependencies. It is planned to replace the server in the next 8 weeks with a new system, but this 8 weeks the server must do the work. Andre Am 18.09.2018 um 17:09 schrieb Aki Tuomi: > Can you upgrade to 2.2.36 or 2.3.2.1 and reproduce this issue? 2.2.13 is > quite old. > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: "Andre Hoepner - i.based: Systemhaus GmbH + Co. KG" > <a.hoepner(a)ibased.de> > Date: 18/09/2018 16:17 (GMT+02:00) > To: dovecot(a)dovecot.org > Subject: dovecot (2.2.13) panic on imap-login from iphone se > > > Hi to all, > > we have trouble with one user account, when using imap-login with iphone > se. The user can login and use the account from webmail (roundcube) and > from thunderbird without any errors and without any restrictions. > > But if we use the account on an iphone se and try to use imap based > emails, there comes the following error (look at the end of the mail). > I have no idea, what for an error it is. Same account on an iphone 5 > works without any trouble. > > We have delete the homedir of the user and also recreated the user with > new uid and new password. Webmail and thunderbird are fine, but if we > use the iphone se we got this error. > > Are there any known issues with this combination? > Thanks for your help. > > best regardings > Andre Hoepner > > ---8<---- > # HOST = hostname of the system; USER = username that gets this error > > Sep 18 12:46:02 HOST dovecot: imap(USER): Panic: file mailbox-list.c: > line 1125 > (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, > path, strlen(root_dir)) == 0) > > Sep 18 12:46:02 HOST dovecot: imap(USER): Error: Raw backtrace: > /usr/lib64/dovecot/libdovecot.so.0(+0x6552e) [0x7f4333e0452e] > -> /usr/lib64/dovecot/libdovecot.so.0(+0x65596) [0x7f4333e04596] > -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f4333dc423e] > -> > /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_list_try_mkdir_root+0x469) > [0x7f43340d3a5a] > -> > /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_list_mkdir_root+0x15) > [0x7f43340d3ac0] > -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x570cb) [0x7f43340c40cb] > -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_set_deleted+0x11a) > [0x7f43340c465c] > -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x563d5) [0x7f43340c33d5] > -> > /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_uidlist_sync_init+0x33) > [0x7f43340c34f7] > -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x517ac) [0x7f43340be7ac] > -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x51c59) [0x7f43340bec59] > -> > /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xb5) > [0x7f43340bef35] > -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x2b) > [0x7f43340cc405] > -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) > [0x7f43340cc4f1] > -> > /usr/lib64/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x2f) > [0x7f43340f1f6a] > -> /usr/lib64/dovecot/lib01_acl_plugin.so(+0xdff9) [0x7f43335ffff9] > -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) > [0x7f43340cd36c] > -> dovecot/imap(imap_status_get+0x5f) [0x41dc1d] > -> dovecot/imap() [0x410cf9] > -> dovecot/imap(cmd_list_full+0x49d) [0x411297] > -> dovecot/imap(command_exec+0x37) [0x417f20] > -> dovecot/imap() [0x4170c9] > -> dovecot/imap() [0x417174] > -> dovecot/imap(client_handle_input+0x106) [0x417400] > -> dovecot/imap(client_input+0x72) [0x417768] > -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x3f) [0x7f4333e13536] > -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd1) > [0x7f4333e142e6] > -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) > [0x7f4333e13598] > > Sep 18 12:46:02 HOST dovecot: imap(USER): Fatal: master: service(imap): > child 32253 > killed with signal 6 (core dumps disabled) > ---8<---- -- Sie möchten wissen, warum wir die Richtigen für Ihr Unternehmen sind? Lesen Sie hier ... http://www.11-gute-gruende.de i.based: Systemhaus GmbH & Co. KG Langenstrasse 38 18439 Stralsund Deutschland http://www.ibased.de a.hoepner(a)ibased.de fon: 03831-28944-0 fax: 03831-28944-29 Registergericht: HRA 2072 Amtsgericht Stralsund Geschäftsführung: i.based: Systemhaus Verwaltungs GmbH Steuer-Nr: 082/187/38401 USt.-ID: DE254322988 persönlich haftend: i.based: Systemhaus Verwaltungs- GmbH, Stralsund HRB 7189 Amtsgericht Stralsund vertreten durch: André Höpner, Mathias Waldeck https://www.linkedin.com/in/andre-hoepner/ https://www.xing.com/hp/andre_hoepner

1 0

dovecot (2.2.13) panic on imap-login from iphone se
by Andre Hoepner - i.based: Systemhaus GmbH + Co. KG 18 Sep '18

18 Sep '18

Hi to all, we have trouble with one user account, when using imap-login with iphone se. The user can login and use the account from webmail (roundcube) and from thunderbird without any errors and without any restrictions. But if we use the account on an iphone se and try to use imap based emails, there comes the following error (look at the end of the mail). I have no idea, what for an error it is. Same account on an iphone 5 works without any trouble. We have delete the homedir of the user and also recreated the user with new uid and new password. Webmail and thunderbird are fine, but if we use the iphone se we got this error. Are there any known issues with this combination? Thanks for your help. best regardings Andre Hoepner ---8<---- # HOST = hostname of the system; USER = username that gets this error Sep 18 12:46:02 HOST dovecot: imap(USER): Panic: file mailbox-list.c: line 1125 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) Sep 18 12:46:02 HOST dovecot: imap(USER): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x6552e) [0x7f4333e0452e] -> /usr/lib64/dovecot/libdovecot.so.0(+0x65596) [0x7f4333e04596] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f4333dc423e] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_list_try_mkdir_root+0x469) [0x7f43340d3a5a] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_list_mkdir_root+0x15) [0x7f43340d3ac0] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x570cb) [0x7f43340c40cb] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_set_deleted+0x11a) [0x7f43340c465c] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x563d5) [0x7f43340c33d5] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_uidlist_sync_init+0x33) [0x7f43340c34f7] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x517ac) [0x7f43340be7ac] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x51c59) [0x7f43340bec59] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xb5) [0x7f43340bef35] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x2b) [0x7f43340cc405] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x7f43340cc4f1] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x2f) [0x7f43340f1f6a] -> /usr/lib64/dovecot/lib01_acl_plugin.so(+0xdff9) [0x7f43335ffff9] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) [0x7f43340cd36c] -> dovecot/imap(imap_status_get+0x5f) [0x41dc1d] -> dovecot/imap() [0x410cf9] -> dovecot/imap(cmd_list_full+0x49d) [0x411297] -> dovecot/imap(command_exec+0x37) [0x417f20] -> dovecot/imap() [0x4170c9] -> dovecot/imap() [0x417174] -> dovecot/imap(client_handle_input+0x106) [0x417400] -> dovecot/imap(client_input+0x72) [0x417768] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x3f) [0x7f4333e13536] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd1) [0x7f4333e142e6] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) [0x7f4333e13598] Sep 18 12:46:02 HOST dovecot: imap(USER): Fatal: master: service(imap): child 32253 killed with signal 6 (core dumps disabled) ---8<----

2 1

Re: Auth process sometimes stop responding after upgrade
by Timo Sirainen 18 Sep '18

18 Sep '18

On 8 Sep 2018, at 15.18, Simone Lazzaris <simone.lazzaris(a)qcom.it> wrote: > > Timo, unfortunately the patch doesn't compile; I've moved the declaration of > "conn" one line up to make it work. Oops, I guess I was too much in a hurry to even compile it. Here's a new patch that compiles and passes our director CI tests.

4 9

Using both starttls and ssl in passdb on proxy results in timeouts
by Filias Heidt 18 Sep '18

18 Sep '18

Hi List, I have a dovecot which proxies to different backends depending on an entry in a mysql-database. The mysql-query sets ‚ssl‘ to ‚any-cert‘ and this works fine. But this causes me a problem: sieve-backends only support STARTTLS and if I set ‚ssl‘ to ‚any-cert‘ (or yes), it will attempt a TLS-connection to the sieve-backends, which fails. My attempt was to alter the query to include %{real_lport} and return ‚ssl=no‘ and ‚starttls=any-cert‘ if the port matches the sieve-port. It works as expected in that it returns the correct values and proxies to the correct backend. However it seems that TLS is no longer working and I get timeouts from the backends. Debug: client passdb out: OK 1 user=someuser(a)example.com proxy proxy_nopipelining=y host=backend1.example.com nodelay=y nologin starttls=no ssl=any-cert hostip=so.me.i.p pass=<hidden> results in: Sep 17 11:08:47 imapproxy1 dovecot: imap-login: Error: proxy(someuser(a)example.com): Login for so.me.i.p:993 timed out in state=/none (after 30 secs, local=lo.cal.i.p:60524): user=<someuser(a)example.com>, method=PLAIN, rip=re.mo.te.ip, lip=lo.cal.i.p, TLS, session=<OySXgw12auwgARYIAAYABwAAAAAAAwAU> My query looks like this: password_query = SELECT host from proxy_domain, NULL as password, 'y' as nopassword, 'y' as proxy, NULL as destuser, 'y' as proxy_nopipelining, 'y' as nodelay, 'y' as nologin, IF(%{real_lport}=4190, 'any-cert', 'no') as 'starttls', IF(%{real_lport}<>4190, 'any-cert', 'no') as 'ssl‘; As soon as I remove the starttls-part and the passdb only returns ssl=any-cert (without starttls=no) it works flawlessly. Is it possible that I am attacking the problem the wrong way? Or is it not possible to set both starttls and ssl to some values in passdb and enable/disable them as needed? Thanks for any input :) Cheers, Filias

2 2

How to send mail to mailbox with disabled domain?
by Kai Schaetzl 17 Sep '18

17 Sep '18

Given the following: mailboxes: user1(a)example1.com user2(a)example1.com user3(a)example1.com etc. aliases: whatever(a)example1.com -> user1(a)example1.com whatever(a)example2.com -> user1(a)example1.com whatever(a)example3.com -> user1(a)example1.com Now the problem: example1.com MX goes elsewhere (doesn't point to this server anymore). Domains example2.com and example3.com still point to that server and should be able to accept mail. I have to disable mail acceptance for example1.com. If not, mail sent *from* that server (e.g. from a web form) to that domain will not leave the server. However, if I disable example1.com for mail dovecot lmtp will not deliver mail to this mail box anymore, although the mailbox still exists. How can I solve this? Is there a way of solving this, but keeping the domain example1.com in the name for these mailboxes? Or is there a way to tell dovecot to ignore domains for mailbox names? e.g. deliver to "user1"? (All user localparts are unique.) Thanks for any hints. Kai

4 6

Re: Proxy secured incoming POP3/IMAP4 to unsecure backend?
by Alexander Chekalin 17 Sep '18

17 Sep '18

Thank you! Ok, so I can omit ssl=no and startssl=no, and this results in default settings for ssl which is 'off'? Or the defaults are 'on' anyway? Can I somehow specify ports on remote hosts that proxy will use to connect to? Like (just image): 'proxy host_imap=10.1.1.1:143 host_pop=10.1.1.1:110' or somehow? On Mon, Sep 17, 2018 at 4:33 PM Aki Tuomi <aki.tuomi(a)dovecot.fi> wrote: > Due to certain design issues, the ssl=no is actually same as ssl=yes, same > goes for starttls=no. So there is no support actually for "ssl=no" at this > moment. > > Aki > > > On 17 September 2018 at 15:32 Alexander Chekalin < > alexander.chekalin(a)gmail.com> wrote: > > > > > > Surely. > > > > Here it is: > > > > # doveadm auth user(a)domain.com > > Password: > > passdb: chekalin_krg(a)ascon.ru auth succeeded > > extra fields: > > user=user(a)domain.com > > proxy > > host=10.10.14.131 > > ssl=no > > startssl=no > > source_ip=10.10.14.2 > > proxy > > proxy > > pass=password > > > > Two "proxy" are from two "proxy" and "proxy=yes" settings passed from > > passdb. > > > > On Mon, Sep 17, 2018 at 3:03 PM Aki Tuomi <aki.tuomi(a)dovecot.fi> wrote: > > > > > Can you provide output of > > > > > > doveadm auth test some-user > > > Aki > > > > > > On 17.09.2018 14:58, Alexander Chekalin wrote: > > > > > > Dear Aki, > > > > > > we keep our users in LDAP so I when I even return 'proxy > host=backend_ip > > > tls=no' it won't use non-TLS connection. The same is when I remove > 'tls=no' > > > part. May there be any extra things I need to pass when I use LDAP? > > > > > > On Mon, Sep 17, 2018 at 2:07 PM Aki Tuomi <aki.tuomi(a)dovecot.fi> > wrote: > > > > > >> > > >> > > >> On 17.09.2018 13:59, Alexander Chekalin wrote: > > >> > Hi, > > >> > > > >> > I try to set up dovecot as a proxy server, to proxy requests to > > >> > several dovecot-based backend servers. I wand external clients who > > >> > connects to this proxy Dovecot to use TLS (this is easy to set up) > > >> > while want to have unsecured (plain IMAP/POP) connections to > backends. > > >> > > > >> > You see, links to backends are over LAN so no TLS needed, and these > > >> > backends are poor old machines (with old Docecots like 2.0.6) this > is > > >> > why I don't want to use TLS to acces backends. > > >> > > > >> > But as I did the test setup I can see proxy Dovecot uses TLS to > > >> > connect to backends. Is there any way I can specify this aspect of > > >> > Dovecot proxy? > > >> > > > >> > Please advice! > > >> > > > >> > Yours, > > >> > Alexander > > >> > > >> Dovecot does not use TLS/SSL when connecting to a backend server by > > >> default, you are probably specifying this in your proxy config or > > >> password database. > > >> > > >> Aki > > >> > > > > > > >

2 5

Proxy secured incoming POP3/IMAP4 to unsecure backend?
by Alexander Chekalin 17 Sep '18

17 Sep '18

Hi, I try to set up dovecot as a proxy server, to proxy requests to several dovecot-based backend servers. I wand external clients who connects to this proxy Dovecot to use TLS (this is easy to set up) while want to have unsecured (plain IMAP/POP) connections to backends. You see, links to backends are over LAN so no TLS needed, and these backends are poor old machines (with old Docecots like 2.0.6) this is why I don't want to use TLS to acces backends. But as I did the test setup I can see proxy Dovecot uses TLS to connect to backends. Is there any way I can specify this aspect of Dovecot proxy? Please advice! Yours, Alexander

3 2

Problem with envelope from in Pigeonhole after upgrade
by David Dodd 17 Sep '18

17 Sep '18

On our FreeBSD 11.2 servers, we recently upgraded from: dovecot2-2.2.26.0_1 dovecot-pigeonhole-0.4.16_1 to: dovecot-2.3.2.1 dovecot-pigeonhole-0.5.2_3 Prior to the upgrade the envelope sender was as expected. After the upgrade, the envelope sender for a user with a sieve script configured is now being set to: >From MAILER-DAEMON Tue Sep 04 13:31:39 2018 The same user without a sieve script in place gets: >From someone(a)gmail.com Tue Sep 04 11:06:04 2018 This happens when manually testing by directly executing: /usr/local/libexec/dovecot/dovecot-lda -d dgdtst -f someone(a)gmail.com It happens with an empty sieve script i.e. just using the implicit keep functionality. I have groped around looking for a configuration setting that might fix the behaviour but nothing I have tried helps. Can anyone suggest what to set to correct the problem ? -- Dave

2 7

Quotas not working with roundcube
by Mik J 17 Sep '18

17 Sep '18

Hello, I'm trying to have quotas working with roundcube. When I'm logged into roundcube I see 0% quota which seems to correspond to disabled. However I did everything that I could to enable quotas https://wiki.dovecot.org/Quota # doveconf -n auth_mechanisms = cram-md5 loginauth_verbose = yes debug_log_path = /tmp/dovecot.log first_valid_uid = 1000 log_path = /var/log/dovecot.log mail_gid = vmail mail_location = maildir:/home/mail/%d/%n/Maildir mail_plugins = notify replication quota mail_uid = vmail mbox_write_locks = fcntl mmap_disable = yes 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 = bsdauth } passdb { args = /etc/dovecot/dovecot.passwd driver = passwd-file } plugin { quota_grace = 10%% quota_rule = *:storage=2G quota_rule2 = Trash:storage=+200M quota_rule3 = SPAM:ignore quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u } ssl_ca = /etc/ssl/certs/CA_Intermed_Lets_Encrypt.crt ssl_cert = </etc/ssl/certs/imap.mydomain.org.crt ssl_key = # hidden, use -P to show it ssl_key_password = # hidden, use -P to show it userdb { driver = passwd } userdb { driver = static } protocol lda { mail_plugins = notify replication quota } protocol imap { mail_plugins = notify replication quota imap_quota }

3 5

Dsync deleting mailboxes due to duplicate UIDs
by Andreas Thienemann 16 Sep '18

16 Sep '18

Hi, I am attempting to migrate a mailspool from a cyrus server to a dovecot server using the dsync backup approach as described in the wiki at <https://wiki.dovecot.org/Migration/Dsync>. The first attempt works great. Everything copies over and a quick glance over the spool looks good. Running doveadm backup again though results in the following error: dsync(eggs): Warning: Deleting mailbox 'INBOX.MailRestore': UID=39 already exists locally for a different mail: Headers hashes don't match (18d567fc7e258a67e47b629c8bb16500 vs 230354b2d5cad21ebbb4a7440b977adb) As promised, the folder MailRestore is gone after dsync finishes. Running doveadm backup again for the third time copies the folder again. Running it a fourth time gives the same error and the folder is gone. Trying to figure this out I initially had a few mails where the header hashes were 68b329da9893e34099c7d8ad5cb9c940, the md5sum of an empty string. Turns out that the source mailspool had a few broken emails and cleaning these out fixed most my issues. But in this case, I am stumped. UID 39 on the server is a valid mail with correct headers and everything. Is there a good way of identifying the two mails that seem to clash? I had a quick look at the dovecot code but did not see how the header_stream gets hashed into the hdr_hash used for comparing mails. Thanks, Andreas

3 5

dovecot_deleted_to_trash no longer compiles with dovecot 2.3.2.1
by Robert S 16 Sep '18

16 Sep '18

I have just upgraded to the latest version of dovecot (Gentoo amd64). When I try to compile the dovecot_deleted_to_trash plugin it won't compile. Is this plugin going to be updated (from https://github.com/lexbrugman/dovecot_deleted_to_trash - same error from https://github.com/NethServer/dovecot-deleted-to-trash)? # make cc \ -fPIC -shared -Wall \ -I/usr/include/dovecot \ -I/usr/include/dovecot/src \ -I/usr/include/dovecot/src/lib \ -I/usr/include/dovecot/src/lib-storage \ -I/usr/include/dovecot/src/lib-mail \ -I/usr/include/dovecot/src/lib-imap \ -I/usr/include/dovecot/src/lib-index \ -DHAVE_CONFIG_H \ src/deleted-to-trash-plugin.c -o lib_deleted_to_trash_plugin.so src/deleted-to-trash-plugin.c: In function ‘copy_deleted_mail_to_trash’: src/deleted-to-trash-plugin.c:117:16: error: too few arguments to function ‘mail box_transaction_begin’ dest_trans = mailbox_transaction_begin(trash_box, MAILBOX_TRANSACTION_FLAG_EX TERNAL); ^~~~~~~~~~~~~~~~~~~~~~~~~ In file included from /usr/include/dovecot/mail-storage-private.h:7:0, from src/deleted-to-trash-plugin.h:5, from src/deleted-to-trash-plugin.c:4: /usr/include/dovecot/mail-storage.h:656:1: note: declared here mailbox_transaction_begin(struct mailbox *box, ^~~~~~~~~~~~~~~~~~~~~~~~~ make: *** [Makefile:32: lib_deleted_to_trash_plugin.so] Error 1 Some further info: # dovecot -n # 2.3.2.1 (0719df592): /etc/dovecot/dovecot.conf # OS: Linux 4.14.8-gentoo-r1 x86_64 Gentoo Base System release 2.4.1 # Hostname: basement-vm.schmidli.com.au doveconf: Warning: please set ssl_dh=</etc/dovecot/dh.pem doveconf: Warning: You can generate it with: dd if=/var/lib/dovecot/ssl-parameters.dat bs=1 skip=88 | openssl dhparam -inform der > /etc/dovecot/dh.pem dict { expire = db:/var/lib/dovecot/expire.db } disable_plaintext_auth = no listen = * mail_location = maildir:~/.maildir mail_plugins = deleted_to_trash mailbox_alias 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 = * driver = pam } plugin { deleted_to_trash_folder = Trash expire = Trash 7 Spam 30 expire_dict = proxy::expire

1 0

Re: auth_policy in a non-authenticating proxy chain
by Peter Mogensen 15 Sep '18

15 Sep '18

On 09/15/2018 10:41 AM, Aki Tuomi wrote: > Point of sending the success ones is to maintain whitelist as well as > blacklist so you know which ones you should not tarpit anymore. We > know it does scale as we have very large deployments using the whole > three request per login model. > > "Success" in a proxy which is not it self authenticating is only whether it know where to proxy the requested username to. I'm not sure whether this would be input to a whitelist. I'm not doubting that 3 req/login scales. /Peter

2 1

auth_policy in a non-authenticating proxy chain
by Peter Mogensen 15 Sep '18

15 Sep '18

Hi, I was looking into the new Authentication Policy feature: https://wiki2.dovecot.org/Authentication/Policy I had kinda hoped that I would be able to enfore this in a proxy running in front of several backends. This proxy does not authenticate. It use "nopassword". But I realize that the "succes" reported in the final authpolicy req. (command=report) is not what is actaully happening on the IMAP protocol level, but rather the result of the passdb chain in the proxy. (I should probably have predicted this, it's kinda reasonable). However... since the proxy use "nopassword", ALL passdb lookups result in "success", so the proxy will never report an authentication failure to the authpolicy server. This, of course, forces me to do the authpolicy check on the backend with a shared state, but It would still have been nice to have the proxy being able to do the first "command=allow" req. and reject attemps already there even though the backend does "command=report". /Peter

3 4

encryption issue in outlook 2016
by ChandranManikandan 14 Sep '18

14 Sep '18

Hi Friends, Am facing the serious issue in outlook 2016. When i tried to configure the email in outlook 2016 it's asking encrypted connection and checked automatically and if not available then it showing unencrypted. but finally unable to configure the email account in outlook 2016 and not permitted. Do i need to update any in the server. Am using COS 6 32 and 64 bit servers with qmailtoaster + dovecot 2.2.7. Currently configured in outlook 2010 it's working without any issue. And always showing in outlook 2010 when i open the account. Do you want to continue yes or no for the certification. Because i have configured in advanced selected Auto in outlook 2010. If i select none it was not working the email. Anyone facing the same issue. How do i rectify it in outlook 2016 and how can i stop the certificate warning message in outlook. If possible to use without encryption and what's the configuration. Please advice and let me know the process. Am seriously cannot access the email from outlook. I have attached the message while open outlook. If i click yes then it will open Is the certificate expired. How do renew it or reload it with the fresh certificate. -- *Thanks & Best Regards,Manikandan.C*

4 4

Occasional crash in db-auth.c (Valgrind: Invalid read of size 4 et al.), Dovecot 2.2.27+
by Jonas Wielicki 14 Sep '18

14 Sep '18

Dear list, We are encountering troubles with dovecot using LDAP userdbs on Debian stretch (but if I’m reading valgrind correctly, we can reproduce this with vanilla dovecot master). Minimal reproducer below. While testing an upgrade to Debian stretch (dovecot-core=1:2.2.27-3+deb9u1), auth-worker has stopped working. We are using two LDAP user databases; one which is iterable, and one which is not (for reasons; I think this is not relevant; if it is, we’re happy to elaborate). The issue seems to be present in any LDAP userdb iteration handling, but it only seems to cause a crash in certain conditions which seem to be reproducibly caused by our setup for some reason. We’re seeing one of two errors. Variant A: Jan 27 13:40:05 up2 dovecot: auth-worker: Error: *** Error in `dovecot/auth': free(): corrupted unsorted chunks: 0x000056553f0fcfa0 *** Jan 27 13:40:05 up2 dovecot: auth-worker: Error: ======= Backtrace: ========= Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /lib/x86_64-linux-gnu/ libc.so.6(+0x70bcb)[0x7f78426adbcb] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /lib/x86_64-linux-gnu/ libc.so.6(+0x76f96)[0x7f78426b3f96] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /lib/x86_64-linux-gnu/ libc.so.6(+0x777de)[0x7f78426b47de] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /usr/lib/dovecot/modules/ auth/libauthdb_ldap.so(+0x5bde)[0x7f7842008bde] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /usr/lib/dovecot/ libdovecot.so.0(io_loop_call_io+0x52)[0x7f78430cfdd2] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /usr/lib/dovecot/ libdovecot.so.0(io_loop_handler_run_internal+0x109)[0x7f78430d1409] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /usr/lib/dovecot/ libdovecot.so.0(io_loop_handler_run+0x3c)[0x7f78430cfe6c] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /usr/lib/dovecot/ libdovecot.so.0(io_loop_run+0x38)[0x7f78430d0018] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /usr/lib/dovecot/ libdovecot.so.0(master_service_run+0x13)[0x7f7843057e93] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: dovecot/auth(main+0x398) [0x56553da45f98] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /lib/x86_64-linux-gnu/ libc.so.6(__libc_start_main+0xf1)[0x7f784265d2b1] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: dovecot/auth(_start+0x2a) [0x56553da461aa] Variant B: Jan 27 13:06:56 up2 dovecot: auth-worker(27495): Panic: file db-ldap.c: line 840 (db_ldap_result_unref): assertion failed: (res->refcount > 0) Jan 27 13:06:56 up2 dovecot: auth-worker(27495): Error: Raw backtrace: /usr/ lib/dovecot/libdovecot.so.0(+0x95272) [0x7f027a4fc272] -> /usr/lib/dovecot/ libdovecot.so.0(+0x9536d) [0x7f027a4fc36d] -> /usr/lib/dovecot/libdovecot.so. 0(i_fatal+0) [0x7f027a492951] -> /usr/lib/dovecot/modules/auth/ libauthdb_ldap.so(+0x3868) [0x7f0279447868] -> /usr/lib/dovecot/modules/auth/ libauthdb_ldap.so(+0x5d7c) [0x7f0279449d7c] -> /usr/lib/dovecot/libdovecot.so. 0(io_loop_call_io+0x52) [0x7f027a510dd2] -> /usr/lib/dovecot/libdovecot.so. 0(io_loop_handler_run_internal+0x109) [0x7f027a512409] -> /usr/lib/dovecot/ libdovecot.so.0(io_loop_handler_run+0x3c) [0x7f027a510e6c] -> /usr/lib/ dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f027a511018] -> /usr/lib/ dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f027a498e93] -> dovecot/ auth(main+0x398) [0x55b981cd2f98] -> /lib/x86_64-linux-gnu/libc.so. 6(__libc_start_main+0xf1) [0x7f0279a9e2b1] -> dovecot/auth(_start+0x2a) [0x55b981cd31aa] When running auth-worker within valgrind, we get more information (valgrind extract from mail.log attached for two versions of dovecot). We have attached mail.log contents for the respective valgrind runs. This seems to affect at least 2.2.27 onwards. We can reproduce the crash with our production data 100% of the time. The valgrind error is present even with very minimal setups (see below). Unfortunately, I haven’t been able so far to create an LDAP database which produces the crash as reliable as our production database does (which we cannot share for obvious reasons). Minimal Reproducer of Valgrind error: - Install dovecot 2.2.27 from debian stretch, or compile from master. - Install valgrind - In conf.d/10-auth.conf, disable auth-system.conf.ext - In conf.d/10-auth.conf, enable auth-ldap.conf.ext - Set contents of dovecot-ldap.conf.ext to: hosts = localhost base = dc=nodomain - In conf.d/10-master.conf, in section "service auth-worker", set executable = /usr/bin/valgrind /usr/lib/dovecot/auth -w (path may differ on your system) - Install an LDAP server with a database for dc=nodomain; this is trivial to do with debian: Simply install slapd and systemctl start slapd. - Start dovecot - Run doveadm user '*' - You should find the error in the mail.log. I hope this is somehow useful to fix our crash issue. We’ll be happy to provide more information as needed. kind regards, Jonas

4 4

Status of SMTPUTF8?
by Noah Tilton 14 Sep '18

14 Sep '18

I was wondering whether there is a roadmap for adding SMTPUTF8 support to Dovecot? My delivery pattern is Postfix -> Dovecot LMTP and it is choking on utf8 messages. I might be able to volunteer some of my time as a developer. Another thread about this seemed to go unanswered: http://dovecot.org/list/dovecot/2016-September/105474.html http://unix.stackexchange.com/questions/320091/configure-postfix-and-doveco… -Noah

4 3

LMTP tcp listener with auth?
by Andreas Thienemann 14 Sep '18

14 Sep '18

I am wondering if it's possible to have a tcp listener for LMTP do authentication and not accept any unauthenticated mail. My configuration looks like the following: service lmtp { inet_listener lmtp { address = 192.168.0.1 127.0.0.1 port = 24 } } This gives me a network reachable lmtp socket, but of course no autentication. When reading the docs, it seems though that only userdb lookup and no actual authentication is supported? Is that understanding correct? cheers, Andreas

4 3

Server certificate verification error with Dovecot 2.3.2.1
by Robert Gill 13 Sep '18

13 Sep '18

I'm attempting to upgrade my Dovecot installation to 2.3.2.1. My SSL certificate authority provides a bundle containing their CA, plus intermediate CAs, which I configure using the 'ssl_ca' option. The comments in the configuration file say to only set this when you're requiring client certificates, which I'm not, but fetchmail complains with a "Server certificate verification error, Broken certificate chain" error if that setting is not set. This works fine with Dovecot 2.2.34. After upgrading to 2.3.2.1, fetchmail throws that error whether 'ssl_ca' is set or not. Dovecot 2.3.2.1 reports the error SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca: SSL alert number 48 in the logs when attempting the TLS handshake. The permissions on the CA bundle haven't changed and should still be readable by Dovecot. I'm running Gentoo Linux on x86_64 and mail is stored on an ext4 file system. I'm attaching my config files for both Dovecot 2.2.34 and Dovecot 2.3.2.1.

3 3

dovecot + centos 7 + internal ca + hostname change
by Matt Bryant 13 Sep '18

13 Sep '18

Not sure if this is dovecot or not but can find very little ie no info around on this ... and added the pem file into /etc/pki/ca-trust/source/anchors and run udpate-ca-trust .. all works ok .. (this is on centos 7 btw) So wanted to change the hostname away from ip-x-x-x-x to something a little bit more descriptive .. but then kaboom .. doesnt work any more and the following errors are seen. Have created and internal CA for domain and added it to Sep 13 10:42:04 ip-10-0-40-230 dovecot: master: Dovecot v2.2.33.2 (d6601f4ec) starting up for imap, pop3, lmtp, sieve (core dumps disabled) Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'attr->pValue != NULL' not true at attrs_build Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'lexer->tok.field.name && lexer->tok.field.value' not true at p11_lexer_next Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'attrs != NULL' not true at attrs_build Sep 13 10:42:04 ip-10-0-40-230 dovecot: message repeated 16 times: [ auth: Error: p11-kit: 'attrs != NULL' not true at attrs_build] Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'new_memory != NULL' not true at maybe_expand_array Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at p11_array_push Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at sink_object Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'attrs != NULL' not true at attrs_build Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'new_memory != NULL' not true at maybe_expand_array Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at p11_array_push Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at sink_object ... ... Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'new_memory != NULL' not true at maybe_expand_array Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at p11_array_push Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at sink_object Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'attr->pValue != NULL' not true at attrs_build Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'new_memory != NULL' not true at maybe_expand_array Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at p11_array_push Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at sink_object Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: no CKA_CLASS attribute found Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: couldn't load file into objects: /usr/share/pki/ca-trust-source/ca-bundle.trust.p11-kit Sep 13 10:42:05 ip-10-0-40-230 dovecot: auth-worker: Error: p11-kit: 'attrs != NULL' not true at attrs_build Sep 13 10:42:05 ip-10-0-40-230 dovecot: auth-worker: Fatal: master: service(auth-worker): child 14389 killed with signal 11 (core dumps disabled) Sep 13 10:42:05 ip-10-0-40-230 dovecot: auth-worker: Error: p11-kit: 'attrs != NULL' not true at attrs_build Sep 13 10:42:05 ip-10-0-40-230 dovecot: auth-worker: Fatal: master: service(auth-worker): child 14391 killed with signal 11 (core dumps disabled) Sep 13 10:42:05 ip-10-0-40-230 dovecot: auth-worker: Error: p11-kit: 'attrs != NULL' not true at attrs_build Sep 13 10:42:05 ip-10-0-40-230 dovecot: auth-worker: Fatal: master: service(auth-worker): child 14393 killed with signal 11 (core dumps disabled) why would a hostname change make any difference here .. the certs specified in dovecot config are all complete in their chain so not sure what its trying to do ... set hostname back to original works find .. so something is obviously tied or keyed to hostname though cant find anything specific anyone seen anything like this at all ?? rgds Matt

1 1

Re: make check (pigeonhole)
by Eric Broch 12 Sep '18

12 Sep '18

Must be non root user as well On 9/12/2018 1:05 PM, Aki Tuomi wrote: > Ok. We have that fix as well but for other reasons. Good to know this. > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Eric Broch <ebroch(a)whitehorsetc.com> > Date: 12/09/2018 21:36 (GMT+02:00) > To: Aki Tuomi <aki.tuomi(a)dovecot.fi>, dovecot(a)dovecot.org > Subject: Re: make check (pigeonhole) > > Hi Aki, > > I needed this patch > <https://src.fedoraproject.org/cgit/rpms/dovecot.git/tree/dovecot-2.3.0.1-li…> > (fedora): > > |diff -up dovecot-2.3.0.1/src/auth/mycrypt.c.libxcrypt > dovecot-2.3.0.1/src/auth/mycrypt.c --- > dovecot-2.3.0.1/src/auth/mycrypt.c.libxcrypt 2018-02-28 > 15:28:58.000000000 +0100 +++ dovecot-2.3.0.1/src/auth/mycrypt.c > 2018-03-27 10:57:38.447769201 +0200 @@ -14,6 +14,7 @@ # define _XPG6 > /* Some Solaris versions require this, some break with this */ #endif > #include <unistd.h> +#include <crypt.h> #include "mycrypt.h" All works > well now. Thanks for your help Eric | > > On 9/12/2018 12:35 AM, Aki Tuomi wrote: >> >> I tried reproducing your problem and I only can make it happen if I >> run the test suite as root, which is not supported. >> >> Aki >> >> >> On 12.09.2018 06:49, Eric Broch wrote: >>> >>> I'll give those a look and make change accordingly. >>> >>> >>> On 9/11/2018 9:26 PM, Aki Tuomi wrote: >>>> You know we have rpm packages for 2.3.2.1 available at >>>> https://repo.dovecot.org if you are in a hurry? >>>> >>>> >>>> >>>> --- >>>> Aki Tuomi >>>> Dovecot oy >>>> >>>> -------- Original message -------- >>>> From: Eric Broch <ebroch(a)whitehorsetc.com> >>>> Date: 12/09/2018 00:35 (GMT+02:00) >>>> To: dovecot(a)dovecot.org >>>> Subject: Re: make check (pigeonhole) >>>> >>>> Any news on this error on CentOS 7 ? >>>> >>>> Help! >>>> >>>> >>>> On 9/10/2018 9:32 AM, Eric Broch wrote: >>>>> >>>>> I attempted as non-root user and got the exact same error. >>>>> >>>>> >>>>> On 9/10/2018 9:10 AM, Aki Tuomi wrote: >>>>>> Have you attempted this as non-root user? >>>>>> >>>>>> >>>>>> >>>>>> --- >>>>>> Aki Tuomi >>>>>> Dovecot oy >>>>> >>>>> -- >>>>> Eric Broch >>>>> White Horse Technical Consulting (WHTC) >>>> >>>> -- >>>> Eric Broch >>>> White Horse Technical Consulting (WHTC) >>> >>> -- >>> Eric Broch >>> White Horse Technical Consulting (WHTC) >> > > -- > Eric Broch > White Horse Technical Consulting (WHTC) -- Eric Broch White Horse Technical Consulting (WHTC)

1 0

Re: make check (pigeonhole)
by Eric Broch 12 Sep '18

12 Sep '18

I'll give those a look and make change accordingly. On 9/11/2018 9:26 PM, Aki Tuomi wrote: > You know we have rpm packages for 2.3.2.1 available at > https://repo.dovecot.org if you are in a hurry? > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Eric Broch <ebroch(a)whitehorsetc.com> > Date: 12/09/2018 00:35 (GMT+02:00) > To: dovecot(a)dovecot.org > Subject: Re: make check (pigeonhole) > > Any news on this error on CentOS 7 ? > > Help! > > > On 9/10/2018 9:32 AM, Eric Broch wrote: >> >> I attempted as non-root user and got the exact same error. >> >> >> On 9/10/2018 9:10 AM, Aki Tuomi wrote: >>> Have you attempted this as non-root user? >>> >>> >>> >>> --- >>> Aki Tuomi >>> Dovecot oy >> >> -- >> Eric Broch >> White Horse Technical Consulting (WHTC) > > -- > Eric Broch > White Horse Technical Consulting (WHTC) -- Eric Broch White Horse Technical Consulting (WHTC)

2 3

Adding namespace alias_for causes index resync?
by Tom Sommer 12 Sep '18

12 Sep '18

I just added a new namespace-alias with alias_for. Apparently this causes all mailbox indexes to be resynced? Is this intentional and/or is there some way to avoid this? My NFS storage pretty much kills its elf when hundreds of thausands of users needs to resync indexes :) Thanks -- Tom

1 1

Re: LMTP tcp listener with auth?
by Andreas Thienemann 12 Sep '18

12 Sep '18

Hi Stephan, On Wed, 12 Sep 2018, Stephan Bosch wrote: > LMTP currently does not support AUTH. Bummer. Thought so. > What is your use case? Most people hide LMTP behind a firewall, or don't > expose it through TCP/IP in the first place. The port is currently only available to a few trusted machines, but having auth available would have been a nice benefit in case the firewall gets misconfigured. Cyrus for example will expose the LMTP port via TCP if configured, but expects valid user credentials. The larger use-case is a migration from cyrus to dovecot. As it's not just the MDA but also the MTA installation that is being migrated I need a way to deliver mail from the old MTA to the new MDA. LMTP comes in handy. https://github.com/ixs/lmtp_proxy/blob/master/README.md#minmal-downtime-mig… has a rough invocation of the steps needed for that. As I said, LMTP auth isn't critical for this, but would have been a nice addition. cheers, Andreas

1 0

Letsencrypt certificate for repo.dovecot.org expired May 14th..
by B. Reino 12 Sep '18

12 Sep '18

Dear all, Just in case you've missed it, the certificate for repo.dovecot.org just expired yesterday. This causes errors in e.g. apt-get update. Thanks in advance for fixing it, -- B. Reino

2 6