- dovecot - dovecot.org

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