- dovecot - dovecot.org

Re: Using dovecot with RoundCubeMail - where is the information for new mail in (blue coloured) directories?
by Scott Ruckh 01 Jan '21

01 Jan '21

On 2020-12-20 17:37, Philip Rhoades wrote: > @lbutlr, > > > On 2020-12-21 00:43, @lbutlr wrote: >> On 20 Dec 2020, at 04:05, Philip Rhoades <phil(a)pricom.com.au> wrote: >>> I guess that is what it seems to look like to me as well - but what >>> does that mean for what I am trying to do? - ie reset the blue folder >>> highlight arbitrarily? >> >> Sound like the Roundcube style choices are outside th purview of >> dovecot. > > > Hmm . . the first response I got here was that it was definitely an > IMAP thing . . I think he was unclear about the actual problem . . > > I will try the RCM forum . . > > Thanks, > > P. I am not sure I have understood this thread completely, but I am running dovecot/RoundCube. If a folder has new messages, then it has a badge that is dark blue (with the theme I am using) with the number of un-read messages. Otherwise it has a badge that is light-blue to indicate un-read messages only. Folders with no badges have zero un-read messages. So there is definitely a distinction for "new" messages.

2 1

migration from 2.0.16
by Barbara M. 01 Jan '21

01 Jan '21

I have an old server with CentOS 6.x and dovecot 2.0.16 (postfix-2.6.6 and roundcube), that was an update from a 1.x many years ago ... Users in /etc/passwd Mailbox format mbox some filtering via procmail About 5.000 users, 1 TB data (/var/mail + /home/users) Obviously I am searching for a smooth upgrade path (with no or minimal downtime and users problems) ;-) Until few days ago my idea was a CentOS 8.x new box with the standard default packages (dovecot-2.3.8, postfix-3.3, ...). Now this can be reconsidered. I suppose there will be a RockyLinux or something equivalent but if there is a good reason I can consider Debian or other OS if they have a decent EOL or some advantages. Anyway, the more relevant problem at the moment is collect info for the best approch to have a smooth dovecot upgrade. My dream is the possibility to configure a new server and rsync the data (/var/mail + /home/users), and, when the tests are satisfiable do the final sync and swap the IP, but I suppose deleting the .imap folders isn't a simple complete solution to compatibility problems. Any hints, links, experiences are appreciated. Thanks, B.

6 9

Initial Replication
by David Morsberger 01 Jan '21

01 Jan '21

I searched the archives and do not see a question/answer for this. Should I perform a set of ordered steps after setting up replication? I have setup dovecot on both ends with identical config except for the remote hostname. Main concern is the existing server gets replicated to the new server. I want nothing from new server replicated to the old server. Risking "Trial and error" and "crossing fingers” doesn’t work with production emails Specifically: Do I need to setup the mail directories for the various virtual users on the remote? If so, do the directories need to empty? Should I initially do a manually one-way synch using doveadm from the existing server? If so, is there a way of turning off automatic replication while the manual one runs? Anything else? T David

2 2

Imap client with ~7500 imap cmds ~250/~500 read() syscall
by Marc Roos 31 Dec '20

31 Dec '20

I am playing a bit with the monitoring, and I have noticed there is one client of the chart with ~7500, while the others are between ~17 and ~60 (dovecot_user_num_cmds). I assume this is related to the client, or is it possible something is wrong on the server side? Is someone having also such numbers or is this really strange. Is it possible to limit these cmd's?

3 8

mail-crypt when using passwd-file driver
by Adam Gould 31 Dec '20

31 Dec '20

Hi, I am just finishing my first personal email server build so I would really appreciate it if the response to my question can be spelled out in enough detail since I am struggling to fill in the gaps to get this working. I have scoured Google and the archives but I am not fully understanding the implementation for my setup. I am looking for a solution to encrypt email using a mechanism that increases the difficulty of decrypting my email. For example, having a plain-text decryption key on disk would not be suitable. From what I understand mail-crypt supports using the user password supplied via IMAP to decrypt email. Can someone explain how this technically works? i.e. is the private key encrypted in disk and then unlocked using the supplied password? Can someone also please step me through 1. how I would ammen the configuration below in order to set this up. 2. the command required to generate keys 3. Any help in understanding the limitations such as password changes or caveats around generating keys securely I am happy to take my notes and update the wiki to help others. Thanks, Adam # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.8 (b7b03ba2) # OS: Linux 4.18.0-240.1.1.el8_3.x86_64 x86_64 Red Hat Enterprise Linux release 8.3 (Ootpa) # Hostname: mailserver.example.com debug_log_path = /var/log/dovecot-debug.log info_log_path = /var/log/dovecot-info.log lda_mailbox_autocreate = yes log_path = /var/log/dovecot.log log_timestamp = "%Y-%m-%d %H:%M:%S " mail_home = /var/mail/%d/%n/ mail_location = maildir:~/mail/ 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 index ihave duplicate mime foreverypart extracttext namespace inbox { inbox = yes location = mailbox Archive { auto = create special_use = \Archive } mailbox Drafts { auto = create special_use = \Drafts } mailbox Junk { auto = create special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = create special_use = \Trash } prefix = } passdb { args = scheme=CRYPT username_format=%n@%d /etc/dovecot/passdb driver = passwd-file } plugin { recipient_delimiter = - sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_dir = /etc/sieve/global/ } protocols = imap lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } } service imap-login { inet_listener imap { address = * port = 143 ssl = yes } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl_cert = </etc/letsencrypt/live/mail.example.com/fullchain.pem ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384: DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA: ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256: DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384: AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH: !EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes userdb { args = uid=vmail gid=vmail home=/var/mail/%d/%n driver = static } protocol lmtp { mail_fsync = optimized mail_plugins = " sieve" recipient_delimiter = - }

2 1

Solr and FTS - assertion failure
by Antonino Esposito 31 Dec '20

31 Dec '20

Hi, in the latest weeks i'm working on the Solr integration and immediately i've faced the assertion failure errors, on 2.0.19, 2.2.9 and 2.3.11.3 servers in our network. Reading the thread on debian ML, I realize this issue is related to nested MIME and it affects large mailboxes In my case, the error in dovecot.log pairs with the following on solr.log and it seems the rows value has the same value of the last UID recorded in the mailbox. For your reference, here is the Solr logs, where *2276996170* is the value passed by Dovecot as rows number and it clearly don't fit with the rows data type. Have you had experienced the same behaviour? Is there a workaround? Thanks Antonino 2020-12-30 12:07:33.897 ERROR (qtp1162918744-918) [ x:qadisha] o.a.s.h.RequestHandlerBase org.apache.solr.common.SolrException: For input string: "2276996170" at org.apache.solr.common.params.SolrParams.getInt(SolrParams.java:236) at org.apache.solr.search.QParser.getSortSpec(QParser.java:274) at org.apache.solr.handler.component.QueryComponent.prepare(QueryComponent.java:189) at org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:337) at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:214) at org.apache.solr.core.SolrCore.execute(SolrCore.java:2627) at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:795) at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:568) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:415) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:345) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1596) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:545) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:590) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1610) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1300) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:485) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1580) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1215) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:221) at org.eclipse.jetty.server.handler.InetAccessHandler.handle(InetAccessHandler.java:177) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:322) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) at org.eclipse.jetty.server.Server.handle(Server.java:500) at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:383) at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:547) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:375) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:273) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129) at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:375) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:806) at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:938) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.NumberFormatException: For input string: "2276996170" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Integer.parseInt(Integer.java:583) at java.lang.Integer.valueOf(Integer.java:766) at org.apache.solr.common.params.SolrParams.getInt(SolrParams.java:233) ... 46 more 2020-12-30 12:07:33.897 INFO (qtp1162918744-918) [ x:qadisha] o.a.s.c.S.Request [qadisha] webapp=/solr path=/select params={q={!lucene+q.op%3DAND}from:mykeyword+OR+to:mykeyword+OR+subject:mykeyword&fl=uid,score&sort=uid+asc&fq=% 2Bbox:6d2c381de797e95fbb160000c46e3ae7+%2Buser:info@qadisha.it&rows=2276996170&wt=xml} status=400 QTime=1

2 2

Re: import_environment = $import_environment DEBUG=1 where should this be logged?
by Odhiambo Washington 30 Dec '20

30 Dec '20

Hi Marc, The same document says this: rawlog binary It works by checking if dovecot.rawlog/ directory exists in the logged in user's home directory, and writing the traffic to yyyymmdd-HHMMSS-pid.in and .out files. Each connection gets their own in/out files. *Rawlog will simply skip users who don't have the dovecot.rawlog/ directory and the performance impact for those users is minimal.* On Wed, 30 Dec 2020 at 20:10, Marc Roos <M.Roos(a)f1-outsourcing.eu> wrote: > > You know by any chance how to limit this only for one user? > > > > -----Original Message----- > From: Odhiambo Washington [mailto:odhiambo@gmail.com] > Sent: 30 December 2020 18:00 > To: dovecot > Subject: Re: import_environment = $import_environment DEBUG=1 where > should this be logged? > > > Hi Marc, > > If you read the link keenly - Debugging/Rawlog - Dovecot Wiki > <https://wiki.dovecot.org/Debugging/Rawlog> - you will realize that you > need to do some stuff. > I have done them and they produced the results. > > Edit /path/to/dovecot/conf.d/10-master.conf and add the following: > > Under this block: > > add executable = imap postlogin to the block that has service imap { > .... > ... > } > > Then create another block in the same file as follows: > > service postlogin { > executable = script-login -d rawlog > unix_listener postlogin { > } > } > > Identify the user for whom you want the rawlogs: > > doveadm user -u technical(a)mydomain.name > userdb: technical(a)mydomain.name > user : technical(a)mydomain.name > home : /var/spool/virtual/mydomain.name/technical > uid : 26 > gid : 26 > > Now do the following: > cd /var/spool/virtual/mydomain.name/technical > mkdir dovecot.rawlog > chown -R 26:26 dovecot.rawlog > > systemctl restart dovecot (or however you do it in CentOS) > > Now login to imap as the user .. perform some operations. > > Now look inside > /var/spool/virtual/mydomain.name/technical/dovecot.rawlog/ > > PS: Adapt as necessary. I tested this on FreeBSD with dovecot- 2.3.11.3 > > Ignore the /tmp/rawlog/%u portion of the HOWTO. I did it too, but there > was nothing in /tmp/rawlog/ even though I created the directory and did > chmod 1777 /tmp/rawlog. > > Adios. > > > > > On Wed, 30 Dec 2020 at 19:30, Marc Roos <M.Roos(a)f1-outsourcing.eu> > wrote: > > > > > You can also set DEBUG environment to have rawlog log an info > message > why it's not doing anything: > import_environment = $import_environment DEBUG=1 > > Where should this message appear, I also don't have this one. > > [1] > https://wiki2.dovecot.org/Debugging/Rawlog > > > > > -- > > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", grep ^[^#] :-) > > > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

