January 2022 - dovecot

FTS flatcurve not index messages when SEARCH run on Virtual Mailboxes
by Alessio Cecchi 18 Jan '22

18 Jan '22

Hi, I'm testing FTS flatcurve plugin in order to understand if I can switch from FTS Solr to flatcurve. In my configuration I have enabled Virtual mailboxes and for search in all folders I just SEARCH on Virtual/All folder. I this (virtual) folder is not indexed with FTS Solr Dovecot start to index it (or all real folders). But with FTS flatcurve when I SEARCH on Virtual/All for the first time the indexer process does not start and the search return empty. Only if I run manually "doveadm index -q -u alessio(a)email.net '*'" flatcurve find messages. Can flatcurve have the same feature as Solr for Virtual mailboxes? Here a sample of my configuration: namespace Virtual { hidden = yes list = no location = virtual:/etc/dovecot/virtual:INDEX=~/Maildir/virtual prefix = Virtual/ separator = / subscriptions = no } namespace inbox { [...] mailbox virtual/All { comment = All my messages special_use = \All } } # cat /etc/dovecot/virtual/All/dovecot-virtual * all Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

3 6

Extracting CLIENTID information from checkpassword or postlogin scripting
by Dan Conway 18 Jan '22

18 Jan '22

Hello, When extracting client_id information from the client connection (i.e. setting imap_id_log = *) the information is directly logged by Dovecot as such: ID sent: name=Thunderbird, version=91.5.0 My question is, Is it possible to export/set this information in a checkpassword script or a postlogin script? client_id If|imap_id_retain| <https://doc.dovecot.org/settings/core/#core_setting-imap_id_retain>is enabled this variable is populated with the client ID request as IMAP arglist. I've enabled both checkpassword and postlogin on a test server, as well as 'imap_id_retain' set to 'yes'. I wrote a simple Perl script that dumps everything in %ENV as well as @ARGV for checkpassword and postlogin, but I don't see any occurrences of ID information. I've also tried to see if I could supply that variable in dovecot.conf by setting 'client_id' as a parameter, but that didn't seem to do the trick either. passdb { ... # Doesn't work args = /usr/local/bin/checkpassword.pl client_id # Doesn't work args = /usr/local/bin/checkpassword.pl %{client_id} ... } What am I missing? Is it possible to get these variables into an external script that checkpassword or postlogin executes? Thanks.

3 2

Order of loading and checking userdb on Ubuntu
by Mike 16 Jan '22

16 Jan '22

When using the lmtp service for local delivery, I'd like to change the user lookup to only use the user portion of the email address. I think I do that in the 20-lmtp.conf file, but not exactly sure how. From what I've found on the web, I just need to change the auth_username_format=%n. I feel confident that I'm not doing it right. older posts implied that the order things are loaded is an issue, but not sure if that is the case anymore. My goal is to set username_format for only lmtp. Thanks for any help.

1 1

Wrong timestamp value in name of file
by Ervin Hegedüs 14 Jan '22

14 Jan '22

Hi there, Debian 10, Dovecot 2.3.4 (1:2.3.4.1-5+deb10u6), ext4 mailstore. A user on our server reorganized the sent items: he moved few items from the old sent folder into a new one. After that, he noticed me that he does not see every mail, but when he starts a search, then he finds it. I looked up the mail, and found this situation: # ls -la 1642152396.M997381P21341.mail2\,S\=473164\,W\=479469\:2\,S -rw-r--r-- 1 vmail vmail 473164 aug 24 10:21 '1642152396.M997381P21341.mail2,S=473164,W=479469:2,S' # grep Date '1642152396.M997381P21341.mail2,S=473164,W=479469:2,S' Date: Tue, 24 Aug 2021 10:21:39 +0200 # date -d @1642152396 Fri Jan 14 10:26:36 CET 2022 As you can see that mail had sent on 24 Aug, 2021, but after the reorganization it got a new timestamp with the date of today. I assume the client (iPhone) orders the mail by the name of files - am I right? Why did this happen? How can I fix that? I mean, is there any way to rename this files (a few hundred...) to the "real" timestamp? Thanks, a.

