- dovecot - dovecot.org

Re: Expunged message reappeared
by Claudio Corvino 05 Jan '22

05 Jan '22

Hi Alex, thanks for your answer, I think this could be related to Dovecot version in use, in our case it is the same: 2.3.4.1 (f79e8e7e4). It could be useful to know if someone can confirm this assumption so we can try an upgrade to the latest version hoping this could solve our issue. Regards On 07/12/21 08:36, Joelly Alexander wrote: > > Don't have the issue with duplicate logs but same problem with > re-appearing of deleted messages very often in a two node setup with > dsync replication. > Messages sometimes have to be deleted multiple times until they stay > in the thrash folder. > > Running dovecot version 2.3.4.1 (f79e8e7e4) > > When i 'move' messages to the Trash folder they seem to stay there but > when i delete them they usually come back. > > Alex > > On 12/3/21 5:53 PM, Claudio Corvino wrote: >> >> I forgot to mention that sometimes users receive duplicate messages >> and Dovecot log: >> >> Dec 3 10:16:12 xxx dovecot: >> lmtp(xxx@xxx)<13468><OOFDAlXgqWGcNAAAIQnY6g:12>: Warning: >> /mnt/mail-storage-lv0007/xxx/Maildir/dovecot-uidlist: Duplicate file >> entry at line 2072: 1638522075.M489729P12338.xxx,S=5854,W=5943 (uid >> 71164 -> 71166) >> >> Thanks >> >> Regars >> >> On 03/12/21 17:50, Claudio Corvino wrote: >>> >>> Hi, >>> >>> I have two IMAP/LMTP Dovecot server in replica (version 2.3.4.1), I >>> use LDAP/AD for /userdb, /replica is working, but sometimes I get >>> these errors into log: >>> >>> Dec 3 15:47:15 xxx dovecot: imap(xxx)<28251><TOSxmj7SPRYloY5/>: >>> Warning: Maildir /mnt/mail-storage-lv0007/xxx/Maildir: Expunged >>> message reappeared, giving a new UID (old uid=233140, >>> file=1638540323.M588041P27708.xxx,S=84376,W=85507:2,) >>> >>> The user delete the message and then the message reappears into mail >>> client after one second. >>> >>> Does anybody knows how can I fix it? >>> >>> Thanks in advance >>> >>> Regards >>> >>

2 3

how to delete attachment and replace some words in subject
by lujie 05 Jan '22

05 Jan '22

hi, all, I need to filter email as follow rules: 1, delete the attachments; 2, replace some word in subject with code; 3, redirect to other email with the modified subject and original text in body. sieve and exrprograms used in my script. But error in run sieve script while try to set body text , which contains invalid character "cr lf". Thanks. -- Best Regards, Jessica

2 1

Doveadm auth fails
by Ken Wright 05 Jan '22

05 Jan '22

I'm still troubleshooting a faulty email server, and got the following results when I tried doveadm: kwright@grace:/etc/dovecot/conf.d$ doveadm auth lookup me(a)mydomain.com Error: auth-master: passdb lookup(me(a)mydomain.com): Auth PASS lookup failed Error: passdb lookup failed for me(a)mydomain.com kwright@grace:/etc/dovecot/conf.d$ doveadm auth test me(a)mydomain.com Password: Error: auth-client: conn unix:/var/run/dovecot/auth-client: connect(/var/run/dovecot/auth-client) failed: Permission denied (euid=1000(kwright) egid=1000(kwright) missing +r perm: /var/run/dovecot/auth-client, dir owned by 0:0 mode=0755) kwright@grace:/etc/dovecot/conf.d$ ls -la /var/run/dovecot/auth-client srw------- 1 dovecot root 0 Jan 4 19:09 /var/run/dovecot/auth-client I see /var/run/dovecot/auth-client only has read and write permissions for the owner and nothing for anyone else. Is this part of my problem? Ken

2 3

Re: Error: fts_solr: received invalid uid
by oliver.krone＠snoog.ch 04 Jan '22

04 Jan '22