1 0

Re: import_environment = $import_environment DEBUG=1 where should this be logged?
by Odhiambo Washington 30 Dec '20

30 Dec '20

Hi Marc, If you read the link keenly - Debugging/Rawlog - Dovecot Wiki <https://wiki.dovecot.org/Debugging/Rawlog> - you will realize that you need to do some stuff. I have done them and they produced the results. Edit /path/to/dovecot/conf.d/10-master.conf and add the following: Under this block: add executable = imap postlogin to the block that has service imap { .... ... } Then create another block in the same file as follows: service postlogin { executable = script-login -d rawlog unix_listener postlogin { } } Identify the user for whom you want the rawlogs: doveadm user -u technical(a)mydomain.name userdb: technical(a)mydomain.name user : technical(a)mydomain.name home : /var/spool/virtual/mydomain.name/technical uid : 26 gid : 26 Now do the following: cd /var/spool/virtual/mydomain.name/technical mkdir dovecot.rawlog chown -R 26:26 dovecot.rawlog systemctl restart dovecot (or however you do it in CentOS) Now login to imap as the user .. perform some operations. Now look inside /var/spool/virtual/mydomain.name/technical/dovecot.rawlog/ PS: Adapt as necessary. I tested this on FreeBSD with dovecot- 2.3.11.3 Ignore the /tmp/rawlog/%u portion of the HOWTO. I did it too, but there was nothing in /tmp/rawlog/ even though I created the directory and did chmod 1777 /tmp/rawlog. Adios. On Wed, 30 Dec 2020 at 19:30, Marc Roos <M.Roos(a)f1-outsourcing.eu> wrote: > > > You can also set DEBUG environment to have rawlog log an info message > why it's not doing anything: > import_environment = $import_environment DEBUG=1 > > Where should this message appear, I also don't have this one. > > [1] > https://wiki2.dovecot.org/Debugging/Rawlog > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

2 2

import_environment = $import_environment DEBUG=1 where should this be logged?
by Marc Roos 30 Dec '20

30 Dec '20

You can also set DEBUG environment to have rawlog log an info message why it's not doing anything: import_environment = $import_environment DEBUG=1 Where should this message appear, I also don't have this one. [1] https://wiki2.dovecot.org/Debugging/Rawlog

1 0

Getting rawlogging working with dovecot 2.2
by Marc Roos 30 Dec '20

30 Dec '20

According to this manual[1] I just have to add these lines to my config, not? protocol imap { rawlog_dir = /tmp/rawlog/%u } I should be seeing something in this /tmp/rawlog if I delete an message via imap not? I have already made this folder 777 and /tmp/rawlog/test 777, but still nothing is there. The normal syslog of dovecot does not report any errors. [1] https://wiki2.dovecot.org/Debugging/Rawlog

1 2

Virtual folder with 'younger' not updating
by Jonathan Casiot 30 Dec '20

30 Dec '20

I have a virtual folder set up with the following in dovecot-virtual: INBOX INBOX.temp ALL YOUNGER 86400 The problem is that messages older than 86,400 seconds (24 hours) never disappear from the folder. Is there any fix for this apart from adding INDEX=MEMORY to the mailbox location in the config file? I'm running Dovecot 2.2.36 on CentOS. Regards, -- Jonathan

2 6

read state not propagated
by Marc Roos 30 Dec '20

30 Dec '20

I have migrated the inbox namespace from mbox to mdbox by doing a doveadm backup to the new server. Both servers are having CentOS7 + dovecot-2.2.36-6.el7_8.1.x86_64, both servers have identical configurations (new server has some different vsz_limits and stats enabled) Now a user complains that an imap mailbox he opens at the same time with a colleague does not propagate the 'read' state. Previously if his colleague read the message, it would show on his mailbox also 'read'. After the transfer it keeps being unread for him. Am I correct to assume that he should indeed get an updated to 'read'? Where should I look to fix this? What can be the cause of this?

3 5

AUTH command behaviour when authentication process failed or aborted by user is changed
by Михаил Сандаков 30 Dec '20

30 Dec '20

Hi all, I have tried to update from 2.3.10.1 to 2.3.11.3 and found some strange change of dovecot behaviour at pop3 authentication. Firstly this changes have been found by my tests with curl. But this can be simply reproduced with telnet too. On version 2.3.10.1 when authentication is failed or aborted by client, client can send "AUTH [auth method]" to retry authentication with the same or another authentication method. Example of client <-> server conversation: server <<< +OK Dovecot ready. client >>> AUTH DIGEST-MD5 server <<< [some_auth_data] client >>> * server <<< -ERR Authentication aborted by client. client >>> AUTH CRAM-MD5 server <<< [another_auth_data] But on version 2.3.11.3 in the same cases client must send only "auth method" without "AUTH". Example of successful conversation on this version: server <<< OK Dovecot ready. client >>> AUTH DIGEST-MD5 server <<< [some_auth_data] client >>> * server <<< -ERR Authentication aborted by client. client >>> CRAM-MD5 server <<< [another_auth_data] And example of what happens if a client will try to do that in an old way on version 2.3.11.3: server <<< OK Dovecot ready. client >>> AUTH DIGEST-MD5 server <<< [some_auth_data] client >>> * server <<< -ERR Authentication aborted by client. client >>> AUTH CRAM-MD5 server <<< ERR [AUTH] Unsupported authentication mechanism. As you can see dovecot tries to find an authentication method by string "AUTH" not by "CRAM-MD5". This change looks strange to me. And changes break curl, because it uses an old way to make authentication. To reproduce it with curl you can just do something like: [user(a)10.52.48.220]# curl -u [user]:[password] --verbose pop3://[dovecot-host] Also seems like new behaviour is not fully accorded to rfc1734 ( https://tools.ietf.org/html/rfc1734) Based on this part of rfc: "If an AUTH command fails with a negative response, the session remains in the AUTHORIZATION state and client may try another authentication mechanism by issuing another AUTH command, or may attempt to authenticate by using the USER/PASS or APOP commands." I think "AUTH command" means full auth command started with "AUTH", not only authentication method. But I may be wrong in the interpretation of this part. I suppose this changes was made in commit https://github.com/dovecot/core/commit/2c42881c056e5ab2e2e14b2f800d6dc72026…, but not sure about this. Seems like if authentication is aborted or failed client->current_cmd is not going to be cleaned. So I suggest to revert old behaviour in this cases. If I am right with commit, it seems like we just need to add clearing client->current_cmd if the authentication process has failed somehow.

2 2

dovecot+ldap with keepalive
by Maciej Milaszewski 28 Dec '20

28 Dec '20