1 0

ssl=required per user?
by Arkadiusz Miśkiewicz 13 Jan '22

13 Jan '22

Can ssl=required be forced on per user setting? Right now I could modify password_query to check if %c (%{secured}) is empty and return appropriate error as "reason" like in https://doc.dovecot.org/configuration_manual/authentication/nologin/#authen… example. Unfortunately password_query is a bit too late. I would like to deny access as soon as possible, so just after user sends his login. (that won't help much in cases when client sends password early like "AUTH PLAIN b64loginpass" but will help in all other cases) user_query doesn't have this capability that password_query it seems. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

1 0

Is Diffie-Hellman needed?
by dovecot＠ptld.com 13 Jan '22

13 Jan '22

Is Diffie-Hellman needed on a modern new dovecot setup? ssl_dh is empty by default. Both ssl_cert and ssl_key on my setup are pointing to let's encrypt certs. However i see Diffie-Hellman related warnings in logs: dovecot[1073]: imap-login: Error: Diffie-Hellman key exchange requested, but no DH parameters provided. Set ssl_dh=</path/to/dh.pem Am i causing issues for some users by not setting up ssl_dh or is this something being phased out?

4 6

source code doesn't compile
by Ruben Safir 12 Jan '22

12 Jan '22

I downloaded the dovecot source and it doesn't compile. The install script fails in auth because it makes a file and then tries to make a directory over it make[2]: Entering directory '/home/ruben/src/dovecot-2.3.17.1/src/auth' make[3]: Entering directory '/home/ruben/src/dovecot-2.3.17.1/src/auth' /usr/bin/mkdir -p '/usr/local/lib/dovecot' /bin/sh ../../libtool --mode=install /usr/bin/install -c auth checkpassword-reply '/usr/local/lib/dovecot' libtool: warning: 'libstats_auth.la' has not been installed in '/usr/local/lib/dovecot/old-stats' libtool: install: /usr/bin/install -c .libs/auth /usr/local/lib/dovecot/auth libtool: install: /usr/bin/install -c .libs/checkpassword-reply /usr/local/lib/dovecot/checkpassword-reply /usr/bin/mkdir -p '/usr/local/lib/dovecot/auth' I am running an older version of dovecott and would really like to upgrade it and there is no package for this linux version -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and extermination camps, but incompatible with living as a free human being. -RI Safir 2013

7 14

Migrate mail_location
by hello＠reox.at 11 Jan '22

11 Jan '22

Hi! I have a dovecot installation, with the following configuration: mail_home = /var/vmail/%d/%n mail_location = maildir:~ I would like to migrate the mail_location to maildir:~/mail, to get around the issues described in the documentation. But I can not really find a good way to do that. I played around with doveadm sync/backup, but I can only copy everything into a new location (i.e. doveadm sync maildir:~/mail), but this does not really untangle the mail_home and location. My other idea was to migrate the maildir manually, i.e. move the maildir related folders and files (new, cur, tmp, all folders starting with a dot and containing itself {new,cur,tmp}, dovecot.* files, subscriptions file) into the ~/mail folder, but I'm not sure if this is a safe method. Is there any safe method to do this using dovecot tools? If the only way is a offline migration, I'm fine with that. Best, Sebastian

2 3

2.17.1 Fatal: master: service(doveadm): child 43879 killed with signal 6 (core dumped)
by Salatiel Filho 10 Jan '22

10 Jan '22