Here is what solr sends to dovecot, the offending uid in this exmaple is '21' { "responseHeader":{ "status":0, "QTime":1, "params":{ "q":"body:Zeitserver"}}, "response":{"numFound":1,"start":0,"numFoundExact":true,"docs":[ { "uid":[21], "box":["2e60f3054059c95fbf580600eb1947e0"], "user":["oliver.krone(a)snoog.ch"], "id":"21/2e60f3054059c95fbf580600eb1947e0/oliver.krone(a)snoog.ch", "body":[" ... "], "hdr":[" ... "], "from":["..."], "subject":["..."], "to":["..."], "_version_":1720682332306800640}] }} Oliver >> I'm using dovecot 2.3.13,? solr 8.x. and roundcube 1.5.1. However when >> I do a search I get the the Error: fts_solr: received invalid uid, >> search results are ok. >> >> Thanks > Presumably one of the uid returned from solr could not be decoded (i.e. > converted to an int). The offending uid should have been printed as > part > of the message. If you need to get more info you could investigate what > is being returned by solr running the exact same query from a browser > if > you're able to retrieve it from the solr log. > > Alternatively you could set rawlog_dir in the fts_solr dovecot settings > and then look at what is being sent back from solr in the .in file that > is logged. > > https://doc.dovecot.org/settings/plugin/fts-solr-plugin/?highlight=fts%20do… > > John

3 2

Client Passdb out
by Ken Wright 03 Jan '22

03 Jan '22

I've been trying to log into Dovecot without success, and this is what I found in /var/log/mail.log: Jan 3 02:47:33 grace dovecot: auth: Debug: client passdb out: FAIL#0111#011user=me(a)mydomain.com Jan 3 02:47:33 grace dovecot: imap-login: Disconnected (auth failed, 1 attempts in 6 secs): user=<me(a)mydomain.com>, method=PLAIN, rip=192.168.1.1, lip=192.168.1.10, TLS, session=<bgBsu6jUhqzAqAEB> I know I provided the correct password, but I'm still having no joy. Ken

2 1

Re: Error: fts_solr: received invalid uid (John Fawcett)
by oliver.krone＠snoog.ch 03 Jan '22

03 Jan '22

Hi John, You are right this was not a dovecot solr query. It is really strange everything seems to work with Dovecot 2.3.4. E.g. search and rebuilding index from scratch using doveadm. As soon as I use version 2.3.13 things are getting wild: dovecot crashed when I re-scan the index using doveadm and search does not work anymore, after re-scan: Panic: file http-client-request.c: line 1240 (http_client_request_send_more): assertion failed: (req->payload_input != NULL) doveadm(krone(a)invectrix.ch): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7fc54cace4e2] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7fc54cace5fe] -> /usr/lib/dovecot/libdovecot.so.0(+0xfc49b) [0x7fc54cada49b] -> /usr/lib/dovecot/libdovecot.so.0(+0xfc4d1) [0x7fc54cada4d1] -> /usr/lib/dovecot/libdovecot.so.0(+0x53aee) [0x7fc54ca31aee] -> /usr/lib/dovecot/libdovecot.so.0(+0x4aec2) [0x7fc54ca28ec2] -> /usr/lib/dovecot/libdovecot.so.0(http_client_connection_output+0xee) [0x7fc54ca7ebde] -> /usr/lib/dovecot/libdovecot.so.0(+0x122171) [0x7fc54cb00171] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7fc54caeff59] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x132) [0x7fc54caf1592] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) [0x7fc54caf0000] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7fc54caf01c0] -> /usr/lib/dovecot/libdovecot.so.0(+0x9c4cd) [0x7fc54ca7a4cd] -> /usr/lib/dovecot/libdovecot.so.0(http_client_request_finish_payload+0x2c) [0x7fc54ca7a6dc] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0xf243) [0x7fc54c0a6243] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(fts_parser_more+0x25) [0x7fc54c0a5345] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0xbfcf) [0x7fc54c0a2fcf] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(fts_build_mail+0xa27) [0x7fc54c0a3a87] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0x11f0b) [0x7fc54c0a8f0b] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_precache+0x2e) [0x7fc54cbf14ae] -> doveadm(+0x3761f) [0x55d18bdbf61f] -> doveadm(+0x31bad) [0x55d18bdb9bad] -> doveadm(+0x32860) [0x55d18bdba860] -> doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x22d) [0x55d18bdbb4ad] -> doveadm(doveadm_cmd_run_ver2+0x4c8) [0x55d18bdcbb88] -> doveadm(doveadm_cmd_try_run_ver2+0x3a) [0x55d18bdcbbda] -> doveadm(main+0x1d0) [0x55d18bdaa450] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) [0x7fc54c69fd0a] -> doveadm(_start+0x2a) [0x55d18bdaa92a] and solr: 2022-01-03 00:13:20.829 ERROR (qtp1991278377-21) [ x:dovecot] o.a.s.s.HttpSolrCall null:[com.ctc.wstx.exc.WstxLazyException] com.ctc.wstx.exc.WstxIOException: Early EOF .... Caused by: org.eclipse.jetty.io.EofException: Early EOF at org.eclipse.jetty.server.HttpInput$3.getError(HttpInput.java:1143) at org.eclipse.jetty.server.HttpInput$3.noContent(HttpInput.java:1131) at org.eclipse.jetty.server.HttpInput.read(HttpInput.java:318) Seems like dovecot is sending an empty query? Oliver > > Hi Oliver > > unless I'm missing something that doesn't look like the type of query > dovecot launches - dovecot sends various parameters including the > request for xml results. The thing that looks odd to me is that the > results fields should be single values not arrays enclosed in [], ie I > would have expected > > "uid":21, > > instead of > > "uid":[21], > > I'd be interested to see the equivalent xml output produced by running > a > query that dovecot sends. > > John >