Hi I have dovecot-2.36.4 (director +5 nodes) - backend to auth is openldap+keepalived to second ldap For test i shutdown my ldap server - keepalive works perfectly VIP switched - ldapserach works ok (all connect to second ldap) but I noticed strange dovecot behavior - some user get "no response" or "waiting waiting" in dovecot i use: auth_cache_negative_ttl = 5 mins auth_cache_size = 20 M auth_cache_ttl = 5 mins service lmtp { inet_listener lmtp { address = 127.0.0.1 10.0.100.4 port = 24 } process_min_avail = 5 protocol lmtp { auth_socket_path = director-userdb mail_plugins = quota expire notify mail_log passdb { args = proxy=y nopassword=y port=24 driver = static name = } syslog_facility = local3 } in ldap server i have: idletimeout 256 Any idea ?

1 0

Re: .imap folders
by Aki Tuomi 28 Dec '20

28 Dec '20

On 28/12/2020 13.10, Elise wrote: > Op 27-12-20 om 16:16 schreef Aki Tuomi: > >> The .imap directories contain indexes for dovecot. If you want to put >> them elsewhere, try adding :INDEX=/somewhere/else/%u to your mail >> location. > > Thanks for this. Where should I put this line or is that part of the > command line? > > /Elise > in your mail location, where you have specified `mbox:~/...` We do not recommend using mbox mail format for read-write, as the support for that is limited. Aki

2 1

Very slow mail download/notification with dovecot 2.3.7 and Thunderbird
by ml_dovecot＠thorsten-reichelt.de 28 Dec '20

28 Dec '20

Hi! I know that there are many results if I search for "dovecot thunderbird very slow" on Google but none of them helped me with my problem. :( (I already posted this on February 2020, but forgot to answer. O.o) I am running Ubuntu 20.04 (4GB RAM, 40GB HDD with EXT4) server with the following software: - Dovecot 2.3.7.2 ---- All accounts are using Maildir ---- Sieve filters - Postfix 3.4.13 ---- with opendkim, spamassassin, razor, pyzor, .... And as IMAP client I am using Thunderbird 78.6 on Windows 10. Sieve is used to sort some incoming mails into my 228 folders (56 INBOX. folders and its subfolders (output of "find .INBOX.* -maxdepth 4 -type d -print |wc -l")). The total size of my Maildir directory is 5.5GB. My problem is that it always takes very very long to synchronize the INBOX and its subfolders. Even if there are only a few new messages to be downloaded. Sometimes Thunderbird outputs something like "downloading message 1 of 19" and it takes at least 60 seconds to download all of them. None of these mails is larger than 5kB. And sometimes it seems that the transfer is suspended for a long time and it takes >5 Minutes to synchronize only a few mails. :( And it seems that some folders are never updated in TB. In example I sort all messages from this list into a "INBOX.Mailinglists.ML-Dovecot" subfolder by using a simple sieve rule. But even after 10 minutes TB thinks that there are no new messages. As soon as I click on the ML-Dovecot folder I see in the /var/log/dovecot-info.log file that TB logs on to the server and then displays hundreds, of new messages. I checked twice but I have subscribed to all 228 folders. How can I find the bottleneck? Is there a test tool available that simulates a simple mail client and can analyse an IMAP server? This is the output of "dovecot -n": =============================== # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0-54-generic x86_64 Ubuntu 20.04.1 LTS # Hostname: mail.XXXXXXX.de auth_mechanisms = plain login debug_log_path = /var/log/dovecot-debug.log default_client_limit = 15653 default_process_limit = 5200 first_valid_uid = 150 info_log_path = /var/log/dovecot-info.log last_valid_uid = 150 lda_original_recipient_header = X-Original-To log_path = /var/log/dovecot-error.log login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_gid = mail mail_home = /var/vmail/%d/%n mail_location = maildir:~/Maildir mail_uid = vmail 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 inbox { inbox = yes location = mailbox Archive { special_use = \Archive } 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-sql.conf.ext driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_default = /var/vmail/global.sieve sieve_dir = ~/sieve } postmaster_address = thorsten(a)MY_DOMAIN.TLD protocols = " imap sieve pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = mail mode = 0666 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_limit = 50 process_min_avail = 2 service_count = 20 } service imap { process_limit = 1024 } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 0 } ssl_cert = </etc/ssl/mail/mail.XXXXXXX.de.fullchain.pem ssl_cipher_list = ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384 ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 syslog_facility = local5 userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = " sieve" rejection_reason = Your message to <%t> was automatically rejected:%n%r } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep imap_idle_notify_interval = 10 mins mail_max_userip_connections = 100 mail_plugins = } protocol sieve { info_log_path = /var/log/dovecot-sieve.log mail_max_userip_connections = 100 managesieve_implementation_string = Dovecot Pigeonhole managesieve_max_line_length = 65536 =============================== Output of "free -h": =============================== free -h total used free shared buff/cache available Mem: 3.8Gi 1.7Gi 1.1Gi 10Mi 958Mi 1.7Gi Swap: 1.0Gi 375Mi 648Mi =============================== Thank you very much! Thorsten

5 6

.imap folders
by Elise 27 Dec '20

27 Dec '20

My user account is located at /usr/home/elise and has a subfolder ./mail In that folder I have some subfolders/subdirectories. What happens now is that dovecot creates all kind of .imap folders in these subfolders. They are all exact mirrors of the base folder(s) the .imap is part of. Can you tell me how I can prevent that dovecot creates these .imap folders other than in my home user folder /usr/home/elise and the /usr/home/elise/mail folder? /Elise

2 1

IMAP from localhost (Squirrelmail) works, IMAP from remote (Outlook) does not authenticate
by Wayne Carrel 25 Dec '20

25 Dec '20

I have been struggling with this for some time now. I have searched, tried, broke it, fixed it, and still no luck. Will somebody please help me see what is wrong? [root@mail ~]# dovecot --version 2.2.36 (1f10bfa63) [root@mail ~]# dovecot -n # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-1160.2.2.el7.x86_64 x86_64 CentOS Linux release 7.9.2009 (Core) # Hostname: mail.mydomainname.com auth_mechanisms = plain login disable_plaintext_auth = no first_valid_uid = 1000 mail_location = maildir:~/Maildir 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 } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = postfix user = postfix } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = # hidden, use -P to show it userdb { driver = passwd } >From maillog: (Successful login from localhost via squirrel mail) Dec 24 16:14:19 mail dovecot: imap-login: Login: user=<terry>, method=PLAIN, rip=::1, lip=::1, mpid=2279, secured, session=<CJKj9z23kN0AAAAAAAAAAAAAAAAAAAAB> (Unsuccessful login from remote ip via Outlook) Dec 24 16:13:53 mail dovecot: imap-login: Disconnected (auth failed, 1 attempts in 4 secs): user=<terry(a)mydomainname.com>, method=PLAIN, rip=75.xx.xx.xx, lip=198.xx.xx.xx, session=<1s/i9T23yspLRsWA> I would be most grateful for any assistance anyone can provide -- my head is sore from beating against the wall! 😊

3 2

doveadm backup -f -n inbox doing writes?
by Marc Roos 22 Dec '20

22 Dec '20

If I start a 'doveadm backup -f -n inbox' on the source server, why do also disk writes increase on the source server (indexes mostly?)

2 2

Repeated Inbox Corruption, how to Troubleshoot?
by Bryan K. Walton 21 Dec '20

21 Dec '20

We are running Dovecot Version 2.3.8 (9df20d2db) (from the CentOS 8 repos). Twice in the last week, I've encountered an issue where my Mutt imap client logs into our imap server and has 0 new messages (when I know that there are a lot of new messages waiting on me). Both times, I've had to shut down my mail client, and then run: doveadm -Dv force-resync -u <username> INBOX After which, I reopen Mutt and all of my new emails appear in the inbox of my mail client. Running the force-resync shows no problems. Furthermore, "doveadm log errors" shows no errors on my account and there is nothing in the logs showing that anything is corrupted for me. Yet, the force-resync is fixing a problem that I can't locate. Where should I be looking (or how should I update my logging) so that I can find out the source of the problem that is causing my repeated inbox problems? Thanks! Bryan Walton -- Bryan K. Walton 319-337-3877 Linux Systems Administrator Leepfrog Technologies, Inc

2 2

Fail2ban and login_trusted_networks
by Javi Legido 21 Dec '20

21 Dec '20

Hi there. First of all many thanks to all the people involved in this project for their time, I really appreciate it. Second my use case: a) Container running Webmail (roundcube) with dovecot-ident plugin enabled <https://github.com/roundcube/roundcubemail/issues/5336#issuecomment-2281310…> . b) Container running Dovecot 2.3.4.1 (docker-mailserver-mysql <https://github.com/Kedu-SCCL/docker-mailserver-mysql>) with fail2ban enabled Since I need to add the private IP address of the webmail to "login_trusted_networks" to "...allow to override their IP addresses and ports" I can keep login to webmail even though if the IP is blocked. Question: there's any way to: a) Allow a certain IP range to override it's IP address and ports (as in "login_trusted_networks") but b) Be blocked, as any other incoming connections, by fail2ban? More context. Once the public IP is banned (8.8.8.8 in this example): ``` 2020-12-21 10:10:31,371 fail2ban.filter [309]: INFO [dovecot] Found 8.8.8.8 - 2020-12-21 10:10:31 2020-12-21 10:10:39,189 fail2ban.filter [309]: INFO [dovecot] Found 8.8.8.8 - 2020-12-21 10:10:39 2020-12-21 10:10:51,222 fail2ban.filter [309]: INFO [dovecot] Found 8.8.8.8 - 2020-12-21 10:10:51 2020-12-21 10:10:52,008 fail2ban.actions [309]: NOTICE [dovecot] Ban 8.8.8.8 ``` I can't reach dovecot by telnet from this public IP: ``` telnet mail.example.com 143 Trying 9.9.9... telnet: Unable to connect to remote host: Connection refused ``` Unless I removed the ban: ``` docker exec mail fail2ban-client set dovecot unbanip 8.8.8.8 ``` Many thanks. Javier

3 3

Using dovecot with RoundCubeMail - where is the information for new mail in (blue coloured) directories?
by Philip Rhoades 21 Dec '20

21 Dec '20

People, Every few years I try to work this problem out - occasionally I would like to re-mark a dir as having new mail so that the dir shows up as blue-coloured in RCM. Every time I Google in vain and then have a go at working it out myself but the only thing I can see is that there is a change in the appropriate dir dovecot.index.log file after having the blue dir clicked on (and the colour of the dir name changes back to black) - so is the information stored somewhere in RCM itself? Thanks, Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: phil(a)pricom.com.au

5 10

Required key not available
by David Matthews 19 Dec '20

19 Dec '20

hello dovecot -n # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-12-amd64 x86_64 Debian 10.0 what is the meaning / cause of this in mail.err:- ---------------------------------------------------------- dovecot: imap(david)<5004><vCVKAtO2UI1/AAAB>: Error: Mailbox Trash: open() failed with mbox: Required key not available ---------------------------------------------------------- I can telnet to port 143, log in and list folders, but cannot open them. This seems to have resulted from an experimental install (now purged) of courier-imap (I maintain a webmail program). Before this, dovecot just worked; now this problem remains even after a reinstall. -- David Matthews mail(a)dmatthews.org

1 0

Using dovecot with RoundCubeMail - where is the information for new mail in (blue coloured) directories?
by Philip Rhoades 19 Dec '20

19 Dec '20

People, Every few years I try to work this problem out - occasionally I would like to re-mark a dir as having new mail so that the dir shows up as blue-coloured in RCM. Every time I Google in vain and then have a go at working it out myself but the only thing I can see is that there is a change in the appropriate dir dovecot.index.log file after having the blue dir clicked on (and the colour of the dir name changes back to black) - so is the information stored somewhere in RCM itself? Thanks, Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: phil(a)pricom.com.au

3 3

ulimit -n vs client_limit vs process_limit
by Joseph Tam 19 Dec '20

19 Dec '20

As many of my users are accessing their mail remotely, I've seen service loads increase and came across this log messages which I haven't seen before imap-login: Error: socketpair() failed: Too many open files: user=<*>, ... I gather I have to increase file descriptor limits, which is currently set to match default_client_limit = 1000 What should I set "ulimit -n" relative to client_limit? Or perhaps I've roofed service imap-login { process_limit = 2 ... } and should adjust that? Joseph Tam <jtam.home(a)gmail.com>

3 3

Dovecot Replication Errors (only) when using tcps: as the mail_replica Protocol
by Reuben Farrelly 18 Dec '20

18 Dec '20

Hi, I've been seeing errors logged for some time with replication processes, whereby replication sessions seem to be timing out periodically. This is with dovecot version 2.3.10.1 (a3d0e1171) and both are Gentoo x86_64. After some investigation I've determined that these timeouts are only ever occurring with tcps as the replication connection type. These errors never occur if non-encrypted tcp is configured. I've been able to validate this by changing only the replica_type on both ends of the replication configuration to tcp, and with no other changes and after a few days of operation there is not a single error logged. mail_replica = tcps:lightning.reub.net:4813 <<< periodic timeouts mail_replica = tcp:lightning.reub.net:4814 <<< works perfectly Example of the error: Jun 12 15:45:44 thunderstorm.reub.net dovecot[21149]: dsync-local(kaylene)<zx+WKTAU416UMwAAzkCIew>: Error: dsync(lightning.reub.net): I/O has stalled, no activity for 600 seconds (last sent=mailbox_delete, last recv=handshake) Jun 12 15:45:44 thunderstorm.reub.net dovecot[21149]: dsync-local(kaylene)<zx+WKTAU416UMwAAzkCIew>: Error: Timeout during state=recv_mailbox_tree doveadm: Error: Timeout during state=slave_recv_mailbox: 6 Time(s) doveadm: Error: Timeout during state=sync_mails (send=mail_requests recv=attributes): 31 Time(s) doveadm: Error: dsync(thunderstorm.reub.net): I/O has stalled, no activity for 600 seconds (last sent=mail_change (EOL), last recv=mailbox): 31 Time(s) doveadm: Error: dsync(thunderstorm.reub.net): I/O has stalled, no activity for 600 seconds (last sent=mailbox_delete, last recv=mailbox_delete): 6 Time(s) It is seen on both sides of the replication setup. The replica is offsite but only a few ms of latency away and there is no packet loss. The replication is happening over IPv6, and the local firewall is logging that sessions are always permitted, and only ever finishing due to tcp-fin or tcp-rst-from-client . SSL appears to be correctly configured, and it seems that the replication itself is for the most part working. Clients are able to use imaps just fine so I don't think there's anything much wrong from an SSL perspective else I'd be seeing complete replication failure and/or client devices unable to connect. Can anyone suggest how we can further debug this problem? Thanks, Reuben

4 3

Outlook with Dovecot
by Elise 17 Dec '20

17 Dec '20

dovecot-2.3.11.3_1 Hi group, I have a problem with connecting Outlook 2019 client to my server (BSD 21.2). Running Postfix and Dovecot. [all.log] Dec 12 16:53:41 poseidon dovecot[36185]: imap-login: Disconnected (auth failed, 1 attempts in 2 secs): user=<elise(a)xxxxx.xx>, method=PLAIN, rip=82.x.x.x.x, lip=10.x.x.x, TLS: Connection closed, session=<U62faUa24N5SsH9H> Providing the correct email address and password. Strang thing is that with Thunderbird it all works fine; only Outlook is refused. tx, Elise [dovecot.conf] auth_mechanisms = plain login disable_plaintext_auth = no mail_location = mbox:/usr/home/%u:INBOX=/var/mail/%u mail_privileged_group = mail passdb { driver = pam } protocols = imap service auth { unix_listener auth-client { group = mail mode = 0660 user = postfix } unix_listener auth-master { mode = 0666 } user = root } service imap-login { inet_listener imap { address = 10.x.x.x } inet_listener imaps { address = 10.x.x.x } } #service pop3-login { # inet_listener pop3 { # address = 10.x.x.x # } # inet_listener pop3s { # address = 10.x.x.x # } #} ssl = yes ssl_ca = </usr/local/share/certs/ca-root-nss.crt ssl_cert = </usr/local/etc/dehydrated/certs/xxxx.xxx/fullchain.pem ssl_key = </usr/local/etc/dehydrated/certs/xxxx.xxx/privkey.pem ssl_cipher_list = HIGH:+TLSv1.2:+TLSv1.3 ssl_dh = </usr/local/etc/dovecot/dh.pem userdb { driver = passwd } 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 { postmaster_address = postmaster(a)xxxxx.xxxx sendmail_path = /usr/sbin/sendmail mail_plugins = sieve }

7 11

Special files under dovecot mail box
by hfh＠cndns.com 17 Dec '20

17 Dec '20

Hello, even if all the mails(messages) are deleted from my mail box (such as the sent box), the capacity of the following special files will not change, that is, these files will only increase and easily occupy the disk. Is there any other way besides using doveadm index manually? In addition, will these files be affected if they are deleted? -rw-------. 1 vmail vmail 3912 Dec 1 13:52 dovecot.index -rw-------. 1 vmail vmail 127008 Dec 17 17:21 dovecot.index.cache -rw-------. 1 vmail vmail 18800 Dec 17 17:21 dovecot.index.log -rw-------. 1 vmail vmail 1567 Jun 20 2019 dovecot.index.thread Dovecot version is 2.2.36.

1 0

Disallow acces via imap, but keep lmtp running
by Julian Kippels 17 Dec '20

17 Dec '20

Hi all, what is the best way to temporarily disable access to a mailbox via imap, but keep it possible to deliver to the mailbox via lmtp? I want to migrate some mailboxes around and would like to ensure that the users cannot access their mail while doing so. I would like to keep the users from logging in entirely rather than setting ACLs. Thanks in advance Julian

5 4

Re: Disallow acces via imap, but keep lmtp running
by Julian Kippels 16 Dec '20

16 Dec '20

I thought about that, but that would also kill their access to wifi and other services, because it all comes from the same LDAP. Julian Am Tue, 15 Dec 2020 23:37:58 +0100 schrieb Jos <jos(a)cloudzeeland.nl>: > You could change their password temporily and do the migration? > > — Verstuurd via een mobiele telefoon > > > Op 15 dec. 2020 om 23:22 heeft Julian Kippels <kippels(a)hhu.de> het > > volgende geschreven: > > > > Hi all, > > > > what is the best way to temporarily disable access to a mailbox via > > imap, but keep it possible to deliver to the mailbox via lmtp? > > I want to migrate some mailboxes around and would like to ensure > > that the users cannot access their mail while doing so. > > I would like to keep the users from logging in entirely rather than > > setting ACLs. > > > > Thanks in advance > > Julian

3 2

Dovecot Director scaling / performance
by tim＠linux-daus.de 15 Dec '20

15 Dec '20

Hi, currently i'm going to evaluate the Dovecot Director. Are there someone with experience how the Dovecot Director does scale? The last current information i could find was a post on this mailing list from 2012: 4 Directors are well known, >75 are too much. Are there any more up to date experience regarding how many user (current and new/s) a single Dovecot Director/proxy node could handle and how many director nodes in a ring are known to work (well)? Best regards, Tim

2 1

Putting UIDL value into X-UIDL: header
by Süleyman Düzdaban 15 Dec '20

15 Dec '20

Hi, Is there any way to put UIDL value into X-UIDL: header with Dovecot or Sieve? As stated in https://wiki2.dovecot.org/Migration page QPopper can do that. I'm asking this for preventing clients who are using POP to re-download messages and making future migrations easy. I can really benefit from inserting UIDL values even only for the new messages from now on, but if there is any way to put it into all messages in all mailboxes (Maildir) I would be grateful for that too. Dovecot version: 2.3.8 (9df20d2db) Thanks in advance.

3 4

How to reset / remove all replicator users
by Ralf Becker 14 Dec '20

14 Dec '20

After creating a new replication pair, it was started with an old sqlite userdb, we use for iteration / replication. The situation was quickly resolved by generating a new sqlite userdb, as it is done hourly anyway. Unfortunately I can not get ride of all access users from the replication: / # doveadm replicator status Queued 'sync' requests 0 Queued 'high' requests 0 Queued 'low' requests 0 Queued 'failed' requests 0 Queued 'full resync' requests 14 Waiting 'failed' requests 1 Total number of known users 724 / # doveadm user '*'|wc -l 507 The replication process creates again and again a lot (empty) mailboxes on both sides of the replication. I tried the obvious with no avail: / # doveadm replicator remove '*' Error: Replicator failed: User not found I also tried restarting the pair one after the other, but it seems the users to replicate are somewhere persisted. I'm also trying to delete the users from the newly created (empty) mailboxes, but the number of known users in "doveadm replicator status" is unchanged: root:/var/dovecot/imap# for domain in $(ls -1 |grep -v bb-trunk.egroupware.de|grep -v outdoor-training.de|grep -v rbz-); do for user in $domain/*; do echo "$(basename $user)@$domain"; doveadm replicator remove "$(basename $user)@$domain"; done; rm -rf $domain; done Any idea what else I can do, or where the replication stores it's users? Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

2 1

How to setup Dovecot director in a NAT-like environment?
by Richard Mader 14 Dec '20

14 Dec '20

How can I setup Dovecot director in a NAT like environment? My mailservers are running within docker and one of them behind a router, so the IP that dovecot binds to does not match the IP that other mailservers have to use to connect to them. Since when running director the servers connect to each other, I'd guess I'd have to set the external IP of the servers in the "director_servers". If I do that I'm unable to start the director nodes since they cannnot find out which of the addresses is their own. I had a quick peek at the sourcecode and director detects its own address by trying to bind to all of the addresses. Since we're behind a NAT, that will of course fail for its external IP. When I set the local address or localhost in the "director_servers" directive, then the director nodes are able to start but they are denied when connecting to other nodes. When using the NAT-internal IP I've got the following error: > Error: Remote director thinks it's someone else (connected to > <other-directors-external-ip>:9090, remote says it's > <other-directors-internal-ip>:9090) When using localhost/127.0.0.1 then I get: > Info: Connecting to <other-directors-external-ip>:9090 (as 127.0.0.1): > Alone in director ring - trying to connect to others > Error: connect(<other-directors-external-ip>:9090) failed: Invalid > argument Is it somehow possible to tell director which of the addresses within "director_servers" is its own address, that it then advertises to other servers, instead of trying figuring that out itself by trying to bind to all ip-addresses on startup? Kafka e.g. has the "advertised.listeners" property to set a custom host to announce to clients and to other Kafka nodes. If there is not such a property or any other workaround, I might consider implementing this into director myself. Although I might need some help getting started since this is my first time contributing to a non Scala/Java or Typescript/NodeJS Project. So far I've discovered that Github seems to be the official repo and is not just a mirror and I was able to compile it on my machine. Now I've got questions such as, where can I find the binaries that I've just compiled and whats the best way to get them running locally and to test my changes, where are unit tests located, ...? Best Regards, Richard

2 1

Migrate mailbox from NFS folder to new NFS folder
by Claudio Corvino 14 Dec '20

14 Dec '20

Hi everyone, I need to migrate many user mailboxes from an NFS folder to a new NFS folder, both mounted on the same Dovecot server (2.2.27). Once migrated, users will connect to a new Dovecot server (2.3.4.1). I would like to know how to use /doveadm backup/ (or sync?) instead of /rsync/ as I noted that after migration with rsync I have duplicates and some e-mails marked as unread. What is the correct way to achieve this? Thanks Cheers

2 1

Unexpected behavior of doveadm mailbox delete -e -s
by Mar Alegre 13 Dec '20

13 Dec '20

Hello, I have encountered what I believe to be a bug, or at least inaccurate documentation. I am running version 2.3.4.1 of Dovecot (installed via the default repo for Debian 10), so my apologies if this has been fixed in a more recent version. I tried to look for changelogs but was not able to find any. The `doveadm mailbox delete` command accepts flags `-e` and `-s` (among others). The flags are described by both the man pages and the wiki as follows: - `-e`: Require mailboxes to be empty before deleting. - `-s`: Unsubscribe deleted mailboxes. Based on these descriptions, I would expect that when both of these flags are combined, a directory that is not empty would be neither deleted nor unsubscribed. However, I have discovered that when I run the command `doveadm mailbox delete -u $myusername -e -s $non_empty_dir`, the result is that the directory is not deleted, but it *is* unsubscribed. I assume this is a bug, but if it is intended, the documentation should probably be updated to more clearly communicate that the `-s` flag will cause a directory to be unsubscribed even if it is not deleted. Best, Mar Alegre

2 1

fyi: please change /var/run to /run in debian buster repository
by Michael 12 Dec '20

12 Dec '20

hey, just one minor thing: if there's any time left, please change in the repository debian/buster in the package dovecot-core in the file /lib/systemd/system/dovecot.service the line PIDFile=/var/run/dovecot/master.pid to PIDFile=/run/dovecot/master.pid because systemd always shows the following warning: Dec 12 15:46:30 mail systemd[1]: /lib/systemd/system/dovecot.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/dovecot/master.pid → /run/dovecot/master.pid; please update the unit file accordingly. creating a drop-in in /etc/systemd/system/dovecot.service.d/ doesn't do anything. greetings...

2 1

important message
by jk00100033＠gmail.com 12 Dec '20

12 Dec '20

I've invited you to fill out the following form: Untitled form To fill it out, visit: https://docs.google.com/forms/d/e/1FAIpQLSeqI7QUpet4levWQvhvUuqn1Au-fqPDo0W… Greetings! To You Mr. Joe is my name; I work in a Bank here in Benin. And I personally handle transactions of Mr. Martin Quick who eventually died on the 5th of February 2017 from injuries sustained in a road accident that happened 3 years ago. Prior to his death, Mr. Martin Quick lived and worked in Benin Republic and was doing Contracting with Benin Energy dept. He has (Four million, three hundred thousand Euros) in a fixed account with the bank with no other beneficiary. Now I write to seek your consent to present you as an oversea based partner to stand in as next of kin to the late Mr. Martin Quick. Let me know if it is ok to work with you. please email me in my private email for more details ( kukuaj001(a)gmail.com ) please email me in my private email for more details ( kukuaj001(a)gmail.com ) My best Regards Mr. Joe. Google Forms: Create and analyze surveys.

4 3

Potential issue with lmtp_rawlog_dir when using TLS
by John Fawcett 11 Dec '20

11 Dec '20

Hi not sure why this happens, but looks like lmtp_rawlog_dir blocks the successful negotiation of an lmtp starttls connection. Reproducible with openssl s_client. Two runs with only difference the presence of lmtp_rawlog_dir setting in dovecot config. Failed connection with lmtp_rawlog_dir Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Connect from ::1 Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Debug: SSL: where=0x10, ret=1: before SSL initialization Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Debug: SSL: where=0x2001, ret=1: before SSL initialization Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Debug: SSL: where=0x2002, ret=-1: before SSL initialization Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Debug: SSL: where=0x2002, ret=-1: error Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Debug: SSL error: SSL_accept() failed: error:1408F10B:SSL routines:ssl3_get_record:wrong version number Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Error: lmtp-server: conn [::1]:53876 [2]: SSL handshake failed: SSL_accept() failed: error:1408F10B:SSL routines:ssl3_get_record:wrong version number Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Debug: SSL error: SSL_accept() syscall failed: Invalid argument Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Disconnect from ::1: SSL Initialization failed (state=READY) Successful connection without lmtp_rawlog_dir Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Connect from ::1 Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x10, ret=1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL_get_servername() failed Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read client hello Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server hello Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write change cipher spec Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: TLSv1.3 write encrypted extensions Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write certificate Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: TLSv1.3 write server certificate verify Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write finished Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read finished Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x20, ret=1: SSLv3/TLS write session ticket Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write session ticket Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write session ticket Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully John

1 0

Dovecot 2.3.11.3 LMTP dropping connection after first part of multipart message received
by Steve Akerman 11 Dec '20

11 Dec '20

Good afternoon I have been using Dovecot with great success for several months now with one problem: I have received several messages (3 to date out of a much larger number) which cause Dovecot LMTP to drop the connection with sendmail after only receiving the first part of the message. Dovecot saves the first part to INBOX, and then drops the link with sendmail as it sees the rest of the data from sendmail as new (and invalid) commands Sendmail sees the delivery as unsuccessful and requeues the message, so the cycle continues until i kill the queue These messages are all Multipart MIME I have attached an extract from the log which shows the above sequence Finally, I have kept one such message from the sendmail queue (df and qf) should this be useful, but prefer not to post here as not sanitised Any help in correcting my configuration would be appreciated. Thanks Steve MAIL LOG extract ------------------------- Dec 9 12:00:10 phone dovecot[179]: lmtp(20774): Connect from local Dec 9 12:00:10 phone sm-mta-rx[20764]: STARTTLS=client, relay=localhost, version=TLSv1.3, verify=OK, cipher=TLS_AES_256_GCM_SHA384, bits=256/256 Dec 9 12:00:10 phone dovecot[179]: lmtp(20775): Connect from local Dec 9 12:00:10 phone sm-mta-rx[20763]: STARTTLS=client, relay=localhost, version=TLSv1.3, verify=OK, cipher=TLS_AES_256_GCM_SHA384, bits=256/256 Dec 9 12:00:10 phone dovecot[179]: lmtp(*********)<20775><8EieKDqu0F8nUQAA0J78UA>: msgid=<39113a86-fdbb-4cea-b1c3-d225dff93328(a)info.ameli.fr <mailto:39113a86-fdbb-4cea-b1c3-d225dff93328@info.ameli.fr>>: saved mail to INBOX Dec 9 12:00:10 phone dovecot[179]: lmtp(20775): Disconnect from local: Too many invalid commands. (state=READY) Dec 9 12:00:10 phone sm-mta-rx[20763]: STARTTLS: write error=syscall error (-1), errno=32, get_error=error:00000000:lib(0):func(0):reason(0), retry=1, ssl_err=5 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: SYSERR(root): timeout writing message to localhost: Broken pipe Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 0: fl=0x0, mode=20666: CHR: dev=30/1306024, ino=301, nlink=1, u/gid=0/0, size=0 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 1: fl=0x1, mode=20666: CHR: dev=30/1306024, ino=301, nlink=1, u/gid=0/0, size=0 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 2: fl=0x1, mode=20666: CHR: dev=30/1306024, ino=301, nlink=1, u/gid=0/0, size=0 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 3: fl=0x4002, mode=100600: dev=1/2, ino=26089780, nlink=1, u/gid=0/23, size=2041 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 4: fl=0x0, mode=20666: CHR: dev=30/1306024, ino=575, nlink=1, u/gid=0/0, size=0 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 5: fl=0x2, mode=140666: SOCK localhost->[[UNIX: /var/run/mDNSResponder]] Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 6: fl=0x0, mode=100640: dev=1/2, ino=25887976, nlink=1, u/gid=0/23, size=12288 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 7: fl=0x0, mode=100640: dev=1/2, ino=25887976, nlink=1, u/gid=0/23, size=12288 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 8: fl=0x0, mode=100600: dev=1/2, ino=26088246, nlink=1, u/gid=0/23, size=58024 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 9: fl=0x6, mode=140444: SOCK localhost->(Invalid argument) Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 10: fl=0x6, mode=140444: SOCK localhost->(Invalid argument) Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 11: fl=0x0, mode=100640: dev=1/2, ino=25768590, nlink=1, u/gid=0/23, size=12288 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 12: fl=0x0, mode=100640: dev=1/2, ino=25768590, nlink=1, u/gid=0/23, size=12288 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: MCI@0x0: NULL Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: MCI@0x7fae2c814818: flags=26404c<CACHED,ESMTP,8BITMIME,INMIME,ENHSTAT,PIPELINED,TLSACT>, errno=32, herrno=0, exitstat=75, state=8, pid=0, maxsize=0, phase=client DATA 354, mailer=dovecot, status=4.4.2, rstatus=(null), host=localhost, lastuse=Wed Dec 9 12:00:10 2020\n Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: to=<s****************>, delay=1+01:11:31, xdelay=00:00:00, mailer=dovecot, pri=4787366, relay=localhost, dsn=4.4.2, reply=75, stat=Deferred ######################*****############## ### DOVECOT Mailer specification ### ##################*****################## Mdovecot, P=[IPC], F=zDFMPhnul59, S=EnvFromSMTP/HdrFromSMTP, R=EnvToSMTP/HdrFromSMTP, T=DNS/RFC822/X-Unix, A=FILE /var/run/dovecot/lmtp dovecot -n ————— # 2.3.11.3 (502c39af9): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.11 (d71e0372) doveconf: Warning: service auth { client_limit=100 } is lower than required under max. load (300) doveconf: Warning: service anvil { client_limit=100 } is lower than required under max. load (203) # OS: Darwin 15.6.0 x86_64 # Hostname: *************** doveconf: Error: t_readlink(/var/run/dovecot//dovecot.conf) failed: readlink() failed: Permission denied auth_mechanisms = cram-md5 auth_username_format = %Ln base_dir = /var/run/dovecot/ default_client_limit = 100 default_internal_group = _dovecot default_internal_user = _dovecot default_login_user = _dovenull hostname =***************** lda_mailbox_autocreate = yes mail_gid = 530 mail_home = /var/mail/%d/%n mail_location = sdbox:~/dbox mail_uid = 530 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 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 = scheme=SSHA256 username_format=%u /usr/local/etc/dovecot/users driver = passwd-file } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } postmaster_address = postmaster protocols = imap lmtp service auth { unix_listener auth-userdb { group = mailusers mode = 0777 user = _dovecot }

2 2

Disconnected: Inactivity (auth failed, 2 attempts in 180 secs)
by basti 11 Dec '20

11 Dec '20

Hello, I have a problem with "apple mail". Once it work as expected, then it does not answer. Dez 10 00:16:04 vsrv10563 dovecot[17121]: imap-login: Login: user=<info(a)example.com>, method=PLAIN, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, mpid=4490, TLS, session=<Oit4OxC2CTZNFv7P> Dez 10 00:17:38 vsrv10563 dovecot[17121]: imap-login: Login: user=<info(a)example.com>, method=PLAIN, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, mpid=5174, TLS, session=<IhlpQhC2XjZNFv7P> Dez 10 00:18:14 vsrv10563 dovecot[17121]: imap-login: Disconnected: Inactivity (auth failed, 2 attempts in 180 secs): user=<user(a)example.com>, method=CRAM-MD5, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, TLS, session=<tkVXOxC2DDZNFv7P> Dez 10 00:18:14 vsrv10563 dovecot[17121]: imap-login: Disconnected: Inactivity during authentication (auth failed, 2 attempts in 179 secs): user=<info(a)example.com>, method=CRAM-MD5, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, TLS, session=<pHVeOxC2HzZNFv7P> Dez 10 00:18:14 vsrv10563 dovecot[17121]: imap-login: Disconnected: Inactivity (auth failed, 2 attempts in 180 secs): user=<test(a)example.com>, method=CRAM-MD5, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, TLS, session=<J6ZXOxC2OTZNFv7P> Dez 10 00:18:14 vsrv10563 dovecot[17121]: imap-login: Disconnected: Inactivity (auth failed, 2 attempts in 180 secs): user=<user(a)example.com>, method=CRAM-MD5, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, TLS, session=<oUFXOxC2ATZNFv7P> Dez 10 04:00:22 vsrv10563 dovecot[17121]: imap-login: Login: user=<test(a)example.com>, method=PLAIN, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, mpid=24532, TLS, session=<QYSEXxO2DzZNFv7P> Dez 10 04:03:06 vsrv10563 dovecot[17121]: imap-login: Disconnected: Inactivity during authentication (auth failed, 2 attempts in 180 secs): user=<info(a)example.com>, method=CRAM-MD5, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, TLS, session=<fo2FXxO2BDZNFv7P> Dez 10 04:03:07 vsrv10563 dovecot[17121]: imap-login: Disconnected: Inactivity during authentication (auth failed, 2 attempts in 180 secs): user=<user(a)example.com>, method=CRAM-MD5, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, TLS, session=<ekWNXxO2VTZNFv7P> Dez 10 04:03:09 vsrv10563 dovecot[17121]: imap-login: Disconnected: Inactivity during authentication (auth failed, 2 attempts in 180 secs): user=<user(a)example.com>, method=CRAM-MD5, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, TLS, session=<YE6sXxO2HTZNFv7P> Then fail2ban block the IP. Has anybody similar problems? This there a way to fix this? Thunderbird does not have this problem. Best Regards,

1 0

Standalone Directors
by William Edwards 11 Dec '20

11 Dec '20

Situation: We will be switching to Dovecot proxy + Director with three email clusters - each cluster will host different email domains and users - with CephFS storage. Problem: A Director instance has one 'director_mail_servers' setting, meaning I could only use one set of email servers, while the set of email servers in the cluster depends on the client's domain. (The reason I use Dovecot proxy is so people can use the same IMAP/POP/SMTP hostnames; regardless of which email server / email cluster they're hosted on.) Question: Is it possible to set 'director_mail_servers' based on the client's email domain? Met vriendelijke groeten, William Edwards

2 2

problems after upgrade from 2.2.27 to 2.3.4.1
by Lampa 09 Dec '20

09 Dec '20

Hello, after debian version from 9 to, also dovecot was upgraded. There was problems with right imap and imap-login connection settings. I adjusted process_limit, service count increased /proc/sys/net/core/somaxconn from 128 to 1024 for imap It's a system with 1000+ imap and 200+ pop3 connections. When imap connections are over 1000 problems begins. Problem one: 2020-12-07T12:46:39.575586+01:00 vhermes dovecot: master: Error: service(pop3): Initial status notification not received in 30 seconds, killing the process 2020-12-07T12:46:39.576448+01:00 vhermes dovecot: pop3: Fatal: master: service(pop3): child 13975 killed with signal 9 2020-12-07T12:46:42.015726+01:00 vhermes dovecot: master: Error: service(lmtp): Initial status notification not received in 30 seconds, killing the process 2020-12-07T12:46:42.016680+01:00 vhermes dovecot: lmtp: Fatal: master: service(lmtp): child 13985 killed with signal 9 2020-12-07T12:46:42.061963+01:00 vhermes dovecot: master: Error: service(lmtp): Initial status notification not received in 30 seconds, killing the process 2020-12-07T12:46:42.062973+01:00 vhermes dovecot: lmtp: Fatal: master: service(lmtp): child 13987 killed with signal 9 problem two: 2020-12-07T13:55:43.106017+01:00 vhermes dovecot: pop3: Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Resource temporarily unavailable 2020-12-07T13:56:22.300893+01:00 vhermes dovecot: lmtp: Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Resource temporarily unavailable 2020-12-07T13:58:11.721892+01:00 vhermes dovecot: imap: Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Resource temporarily unavailable problem three - lot of 2020-12-07T10:16:24.773347+01:00 vhermes dovecot: imap-login: Error: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable problem four - crashing 020-12-09T07:53:26.914331+01:00 vhermes dovecot: imap(user@domain)<5426><cv8ehAK2npZX7MQb>: Panic: file message-parser.c: line 174 (message_part_finish): assertion failed: (ctx->nested_parts_count > 0) 2020-12-09T07:53:26.916771+01:00 vhermes dovecot: imap(user@domain)<5426><cv8ehAK2npZX7MQb>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xdb62b) [0x7f31bb0d462b] -> /usr/lib/dovecot/libdovecot.so.0(+0xdb6c1) [0x7f31bb0d46c1] -> /usr/lib/dovecot/libdovecot.so.0(+0x4a149) [0x7f31bb043149] -> /usr/lib/dovecot/libdovecot.so.0(+0x474ac) [0x7f31bb0404ac] -> /usr/lib/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x104) [0x7f31bb0bc844] -> /usr/lib/dovecot/libdovecot.so.0(message_search_msg+0xa8) [0x7f31bb0bedf8] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xcf89e) [0x7f31bb25789e] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_search_args_foreach+0x45) [0x7f31bb1d9445] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xd0774) [0x7f31bb258774] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xd1a68) [0x7f31bb259a68] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x61) [0x7f31bb25a0e1] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x28) [0x7f31bb1e2e58] -> dovecot/imap [user@domain 1.2.3.4 UID SORT](+0x2691f) [0x559347dc891f] -> dovecot/imap [user@domain 1.2.3.4 UID SORT](command_exec+0x70) [0x559347dc1d80] -> dovecot/imap [user@domain 1.2.3.4 UID SORT](+0x25ed2) [0x559347dc7ed2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0x111) [0x7f31bb0ea8f1] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd0) [0x7f31bb0ec070] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7f31bb0eab7c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7f31bb0eace0] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f31bb06b0d3] -> dovecot/imap [user@domain 1.2.3.4 UID SORT](main+0x325) [0x559347db2bf5] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f31bae5609b] -> dovecot/imap [user@domain 1.2.3.4 UID SORT](_start+0x2a) [0x559347db2d8a] 2020-12-09T07:53:26.917634+01:00 vhermes dovecot: imap(user@domain)<5426><cv8ehAK2npZX7MQb>: Fatal: master: service(imap): child 5426 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) Seems that last problem is solved (if same) https://github.com/dovecot/core/commit/a668d767a710ca18ab6e7177d8e8be22a6b0… Thank you for any help -- Lampa

2 2

Question about login_log_format_elements in a proxy environment
by Adi Pircalabu 08 Dec '20

08 Dec '20

Hi, I have a Dovecot proxy setup with several proxy machines (currently running 2.3.11.3) in front of the real Dovecot servers (2.3.10.1) storing the mailboxes. "doveconf -a | egrep lip" returns: login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> In the real server maillog I'm expecting to have "lip" replaced with the IP address of the proxy. It works as expected for imap-login processes, however for pop3-login processes I still see the real server IP instead of the proxy IP. Ideas? Regards, -- Adi Pircalabu

2 8

Fts solr add fields message-id, date, in-reply-to
by michael1970 08 Dec '20

08 Dec '20

Hi, how can I add fields message-id, date, in-reply-to to fts solr index like hdr,body,subject or to? Thanks, Michael -- Sent from: http://dovecot.2317879.n4.nabble.com/

3 6

dovecot/imap killed with signal 6 after SEARCH in specific mailbox
by Jiri 07 Dec '20

07 Dec '20

Hi All, on my older production server (Deb9 dovecot version 2.2.27-3+deb9u6) a client reported that searching text in one mailbox failed while other mailboxes do search ok. He is using Rouddcube webmail and is searching the whole messages including the body. Errorlog shows panic and assertion failed logs. So I'v moved the 'problematic' mailbox to my latest production server (Deb10 2.3.4.1-5+deb10u4 = 2.3.4.1 (f79e8e7e4)) where I have more RAM to eliminate that and the same error appeared. There is nothing special about the mailbox, roughly 600MiB and 2200 messges. Other much larger mailboxes on the same server do search fine. After turning on imap logging in Roundcube mail, the critical command was: A0004 UID SEARCH RETURN (ALL) TEXT whatever I increased default_process_limit and default_client_limit, I run: doveadm index -u ttt(a)mail2.swpraha.cz -q INBOX but didn't help. I used the gdb method to reproduce it and to get the whole info including backtrace: vmail@s6mail:~$ gdb --args /usr/lib/dovecot/imap -u ttt(a)mail2.swpraha.cz (gdb) r Starting program: /usr/lib/dovecot/imap -u ttt(a)mail2.swpraha.cz process 4458 is executing new program: /usr/bin/doveconf process 4458 is executing new program: /usr/lib/dovecot/imap * PREAUTH [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY LITERAL+ NOTIFY SPECIAL-USE QUOTA] Logged in as ttt(a)mail2.swpraha.cz a select INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $MDNSent Junk $Forwarded NonJunk) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft $MDNSent Junk $Forwarded NonJunk \*)] Flags permitted. * 682 EXISTS * 0 RECENT * OK [UNSEEN 639] First unseen. * OK [UIDVALIDITY 1147771637] UIDs valid * OK [UIDNEXT 104487] Predicted next UID * OK [HIGHESTMODSEQ 53108] Highest a OK [READ-WRITE] Select completed (0.002 + 0.000 + 0.001 secs). A0004 UID SEARCH RETURN (ALL) TEXT whatewer imap(ttt(a)mail2.swpraha.cz)<4458><Auy4NnMnzl9qEQAAevFY8w>: Panic: file message-parser.c: line 174 (message_part_finish): assertion failed: (ctx->nested_parts_count > 0) imap(ttt(a)mail2.swpraha.cz)<4458><Auy4NnMnzl9qEQAAevFY8w>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xdb62b) [0x7ffff7dbb62b] -> /usr/lib/dovecot/libdovecot.so.0(+0xdb661) [0x7ffff7dbb661] -> /usr/lib/dovecot/libdovecot.so.0(+0x4a149) [0x7ffff7d2a149] -> /usr/lib/dovecot/libdovecot.so.0(+0x474ac) [0x7ffff7d274ac] -> /usr/lib/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x104) [0x7ffff7da3844] -> /usr/lib/dovecot/libdovecot.so.0(message_search_msg+0xa8) [0x7ffff7da5df8] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xcf89e) [0x7ffff7f3e89e] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_search_args_foreach+0x45) [0x7ffff7ec0445] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xd0774) [0x7ffff7f3f774] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xd1a68) [0x7ffff7f40a68] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x10d) [0x7ffff7f4118d] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x28) [0x7ffff7ec9e58] -> /usr/lib/dovecot/imap [ttt(a)mail2.swpraha.cz UID SEARCH](+0x2691f) [0x55555557a91f] -> /usr/lib/dovecot/imap [ttt(a)mail2.swpraha.cz UID SEARCH](command_exec+0x70) [0x555555573d80] -> /usr/lib/dovecot/imap [ttt(a)mail2.swpraha.cz UID SEARCH](+0x25ed2) [0x555555579ed2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0x111) [0x7ffff7dd18f1] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd0) [0x7ffff7dd3070] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7ffff7dd1b7c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7ffff7dd1ce0] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7ffff7d520d3] -> /usr/lib/dovecot/imap [ttt(a)mail2.swpraha.cz UID SEARCH](main+0x325) [0x555555564bf5] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7ffff7b3c09b] -> /usr/lib/dovecot/imap [ttt(a)mail2.swpraha.cz UID SEARCH](_start+0x2a) [0x555555564d8a] Program received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt full #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 set = {__val = {0, 9355454118400172544, 1928, 1862, 1863, 93824992506008, 65, 140737352109185, 140737351192526, 140737351951989, 257, 145, 206158430224, 140737488344944, 140737488344736, 140737351756174}} pid = <optimized out> tid = <optimized out> ret = <optimized out> #1 0x00007ffff7b3a535 in __GI_abort () at abort.c:79 save_stage = 1 act = {__sigaction_handler = {sa_handler = 0x9ef, sa_sigaction = 0x9ef}, sa_mask = {__val = {30216, 93824992300426, 0, 513, 513, 140737351192526, 140737351744763, 140737351192526, 9355454118400172544, 140737351192526, 140737351951234, 140737488344944, 93824992503880, 140737351192526, 140737351951609, 140737351192526}}, sa_flags = -136625910, sa_restorer = 0x5} sigs = {__val = {32, 0 <repeats 15 times>}} #2 0x00007ffff7d2a481 in ?? () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #3 0x00007ffff7dbb661 in default_fatal_handler () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #4 0x00007ffff7d2a149 in i_panic () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #5 0x00007ffff7d274ac in ?? () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #6 0x00007ffff7da3844 in message_parser_parse_next_block () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #7 0x00007ffff7da5df8 in message_search_msg () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #8 0x00007ffff7f3e89e in ?? () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #9 0x00007ffff7ec0445 in mail_search_args_foreach () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #10 0x00007ffff7f3f774 in ?? () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #11 0x00007ffff7f40a68 in ?? () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #12 0x00007ffff7f4118d in index_storage_search_next_nonblock () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #13 0x00007ffff7ec9e58 in mailbox_search_next_nonblock () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #14 0x000055555557a91f in ?? () No symbol table info available. #15 0x0000555555573d80 in command_exec () No symbol table info available. #16 0x0000555555579ed2 in ?? () No symbol table info available. #17 0x00007ffff7dd18f1 in io_loop_handle_timeouts () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #18 0x00007ffff7dd3070 in io_loop_handler_run_internal () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #19 0x00007ffff7dd1b7c in io_loop_handler_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #20 0x00007ffff7dd1ce0 in io_loop_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #21 0x00007ffff7d520d3 in master_service_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #22 0x0000555555564bf5 in main () No symbol table info available. (gdb) ========================== dovecot -n: # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 5.4.65-1-pve x86_64 Debian 10.6 # Hostname: s6mail.ehosting.cz default_client_limit = 10000 default_process_limit = 1000 deliver_log_format = msgid=%m, from=%f, Subj=%s: %$ dict { expire = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no first_valid_gid = 150 first_valid_uid = 150 last_valid_gid = 150 last_valid_uid = 150 log_timestamp = "%Y-%m-%d %H:%M:%S " mail_plugins = quota trash expire mail_privileged_group = vmail 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 spamtest spamtestplus namespace inbox { inbox = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } 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-sql.conf.ext driver = sql } plugin { antispam_backend = pipe antispam_crm_binary = /bin/false antispam_dspam_args = --deliver=;--user;%u;--source=error;--signature=%%s antispam_dspam_binary = /usr/bin/dspam antispam_dspam_notspam = --class=innocent antispam_dspam_result_header = X-DSPAM-Result antispam_dspam_spam = --class=spam antispam_pipe_program = /usr/local/bin/postfix/reclasify-from-dovecot antispam_pipe_program_args = %u;%d antispam_pipe_program_notspam_arg = --ham antispam_pipe_program_spam_arg = --spam antispam_pipe_tmpdir = /tmp antispam_signature = X-CRM114-CacheID antispam_signature_missing = error antispam_spam = Junk;Spam antispam_spool2dir_notspam = /tmp/spamspool/%%020lu-%u-%%05luh antispam_spool2dir_spam = /tmp/spamspool/%%020lu-%u-%%05lus antispam_trash = trash;Trash;Deleted Items;Deleted Messages antispam_verbose_debug = 0 expire = Trash expire2 = Trash/* expire3 = Spam expire_dict = proxy::expire quota = dict:User quota::proxy::quota quota_exceeded_message = Uzivatel %u ma zaplnenou schranku. quota_rule = *:storage=1G quota_rule2 = Trash:storage=+100M sieve = file:~/sieve;active=~/.dovecot.sieve sieve_after = /etc/dovecot/sieve_after sieve_before = /etc/dovecot/sieve_before sieve_extensions = +spamtest +spamtestplus sieve_spamtest_max_value = 15 sieve_spamtest_status_header = X-Spam-Level sieve_spamtest_status_type = strlen trash = /etc/dovecot/dovecot-trash.conf.ext } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = UID%u-%v postmaster_address = sysadmin(a)ehosting.cz protocols = " imap lmtp sieve pop3" service auth-worker { user = $default_internal_user } service dict { unix_listener dict { user = vmail } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } user = vmail } service stats { unix_listener stats-writer { user = vmail } } ssl_cert = </etc/dovecot/private/dovecot.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it syslog_facility = local0 userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lmtp { mail_plugins = quota trash expire sieve quota trash expire } protocol lda { mail_plugins = quota trash expire sieve } protocol imap { mail_plugins = quota trash expire antispam imap_quota } ========================== The dovecot.err shows the two mentioned error lines (Panic:, Error:) plus: Dec 7 13:12:21 s6mail dovecot: imap(ttt(a)mail2.swpraha.cz)<13466><wezwvN61RK0AAAAAAAAAAAAAAAAAAAAB>: Fatal: master: service(imap): child 13466 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) Please let me know if you need any other details. Thanks for any suggestion --Jiri Kacena

