- dovecot - dovecot.org

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 02 Jan '22

02 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

spf helo pass
by Benny Pedersen 02 Jan '22

02 Jan '22

would be nice to see added :=) talvi.dovecot.org txt "spfv1 a -all"

5 13

auth crashes when oauth2 passdb is enabled
by Sebastiano Degan 01 Jan '22

01 Jan '22

I've enabled both sql and oauth2 passdb, regardless of the method used by the client, I get the following error: Jan 1 15:38:56 mail dovecot[52828]: auth: Panic: file http-client.c: line 646 (http_client_context_close): assertion failed: (cctx->clients_list == NULL) Jan 1 15:38:56 mail dovecot[52826]: master: Error: service(auth): command startup failed, throttling for 2.000 secs Jan 1 15:38:56 mail dovecot[52828]: auth: Fatal: master: service(auth): child 52840 killed with signal 6 (core dumped) Jan 1 15:38:56 mail dovecot[52828]: imap-login: Disconnected: Auth process broken (disconnected before auth was ready, waited 0 secs): user=<>, rip=192.168.1.104, lip=192.168.1.101, TLS, session=<QW7rFYfUgcTAqAFo> If I remove the oauth2 passdb, there are no problems. This is the output of dovecot -n: # 2.3.17 (e2aa53df5b): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.17 (054dddfa) # OS: FreeBSD 13.0-RELEASE-p4 amd64 nullfs # Hostname: localhost auth_mechanisms = plain login oauthbearer xoauth2 default_internal_user = vmail first_valid_uid = 0 hostname = ***DELETED*** mail_location = maildir:/data/mailboxes/%d/%n mail_plugins = " fts fts_solr" 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 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 Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { args = /usr/local/etc/dovecot/dovecot-oauth2.conf.ext driver = oauth2 mechanisms = xoauth2 oauthbearer } plugin { antispam_backend = pipe antispam_mail_notspam = learn_ham antispam_mail_sendmail = /usr/bin/rspamc antispam_mail_sendmail_args = -h;localhost:11334 antispam_mail_spam = learn_spam antispam_spam = Junk antispam_trash = Trash fts = solr fts_solr = url=http://localhost:8983/solr/dovecot sieve = ~/.dovecot.sieve sieve_before = /etc/dovecot/sieve/before.d sieve_dir = ~/sieve } postmaster_address = ***DELETED*** protocols = imap lmtp sieve pop3 service auth-worker { unix_listener auth-worker { user = vmail } } service auth { inet_listener { port = 1666 } unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } user = vmail } service imap-login { inet_listener imap { port = 0 } } service lmtp { inet_listener lmtp { port = 24 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } user = vmail } service pop3-login { inet_listener pop3 { port = 0 } } ssl = required ssl_cert = </usr/local/etc/letsencrypt/live/***DELETED***/fullchain.pem ssl_key = # hidden, use -P to show it userdb { args = uid=vmail gid=vmail home=/data/mailboxes/%d/%n driver = static } protocol lda { mail_plugins = " fts fts_solr sieve" } protocol imap { mail_plugins = " fts fts_solr imap_sieve" } protocol lmtp { mail_plugins = " fts fts_solr sieve" postmaster_address = ***DELETED*** }

1 0

Add arm64 support to docker image
by alpe 01 Jan '22

01 Jan '22

I think the issue is here: ADD https://github.com/krallin/tini/releases/download/v0.19.0/tini /sbin/tini # buildkit tini has arm64 (and others) version. So it should be easy to make the container work with arm.

1 0