Hi, my dovecot 2.17.1 instance is crashing a lot. Quick question: The coredump should contain some private data, am I correct ? Assuming so, should it be posted on a public maillist? Panic: file dsync-ibc.c: line 166 (dsync_ibc_send_mail_request): assertion failed: (request->guid != NULL || request->uid != 0) ... Fatal: master: service(doveadm): child 43879 killed with signal 6 (core dumped) Using gdb/bt over the coredump I get: Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `dovecot/doveadm-server'. Program terminated with signal SIGABRT, Aborted. #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50 return ret; (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x00007f612d382db5 in __GI_abort () at abort.c:79 #2 0x00007f612db04485 in default_fatal_finish (status=0, type=LOG_TYPE_PANIC) at failures.c:459 #3 fatal_handler_real (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at failures.c:471 #4 0x00007f612dbb10f7 in i_internal_fatal_handler (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at failures.c:872 #5 0x00007f612db04126 in i_panic (format=format@entry=0x5641e4c16ba8 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:524 #6 0x00005641e4bcfcb2 in dsync_ibc_send_mail_request (ibc=0x5641e50a5990, request=0x5641e51dcc70) at dsync-ibc.c:166 #7 0x00005641e4bfe0bc in dsync_brain_send_mail_request (brain=0x5641e50a8538) at dsync-brain-mails.c:215 #8 dsync_brain_sync_mails (brain=brain@entry=0x5641e50a8538) at dsync-brain-mails.c:418 #9 0x00005641e4bf9ad8 in dsync_brain_run_real (changed_r=0x7ffcd2397a47, brain=0x5641e50a8538) at dsync-brain.c:716 #10 dsync_brain_run (changed_r=0x7ffcd2397a47, brain=0x5641e50a8538) at dsync-brain.c:749 #11 dsync_brain_run (brain=0x5641e50a8538, changed_r=0x7ffcd2397a47) at dsync-brain.c:737 #12 0x00005641e4bfa13e in dsync_brain_run_io (context=0x5641e50a8538) at dsync-brain.c:110 #13 0x00005641e4c0b3c3 in dsync_ibc_stream_input (ibc=0x5641e50a5990) at dsync-ibc-stream.c:232 #14 0x00007f612dbc78ad in io_loop_call_io (io=0x5641e5040510) at ioloop.c:737 #15 0x00007f612dbc8f19 in io_loop_handler_run_internal (ioloop=ioloop@entry=0x5641e4f89ce0) at ioloop-epoll.c:222 #16 0x00007f612dbc7950 in io_loop_handler_run (ioloop=0x5641e4f89ce0) at ioloop.c:789 #17 0x00007f612dbc7ad0 in io_loop_run (ioloop=0x5641e4f89ce0) at ioloop.c:762 #18 0x00005641e4bddafa in cmd_dsync_run_remote (user=<optimized out>, user=<optimized out>) at doveadm-dsync.c:496 #19 cmd_dsync_run (_ctx=0x5641e4f89fe8, user=<optimized out>) at doveadm-dsync.c:703 #20 0x00005641e4bdfc26 in doveadm_mail_next_user (ctx=0x5641e4f89fe8, error_r=0x7ffcd2397de8) at doveadm-mail.c:462 #21 0x00005641e4be0d74 in doveadm_mail_cmd_exec (wildcard_user=0x0, ctx=0x5641e4f89fe8) at doveadm-mail.c:654 #22 doveadm_cmd_ver2_to_mail_cmd_wrapper (cctx=<optimized out>) at doveadm-mail.c:983 #23 0x00005641e4bf17c7 in doveadm_cmd_run_ver2 (argc=argc@entry=10, argv=argv@entry=0x5641e4fa3788, cctx=cctx@entry=0x7ffcd2397f40) at doveadm-cmd.c:465 #24 0x00005641e4bf5d1a in doveadm_cmd_server_run_ver2 (cctx=0x7ffcd2397f40, argv=0x5641e4fa3788, argc=10, conn=0x5641e4f81328) at client-connection-tcp.c:187 #25 doveadm_cmd_handle (cctx=0x7ffcd2397f40, argv=<optimized out>, argc=<optimized out>, cmd_name=<optimized out>, conn=0x5641e4f81328) at client-connection-tcp.c:214 #26 client_handle_command (args=<optimized out>, conn=0x5641e4f81328) at client-connection-tcp.c:284 #27 client_connection_tcp_input (conn=0x5641e4f81328) at client-connection-tcp.c:436 #28 0x00007f612dbc78ad in io_loop_call_io (io=0x5641e4f88ee0) at ioloop.c:737 #29 0x00007f612dbc8f19 in io_loop_handler_run_internal (ioloop=ioloop@entry=0x5641e4f3df40) at ioloop-epoll.c:222 #30 0x00007f612dbc7950 in io_loop_handler_run (ioloop=0x5641e4f3df40) at ioloop.c:789 #31 0x00007f612dbc7ad0 in io_loop_run (ioloop=0x5641e4f3df40) at ioloop.c:762 #32 0x00007f612db39287 in master_service_run (service=0x5641e4f3dda0, callback=<optimized out>) at master-service.c:863 #33 0x00005641e4bd09f2 in main (argc=<optimized out>, argv=<optimized out>) at main.c:124 # 2.3.17.1 (476cd46418): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.17.1 (a1a0b892) # OS: Linux 4.18.0-348.7.1.el8_5.x86_64 x86_64 AlmaLinux release 8.5 (Arctic Sphynx) xfs # Hostname: redacted auth_username_format = %Ln doveadm_password = # hidden, use -P to show it first_valid_uid = 1000 mail_home = /var/spool/imap/%n mail_location = maildir:/var/spool/imap/%n/mail:VOLATILEDIR=/var/spool/imap/%n mail_plugins = " notify replication" 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 { list = children location = maildir:/var/spool/imap/redacted/mail/:INDEXPVT=/var/spool/imap/%n/pub-seen-idx/ mailbox * { autoexpunge = 60 days } prefix = redacted/ separator = / subscriptions = no type = public } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { 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 = scheme=CRYPT username_format=%n /etc/dovecot/users driver = passwd-file } passdb { args = failure_show_msg=yes dovecot driver = pam } plugin { mail_replica = tcps:10.111.1.1:26 sieve = file:/var/spool/imap/%n/sieve;active=/var/spool/imap/%n/.dovecot.sieve sieve_before = /var/lib/dovecot/sieve.d/ sieve_global = /var/lib/dovecot/sieve.d/ } protocols = imap lmtp sieve replication_dsync_parameters = -d -N -l 60 -U service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = dovecot } unix_listener replication-notify { mode = 0666 user = dovecot } } service doveadm { inet_listener { port = 26 ssl = yes } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 user = dovecot } } ssl = required ssl_cert = </etc/ssl/certs/cluster-redacted.crt ssl_key = # hidden, use -P to show it userdb { args = username_format=%n /etc/dovecot/users default_fields = uid=vmail gid=mail home=/var/spool/imap driver = passwd-file } userdb { driver = passwd override_fields = uid=vmail gid=mail home=/var/spool/imap/%n } protocol lmtp { mail_plugins = " notify replication sieve" } protocol imap { ssl_cert = </etc/ssl/certs/redacted.crt ssl_key = # hidden, use -P to show it } Atenciosamente/Kind regards, Salatiel

1 0

Spamassassin fails
by Hans Brage 10 Jan '22

10 Jan '22

Hi! I've been running a server with Dovecot, Sieve, Spamassassin and getmail to handle my emails for several years now. Just before christmas I did one of these regular updates and since then I got problems with spamassassin. Quite a lot of spam is not been filtered out. I can see a lot of errors like these in the mail-log. spamd: failed to create readable default_prefs: /home/vmail/.spamassassin/user_prefs Vmail is the user that is running my scripts that retrieves email and executes spamc. Any ideas? Regards, Hans

2 3