2 2

logging in to postfixadmin failed probably because of a dovecot error
by peacecop kalmer: 07 Dec '20

07 Dec '20

I can’t log in to postfixadmin anymore. It says that the username or password is incorrect. It can’t be incorrect as I’ve stored them in Google and “Chrome”. I have two admin accounts and none of them can’t be used for logging in. So I changed the main password with “setup.php” and copied that hash into the configuration file. Then, I deleted one of the admin accounts directly in the database from the table “admin”. Finally, I tried to recreate that deleted admin account using “setup.php”. I get the following error message: “can’t encrypt password with dovecotpw, see error log for details”. I had a look into the error log file of postfixadmin and found these complaints: [Wed Dec 02 02:33:37.551048 2020] [authz_core:debug] [pid 30540] mod_authz_core.c(809): [client 192.168.1.65:54948] AH01626: authorization result of Require all granted: granted, referer:https://postfixadmin.tennis24.ee/setup.php [Wed Dec 02 02:33:37.551070 2020] [authz_core:debug] [pid 30540] mod_authz_core.c(809): [client 192.168.1.65:54948] AH01626: authorization result of : granted, referer:https://postfixadmin.tennis24.ee/setup.php [Wed Dec 02 02:33:37.551280 2020] [php7:warn] [pid 30540] [client 192.168.1.65:54948] PHP Warning: Cannot assign an empty string to a string offset in /usr/share/postfixadmin/variables.inc.php on line 31, referer:https://postfixadmin.tennis24.ee/setup.php [Wed Dec 02 02:33:37.568128 2020] [php7:notice] [pid 30540] [client 192.168.1.65:54948] dovecotpw password encryption failed., referer:https://postfixadmin.tennis24.ee/setup.php [Wed Dec 02 02:33:37.568155 2020] [php7:notice] [pid 30540] [client 192.168.1.65:54948] STDERR output: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 13: ssl_cert: Can't open file /etc/letsencrypt/live/test.tennis24.ee/fullchain.pem: Permission denied\n, referer:https://postfixadmin.tennis24.ee/setup.php [Wed Dec 02 02:33:37.568897 2020] [deflate:debug] [pid 30540] mod_deflate.c(854): [client 192.168.1.65:54948] AH01384: Zlib: Compressed 1320 to 732 : URL /setup.php, referer:https://postfixadmin.tennis24.ee/setup.php Is the issue connected to the permission problem? If so why is the permission denied? I can't even receive any mails to the address kalmer(a)test.tennis24.ee anymore. If I send out it works fine but no mail arrives. -- *peacecop kalmer:* *Instituudi tee 3-27 * *76902 * *Harku * *Harku* *Harjumaa* Estonia *+372 652 4228 * *+372 5620 4556 * *__________________________________________________________________ *