2 2

Can't connect to database
by Ken Wright 03 Jan '22

03 Jan '22

Dovecot has been giving me problems for the past week or so. Today the error log showed me this: Jan 2 13:33:39 grace dovecot: auth-worker(3250): Error: mysql(localhost): Connect failed to database (postfix): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) - waiting for 5 seconds before retry The socket is there, showing full permissions (rwx for owner, group, and rest of the universe) so I can't understand why dovecot can't connect. Is there anyone who can help? Ken

3 3

master: service(imap): child xxxx killed with signal 11
by Lukas Matasovsky 02 Jan '22

02 Jan '22

Dear Maintainer, I have several dovecot installations, all of them stopped working with the upgrade from .16 to .17. Maybe I am missing something, or it's a bug. All I can see is a signal 11 after each login attempt. Attached you can find a sysreport plus a core dump, both from different states of configuration (I reverted the core-dump settings later on) of the same server, but the effect has been the same ever since upgrading. I have other servers that use pam (not mariadb) and local maildirs that show the same behavior. For now, I have downgraded all servers, if needed I could run some more tests. Thank you for checking & cheers, Lukas

2 3

Dovecot Docker Image Volumes
by Thomas Bellebaum 02 Jan '22

02 Jan '22

Hello there and happy new year, I have a question/request regarding the Docker Image hosted at https://hub.docker.com/r/dovecot/dovecot. The Dockerfile itself declares two volumes: - `/etc/dovecot` for configuration data - `/srv/mail` for mail storage It seems inconvenient in some cases to have the image create these volumes, especially in case of the former. Consider a minimal Dockerfile like the following: ``` FROM dovecot/dovecot:latest COPY dovecot.conf /etc/dovecot/dovecot.conf ``` This creates a new image building on top of the official one, which has statically configured configuration, and thus does not need to save its config in a volume. Yet currently, since the base image exports volumes, a config volume is created. A user might also choose to save mail in a different directory or even in a remote SQL database, rendering the second volume unnecessary. I would like to know a bit about the reasons for declaring the volumes, and suggest removing the line, should this be an option. Some impact considerations: - Removing the volumes for future image versions will not impact existing deployments building on tags other than `latest`. - As the default (example) configuration is not very useful for non-test-setups, most people have probably assigned the config volume explicitly, e.g. using docker's `-v` option. These people will also not be affected. - The description explicitly states to mount `/srv/mail/`, but some people might rely on the the automatic volume creation nonetheless. - Some obscure proprietary scripts may rely on the current behavior. In any case, if the volumes are no longer declared, the image description should mention that the mail storage location (the default being `/var/mail`) must be saved e.g. by using volumes, and probably also that the configuration is expected at `/etc/dovecot/dovecot.conf`. Stay healthy and have a nice day, -- Thomas Bellebaum <thomas(a)bellebaum.eu>

2 1

Permission denied
by Ken Wright 02 Jan '22

02 Jan '22

My server has been running just fine for over a year, until I upgraded PostfixAdmin and somehow messed things up. Now I can't log in, and my mail client (Evolution, if it matters) keeps popping up an authentication request. The server is Ubuntu 20.04, my Dovecot is version 2.3.7.2, and Evolution is 3.40.4-1. I've also tried logging in with Roundcube with no success. Any insight or suggestions will be gratefully received! Here's the most recent entry from /var/log/mail.err: Dec 28 22:05:02 grace dovecot: lmtp(me(a)mydomain.com)<910309><SOFiMl7Qy2Hl4w0AThsuZQ>: Error: lmtp- server: conn unix:pid=906625,uid=117 [6]: rcpt me(a)mydomain.com: Mailbox INBOX: open(/var/mail/vmail/me(a)mydomain.com/tmp/1640747102.M850878P910309.grac ) failed: Permission denied Any further information available upon request!

3 6