2 1

http pipelining on auth_policy_server
by Adrian M 07 Dec '20

07 Dec '20

Hi, I'm curious to know if dovecot can be configured to do pipelining for auth_policy in order to use less connection to the server and keep them for longer. I'm working on making a small policy server and the lack of persistent connections is a cause of overhead. Thank you !

2 2

[patch] enhancement for adding limits to solr and tika parsing
by John Fawcett 07 Dec '20

07 Dec '20

Hi As mentioned in a previous thread, the solr + tika combination has caused me some issues due to attachment size. While tika seems to be able to parse large attachments, the resulting volume of text can overwhelm the solr server. One solution would be to throw resources at the problem, but in my case such large attachments don't contain anything worthwile indexing. Additionally I don't want people to be able to randomly crash my solr server by sending large compressed attachments that expand into huge volumes for solr. It's also a safety feature to have sane limits on what can be indexed. Attached is a first attempt to address the problem. I did not find a way to easily get actual attachment sizes, so I used an already available information - the overall message size. It may not be ideal but at least introduces limits where none existed. I have introduced two new parameters for the plugin section, for example: plugin { fts_max_size = 2M fts_max_size_tika = 1M } They can be used separately or together. Both sizes refer to the overall message size. The meaning is: fts_max_size - do not parse message bodies if the message size exceeds this value. A value of 0 indicates no limit. If the message body is not parsed, attachments are also not parsed. fts_max_size_tika - do not parse message attachments with tika if the message size exceeds this value. A value of 0 indicates no limit. If using both settings it makes sense to have fts_max_size > fts_max_size_tika, since with a smaller fts_max_size bodies are not indexed including attachments and the fts_max_size_tika will have no effect. The difference (ft_max_size - fts_max_size_tika) places an upper bound on the size of the non attachment body text that will be indexed. However, any attachments over the fts_size will automatically consume this limit and no body text will be indexed for those messages. I've only updated the tika parser not the script parser though the script parser potentially could benefit from this approach. The attached patch also includes the rolled up patch for using basic auth with the tika server and the previous posted patch (not mine) which solves an assert when using solr and tika together. John

1 0

Re: Re: Re: Dovecot+Solr+Tika segmentation fault
by Manuel Josupeit-Walter 07 Dec '20

07 Dec '20

>>> A fix was posted on this list which seems to avoid segfaults when >>> using solr+tika. I reposted it not long ago in response to another >>> question. Before exploring the other segfaults it would be worthwhile >>> getting that fix. If other segfaults continue then I suggest posting >>> the logging from Dovecot >> >> https://github.com/dovecot/core/commit/043d111cea78533cf22d3bfe0872c8376d84… >> (DOV-4090) >> >> Scheduled for 2.3.13. > > I applied the fix and will observe it for the next couple of days. Unfortunately, the issue still persists even with this patch. The log message is slightly different, though, regarding disconnection: Dec 03 17:10:49 server.name tika[988]: INFO tika/ (application/pdf) Dec 03 17:10:49 server.name tika[988]: INFO tika/ (image/png) Dec 03 17:10:49 server.name kernel: indexer-worker[15805]: segfault at 0 ip 00007f140483db64 sp 00007ffc04fa7960 error 4 in libdovecot.so.0.0.0[7f14047f3000+db000] Dec 03 17:10:49 server.name kernel: Code: 89 f5 48 8d b8 f0 01 00 00 48 8b 52 08 4c 8b 62 48 e8 90 89 fb ff 48 8b 44 24 08 be 00 20 00 00 4c 89 ef 48 8b 80 10 01 00 00 <4c> 8b 38 e8 64 b2 fb ff 48 8b 44 24 0 Dec 03 17:10:49 server.name dovecot[988]: Dec 03 16:10:49 indexer: Error: Indexer worker disconnected, discarding 1 requests for username_stripped Dec 03 17:10:49 server.name dovecot[988]: Dec 03 16:10:49 indexer-worker(username_stripped)<1952><Ed3ek5G1BMQgARa4EL8DAKGMINRlZjjS:c+gACAkOyV+gBwAAhFs1yA>: Fatal: master: service(indexer-worker): child 1952 killed It seems that there is something else going wrong in this version. Best, Manuel

3 3