- dovecot - dovecot.org

doveadm stateful backup
by Christian 26 Jan '22

26 Jan '22

Hi all, first: I'm using version 2.3.4.1 I manage some rather large imap mailboxes which I want to backup on a regular basis. Some of them have relatively heavy traffic and one of them is greater than 30GB in size. I studied the docs for doveadm backup (https://wiki2.dovecot.org/Tools/Doveadm/Sync) and even did some code research to better understand the process. The docs state that using stateful synchronization is the most efficient way to synchronize mailboxes, therefore I chose this approach. Highlevel overview: - store a copy of the whole maildir in a separate directory (/var/vmail/backup) - backup to this directory once a minute (trying to make most use of transaction logs) using the last state stored within a file - create a backup once a day using tar (full, differential and incremental ones) blocking the backup process of the before mentioned step I quite often receive notifications that doveadm backup returned an exit code of 2, which should be quite normal. These notifications look like that: dsync(another_address(a)my.domain): Warning: Failed to do incremental sync for mailbox INBOX, retry with a full sync (Modseq 171631 no longer in transaction log (highest=177818, last_common_uid=177308, nextuid=177309)) dsync(another_address(a)my.domain): Warning: Mailbox changes caused a desync. You may want to run dsync again: Remote lost mailbox GUID e9149d0ae4e02d532505000026ca4352 (maybe it was just deleted?) Synced another_address(a)my.domain successfully but missing some changes. Took 3 seconds. Starting retry 1... The first message seems to point out that the transaction log got rolled and no more contains the messages from the backup dir, right? I thought about setting mail_index_log_rotate_min_age to 1hour to prevent rolling transaction logs too often, but abandoned this thought and increased the backup interval to once a minute. The warnings still appear so maybe my thoughts about transactions logs are wrong. The second message seems less alarming to me. How does doeveadm backup behave in such situations? Does it directly fall back to a less efficient way of syncing mails? Does the state store the information "retry with a full sync" and the next run uses this mode? To investigate on this I simply measured runtimes an saw that the second/retry run takes a bit longer (up to about 15 seconds) to sync the dir. I'm afraid of losing messages using my approach. Is it safe to always use doveadm backup -s $state? Simply counting one maildirs files within the live directory and the backup copy shows a 100 fewer files within the backup dir although the script runs only since a few days. For reference, see my backup script below. Regards Christian #!/bin/bash # * * * * * /root/bin/backup.sh --sync-only # 12 2 1-7 * * test $(date +\%u) -eq 6 && /root/bin/backup.sh --full # 12 2 8-31 * * test $(date +\%u) -eq 6 && /root/bin/backup.sh --differential # 12 2 * * * test $(date +\%u) -ne 6 && /root/bin/backup.sh synconly=0 differential=0 fullbackup=0 if [ $# -gt 0 ] ; then if [ "$1" == "--sync-only" ] ; then synconly=1 elif [ "$1" == "--differential" ] ; then differential=1 elif [ "$1" == "--full" ] ; then fullbackup=1 fi fi basedir="/var/vmail/backup" targetdir="/var/vmail/backup/done" mailaddresses="one_address(a)my.domain another_address(a)my.domain yet_another(a)my.domain" if [ ! -d "$basedir" ] ; then mkdir -p "$basedir" chown vmail:vmail "$basedir" fi if [ ! -d "$targetdir" ] ; then mkdir -p "$targetdir" chown vmail:vmail "$targetdir" fi for mailaddr in ${mailaddresses} ; do #echo "Creating backup for $mailaddr." domainpart=${mailaddr#*@} localpart=${mailaddr%%@*} lockfile="$basedir/$mailaddr.lock" statefile="$basedir/$mailaddr.state" backupdir="$domainpart/$localpart/Maildir" snapshotfile_full="$basedir/$mailaddr.full.snar" snapshotfile="$basedir/$mailaddr.snar" backup_basename="$basedir/${mailaddr}_$(date '+%Y%m%d_%H%M%S')" ( if [ $synconly -eq 1 ] ; then flock -xn 200 if [ $? -eq 1 ] ; then # failed to acquire lock. Skip mailbox silently. exit fi fi # try to acquire exclusive lock for one minute flock -xw 60 200 if [ $? -eq 1 ] ; then echo "Failed to acquire write lock within 60 seconds. Skipping $mailaddr." exit fi retries=0 retval=1 until [ $retval -eq 0 ] || [ $retries -ge 3 ] ; do let 'retries++' if [ -f "$statefile" ] ; then oldstate=$(head -1 "$statefile") else oldstate="" fi start_time=$(date +%s) ERROR=$((doveadm backup -u "$mailaddr" -s "$oldstate" "maildir:$basedir/$backupdir") 2>&1 > "$statefile") retval=$? end_time=$(date +%s) let 'duration=end_time-start_time' if [ $retval -eq 2 ] ; then #if [ $retries -gt 1 ] ; then echo "$ERROR" echo "Synced $mailaddr successfully but missing some changes. Took $duration seconds. Starting retry $retries..." #fi elif [ $retval -ne 0 ] ; then echo "$ERROR" echo "Syncing $mailaddr failed. Return code $retval. Took $duration seconds. Removing backup directory and starting retry $retries..." rm -rf "$basedir/$backupdir" rm -f "$statefile" "$snapshotfile" elif [ $retries -gt 1 ] ; then echo "Successful sync took $duration seconds." fi done # downgrade lock to shared lock flock -sn 200 [ $synconly -eq 1 ] && exit if [ $retval -ne 0 ] ; then echo "Too many retries. Aborting backup of $mailaddr." exit fi cd "$basedir" if [ $fullbackup -eq 1 ] || [ ! -f "$snapshotfile_full" ] ; then tar -cpzf "${backup_basename}_full.tar.gz" --level=0 -g "$snapshotfile_full" "$backupdir" cp -f "$snapshotfile_full" "$snapshotfile" else suffix="" if [ $differential -eq 1 ] ; then cp -f "$snapshotfile_full" "$snapshotfile" suffix="_diff" fi tar -cpzf "${backup_basename}${suffix}.tar.gz" -g "$snapshotfile" "$backupdir" fi cd - > /dev/null mv "${basedir}/"*.tar.gz "$targetdir" ) 200>"$lockfile" [ $synconly -eq 1 ] && continue # housekeeping newest_full=$(ls -1 "${targetdir}/${mailaddr}_"*_full.tar.gz 2>/dev/null | sort | tail -1) if [ -n "$newest_full" ] ; then #echo "Cleaning up files older than $newest_full..." find "$targetdir" -depth -maxdepth 1 -name "${mailaddr}_*" ! -newer "$newest_full" ! -samefile "$newest_full" -printf 'Deleting %p...\n' -delete fi done

1 1

pop3-login logging double Disconencted
by Noel Butler 26 Jan '22

26 Jan '22

Hi all, Wondering if anyone else is seeing this double Disconnected in the logs with current stable version, it only happens for pop3-login, and only with Too many commands... other pop3-login logging with Disconnected like Connection closed (no auth attempts... etc are fine Example of anomaly - pop3-login: Info: Disconnected: Disconnected: Too many bad commands (no auth attempts in ... If anyone running 2.3.17.1 sees this or does not see it on Too many bad... or at all, kindly mind letting me know, not sure if something has gone haywire here or its a bug that needs reporting since logs indicate this only occurred after updating to the point 1 release. -- Regards, Noel Butler This Email, including attachments, may contain legally privileged information, therefore at all times remains confidential and subject to copyright protected under international law. You may not disseminate this message without the authors express written authority to do so. If you are not the intended recipient, please notify the sender then delete all copies of this message including attachments immediately. Confidentiality, copyright, and legal privilege are not waived or lost by reason of the mistaken delivery of this message.

2 1

noob maildir question
by mikfum 25 Jan '22

25 Jan '22

I would like to ask if it is an acceptable practice to manage messages in the maildir as a file (move them from one folder to another) while dovecot is in stop state thinking that it will be rebuild to the next imap user login thanks for your patience:) mik

5 10

Re: noob maildir question
by mikfum 24 Jan '22

24 Jan '22

thanks ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ Il lunedì 24 gennaio 2022 5:15 AM, Ted Hatfield <ted(a)io-tx.com> ha scritto: > I do this all the time on my server. From one user mailbox to another or > > from one maildir folder to another. On my platform I need to make certain > > owner/group of the moved messages is correct for the user I've moved them > > to. Other than that dovecot appears to re-index on the fly. > > Be aware that this is observed information. Others more knowledgeable may > > have concerns that I'm not aware of or just can't see on my system. > > Ted > > On Mon, 24 Jan 2022, mikfum wrote: > > > I would like to ask if it is an acceptable practice to manage messages in the maildir as a file (move them from > > > > one folder to another) while dovecot is in stop state thinking that it will be rebuild to the next imap user login > > > > thanks for your patience:) > > > > mik

1 0

zlib.read errors after upgrade from 2.3.15 to 2.3.17.1
by Arno Schneider 24 Jan '22

24 Jan '22

After upgrading my mailserver from buster to bullseye and dovecot 2.3.15 to 2.3.17.1 I got the following errors: Jan 22 14:22:32 Warning: doveadm(user1)<2953060><49b0NRQF7GFkDy0ALVPUUA>: mdbox /local/mail/user1/storage: rebuilding indexes Jan 22 14:22:39 Error: doveadm(user2)<2953112><awsPGB8F7GGYDy0ALVPUUA>: dsync(2nd.dovecot.server): read(compress(/local/mail/user2/storage/m.4650)) failed: read(/local/mail/user2/storage/m.4650) failed: zlib.read(/local/mail/user2/storage/m.4650): unexpected EOF at 7038367 (last sent=mail, last recv=mail_request (EOL)) I have 2 dovecot servers in a multi-master configuration. The both servers are synced with dsync and the users are routed through a dovecot directors. Any hints where I can continue to investigate / solve this issue? best regards, arno

1 0

Why would dovecot not be answering
by Ruben Safir 23 Jan '22

23 Jan '22

I am really lost as to why dovecot is not authenticating I have smtpd_sasl_type = dovecot in main.cf and # Postfix smtp-auth unix_listener /var/spool/postfix/private/auth { mode = 0666 user = postfix group = postfix } in /etc/dovecot/conf.d/10-master.conf I want it to authenticate on submition only Everything I read says this should do it, but I am up against a wall. I have no debugging information or log at all to confirm what postfix is doing. -- 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

3 5

S3 integration w Dovecot
by Martin Olsen 21 Jan '22

21 Jan '22

Good morning, day, evening :P As stated on documentation S3-compatible Storages — Dovecot documentation <https://doc.dovecot.org/configuration_manual/mail_location/obox/s3/> only AWS S3 is officially supported. However, we know that Scality has been successfully integrated at some larger corporations. Particularly curious if anyone has integrated with Pure S3 object storage solution, or any other for that matter? Just looking at some different options. - Sincerely, Martin.

4 3

Stop used or not
by mauric＠gmx.ch 21 Jan '22

21 Jan '22

Sieve scripts running fine, but please what would mean the "Stop", if I have multiple Policy that will run true, I need one stop to finish this per section? if header :is ["from","bcc","to"] ["Email-Address-one", "Email-Address-Two", "and so on"] { fileinto ".\Magic-FolderName"; stop; } thanks

3 4

Upgrade only piegenhole to 0.5.17?
by mauric＠gmx.ch 20 Jan '22

20 Jan '22

Please it's possible to update only piegenhole to 0.5.17, on existing Dovecot installation? Downloading dovecot-2.3-pigeonhole-0.5.17.1 Here I found the update-version, its this the possible way? And why I don't found any Informations on any readme, please point me to the right place. installed version, I think this it's the right view? Please on witch place I can check the Sieve installed module? doveconf | head # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5 () Also found in file pieg-config /* Define to the version of Pigeonhole for Dovecot. */ #define PIGEONHOLE_VERSION "0.5.4" On Debian 10 I have this installed. dovecot-managesieved 1:2.3.4.1-5+deb10u6 amd64 secure POP3/IMAP server - ManageSie dovecot-sieve 1:2.3.4.1-5+deb10u6 amd64 secure POP3/IMAP server - Sieve filters support also checking the folder /usr/include/dovecot/sieve with intention so found any possible version? Thanks for any update

2 2

sockets created for lmtp
by Mike 20 Jan '22

20 Jan '22

Was recently configuring lmtp to listen in the postfix spool for mail. I set the socket as suggested in the documentation, however, when I look at what sockets were created there was an additional one for dovecot. Since I made the change, my expectation would have been just the one that I set up. I doubt it impacts it negatively, but I wanted to understand if I configured things correctly or not. Thanks. Mike

4 6

FTS Tokenization filters normalizer-icu vs lowercase
by Alessio Cecchi 20 Jan '22

20 Jan '22

Hi, I'm trying to setup fts-flatcurve with tokenization. What are the differences/benefits with "fts_filters = normalizer-icu" vs "fts_filters = lowercase"? Reading the Doc I found about normalizer-icu "This is potentially very resource intensive." and about lowercase "Supports UTF8, when compiled with libicu". So, using lowercase is almost the same that normalizer-icu but faster? FYI for using fts-flatcurve with dovecot RPM packages from repo.dovecot.org you have to rebuild with --with-icu --with-stemmer --with-textcat and related library. Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

2 1

Save of messages slow when replica unavailable
by Jörg Faudin Schulz 20 Jan '22

20 Jan '22

We have a setup with a dovecot server + replica. This works fine as long as the replica is available. When the replica is not available for some reason, the clients can work normally with one exception: the saving of sent messages to their inboxes takes ages. Thunderbird times out and complains (and duplicates the message), mail.app just waits until it's done. Is there any setting that helps here? For the time being, I deactivated replication; but this isn't a long time solution. Thank you for all your work&support, appreciating the doc as well.

1 0

dovecot-2.3.17: "Panic: file ioloop.c: line 865"
by Christian Küppers 20 Jan '22

20 Jan '22

Hello, we got the same backtrace in dovecot-ee version 2:2.3.17-8+ubuntu20.04 as Andreas Piper mentioned in November 2021 https://dovecot.org/pipermail/dovecot/2021-November/123468.html after installing dovecot package updates. Panic: file ioloop.c: line 865 (io_loop_destroy): assertion failed: (ioloop == current_ioloop) Error: Raw backtrace: #0 t_askpass[0x7fc609b0eba0] -> #1 backtrace_append[0x7fc609b0ee00] -> #2 backtrace_get[0x7fc609b0ef70] -> #3 i_syslog_error_handler[0x7fc609b1bfa0] -> #4 i_syslog_fatal_handler[0x7fc609b1c0d0] -> #5 i_panic[0x7fc609a6f1af] -> #6 i_error[0x7fc609a72906] -> #7 doveadm_http_server_deinit[0x55abd194af90] -> #8 doveadm_print_stream[0x55abd19447b0] -> #9 doveadm_print_istream[0x55abd1944810] -> #10 expunge_search_args_check[0x55abd1936a00] -> #11 expunge_search_args_check[0x55abd1935860] -> #12 doveadm_dsync_main[0x55abd1932900] -> #13 doveadm_cmd_ver2_to_mail_cmd_wrapper[0x55abd1933890] -> #14 doveadm_cmd_run_ver2[0x55abd1943fb0] -> #15 doveadm_server_deinit[0x55abd1948760] -> #16 io_loop_call_io[0x7fc609b32440] -> #17 io_loop_handler_run_internal[0x7fc609b33a00] -> #18 io_loop_handler_run[0x7fc609b32500] -> #19 io_loop_run[0x7fc609b32680] -> #20 master_service_run[0x7fc609aa4780] -> #21 main[0x55abd1923820] -> #22 __libc_start_main[0x7fc60970efc0] -> #23 _start[0x55abd1923980] Error: doveadm server disconnected before handshake: EOF Command fetch failed for <mailbox>: EOF We got it during doveadm fetch of a mail on multiple mailboxes. Is there any progress on this? Will it be fixed in next release? Kind regards, Christian Küppers Expert Administrator onOffice GmbH Charlottenburger Allee 5 | 52068 Aachen Tel. +49 (0)241 446 86-0 | Fax. +49 (0)241 446 86-250 E-Mail:c.kueppers@onoffice.de| Web:www.onOffice.com Registergericht: Amtsgericht Aachen, HRB 21420 Geschäftsführer: Dipl.-Kfm. Stefan Mantl Prokuristen: Janosch Reuschenbach, Kristina Andresen, Christian Mähringer

2 1

lmtp_save_to_detail_mailbox
by dovecot＠ptld.com 19 Jan '22

19 Jan '22

lmtp_save_to_detail_mailbox: " If the recipient address includes a detail element / role (as in user+detail format), save the message to the detail mailbox. " Im not understanding this, what is the "detail mailbox"? I tried testing this feature by setting "lmtp_save_to_detail_mailbox = yes" and sending an email to user+test(a)example.com. The email still ended up in the default inbox folder. So what does lmtp_save_to_detail_mailbox do or is there another setting that also needs to be set to use this feature?

3 5

Outlook vs. Dovecot experience
by Vladislav Kurz 18 Jan '22

18 Jan '22

Dear colleagues, what is your experience regarding using outlook (2016/365) as IMAP client and dovecot on server side? We have sync issues with outlook vs. cyrus IMAP server, and we consider moving to dovecot. But before that I'd like to hear from others if this combination works well. Especially if users have large and bushy mailboxes (>10 GB, >100 mailboxes), two mailboxes (accounts) on the same server. I don't want to do the migration just to find out that it is general issue of outlook vs. any IMAP server. -- Best regards Vladislav Kurz

7 10

JA3/JA3S as a Dovecot plugin?
by Sidsel Jensen 18 Jan '22

18 Jan '22

Hi We have been looking a bit into JA3 (https://engineering.salesforce.com/tls-fingerprinting-with-ja3-and-ja3s-247… <https://engineering.salesforce.com/tls-fingerprinting-with-ja3-and-ja3s-247…> and https://blog.squarelemon.com/tls-fingerprinting/ <https://blog.squarelemon.com/tls-fingerprinting/> ) for possible threat actor identifications. Roughly speaking you can think of JA3 as the TLS equivalent of the User-Agent string. Has anybody been looking into the possibility of building an open source dovecot JA3 plugin? I’d also like to hear the technical pros/cons of doing so…and perhaps the ethical deliberations also :-) Kind Regards, Sidsel

1 0

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

Dovecot 2.3.17 on FreeBSD 12.2 panic
by Bert JW Regeer 10 Jan '22

10 Jan '22

Hello, I have dovecot 2.3.17 running on FreeBSD 12.2 and it keeps panicking: Jan 10 03:04:07 strida dovecot[55198]: imap(xistence(a)0x58.com)<56382><dx4KlzHVQecmAQKCQwA50VytdgLnsQSr>: Panic: file array.c: line 10 (array_idx_modifiable_i): assertion failed: (idx < array->buffer->used / array->element_size) Jan 10 03:04:07 strida dovecot[55198]: imap(xistence(a)0x58.com)<56382><dx4KlzHVQecmAQKCQwA50VytdgLnsQSr>: Fatal: master: service(imap): child 56382 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps) Ignore the core not dumped, this is happening over and over, and I got one process to core dump: # lldb /usr/local/libexec/dovecot/imap -c imap.core (lldb) target create "/usr/local/libexec/dovecot/imap" --core "imap.core" Core file '/usr/local/vmail/domains/0x58.com/xistence/imap.core' (x86_64) was loaded. (lldb) bt * thread #1, name = 'imap', stop reason = signal SIGABRT * frame #0: 0x0000000011588c2a libc.so.7`__sys_thr_kill + 10 frame #1: 0x0000000011587084 libc.so.7`__raise + 52 frame #2: 0x00000000114fd279 libc.so.7`abort + 73 frame #3: 0x00000000113736f3 libdovecot.so.0`___lldb_unnamed_symbol873$$libdovecot.so.0 + 147 frame #4: 0x0000000011371eaf libdovecot.so.0`___lldb_unnamed_symbol862$$libdovecot.so.0 + 47 frame #5: 0x0000000011372c71 libdovecot.so.0`___lldb_unnamed_symbol864$$libdovecot.so.0 + 33 frame #6: 0x00000000113720bb libdovecot.so.0`i_panic + 187 frame #7: 0x0000000011363d3f libdovecot.so.0`array_idx_modifiable_i + 79 frame #8: 0x0000000011ef7c68 lib20_fts_plugin.so`fts_user_autoindex_exclude + 72 frame #9: 0x0000000011ef550f lib20_fts_plugin.so`fts_mailbox_allocated + 239 frame #10: 0x000000001113ed5a libdovecot-storage.so.0`hook_mailbox_allocated + 154 frame #11: 0x00000000111381e1 libdovecot-storage.so.0`mailbox_alloc + 449 frame #12: 0x0000000001043db4 imap`cmd_select_full + 356 frame #13: 0x000000000104c582 imap`command_exec + 178 frame #14: 0x000000000104ae8a imap`___lldb_unnamed_symbol58$$imap + 58 frame #15: 0x000000000104af91 imap`___lldb_unnamed_symbol58$$imap + 321 frame #16: 0x00000000010499e7 imap`client_handle_input + 471 frame #17: 0x0000000001048178 imap`client_input + 120 frame #18: 0x000000001138ca9f libdovecot.so.0`io_loop_call_io + 111 frame #19: 0x000000001138f45b libdovecot.so.0`io_loop_handler_run_internal + 347 frame #20: 0x000000001138cffa libdovecot.so.0`io_loop_handler_run + 346 frame #21: 0x000000001138ce58 libdovecot.so.0`io_loop_run + 88 frame #22: 0x00000000112f11c8 libdovecot.so.0`master_service_run + 24 frame #23: 0x000000000105a417 imap`main + 1383 frame #24: 0x000000000103bed2 imap`_start + 226 (lldb) ^D I was able to generate a core dump by issue a doveadm command too: (lldb) bt * thread #1, name = 'doveadm', stop reason = signal SIGABRT * frame #0: 0x00000008017b1c2a libc.so.7`__sys_thr_kill + 10 frame #1: 0x00000008017b0084 libc.so.7`__raise + 52 frame #2: 0x0000000801726279 libc.so.7`abort + 73 frame #3: 0x000000080159c6f3 libdovecot.so.0`___lldb_unnamed_symbol873$$libdovecot.so.0 + 147 frame #4: 0x000000080159aeaf libdovecot.so.0`___lldb_unnamed_symbol862$$libdovecot.so.0 + 47 frame #5: 0x000000080159ae71 libdovecot.so.0`default_fatal_handler + 33 frame #6: 0x000000080159b0bb libdovecot.so.0`i_panic + 187 frame #7: 0x000000080158cd3f libdovecot.so.0`array_idx_modifiable_i + 79 frame #8: 0x0000000802236c68 lib20_fts_plugin.so`fts_user_autoindex_exclude + 72 frame #9: 0x000000080223450f lib20_fts_plugin.so`fts_mailbox_allocated + 239 frame #10: 0x0000000801367d5a libdovecot-storage.so.0`hook_mailbox_allocated + 154 frame #11: 0x00000008013611e1 libdovecot-storage.so.0`mailbox_alloc + 449 frame #12: 0x000000080222d5fc lib20_fts_plugin.so`fts_backend_rescan + 60 frame #13: 0x000000080227c1a3 lib20_doveadm_fts_plugin.so`___lldb_unnamed_symbol15$$lib20_doveadm_fts_plugin.so + 99 frame #14: 0x000000000107172f doveadm`___lldb_unnamed_symbol134$$doveadm + 479 frame #15: 0x000000000107252c doveadm`doveadm_cmd_ver2_to_mail_cmd_wrapper + 2492 frame #16: 0x0000000001083c98 doveadm`doveadm_cmd_run_ver2 + 1416 frame #17: 0x00000000010836d7 doveadm`doveadm_cmd_try_run_ver2 + 71 frame #18: 0x0000000001086da3 doveadm`main + 835 frame #19: 0x000000000105fa92 doveadm`_start + 226 (lldb) # doveadm fts rescan -u xistence(a)0x58.com doveadm(xistence(a)0x58.com): Panic: file array.c: line 10 (array_idx_modifiable_i): assertion failed: (idx < array->buffer->used / array->element_size) Abort (core dumped) # dovecot-sysreport Gathering configurations ... grep: The -P option is not supported grep: The -P option is not supported grep: The -P option is not supported Gathering system informations ... Creating archive ... All done! Please report file dovecot-sysreport-strida.0x58.com-1641784164.tar.gz Removing temp files at /tmp/tmp.z5qJkwrW … While reading about fts/fts_squat I came across the page noting it was deprecated. I am running a mail server for myself, and have avoided installing Solr this entire time, but I guess its time to upgrade. In the mean time hopefully this core dump can help figure out what is going on. Bert JW Regeer

2 3

outlook 2019 not working
by postmaster 10 Jan '22

10 Jan '22

Just tried connecting a Windows 10 client with Outlook 2019 but it fail's on both POP3 or IMAP - i knew it was working when i tested it after the server setup about a year ago because i documented everything with screenshots. All other devices we use (Thunderbird, iPhone/iPad, Android devices, RoundCube) are working without any issue, just Outlook won't connect anymore. We don't have much Windows/Outlook experience - any help/hints appreciated. This what i have in the logs, but doesn't see anything that helps: 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x10, ret=1: before SSL initialization 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: before SSL initialization 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read client hello 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server hello 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write certificate 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write key exchange 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read client key exchange 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read change cipher spec 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read finished 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write session ticket 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write change cipher spec 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write finished 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x20, ret=1: SSL negotiation finished successfully 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully 2022.01.10 02:22:25 pop3-login: Info: Login: user=<user1(a)mail-server.cc>, method=PLAIN, rip=178.189.103.34, lip=195.88.238.13, mpid=1694, TLS, TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Loading modules from directory: /usr/lib/dovecot/modules 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib01_acl_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib15_notify_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_mail_log_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_replication_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_virtual_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_zlib_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Added userdb setting: plugin/quota_rule=*:bytes=10240000 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Effective uid=5000, gid=5000, home=/srv/vmail/mail-server.cc/user1/ 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(file): dict created (uri=file:/srv/vmail/shared-mailboxes.db, base_dir=/var/run/dovecot) 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota root: name=User Quota backend=dict args=:proxy::sqluserquota 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota rule: root=User Quota mailbox=* bytes=10240000 messages=0 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota rule: root=User Quota mailbox=Trash bytes=+1024000 (10%) messages=0 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota rule: root=User Quota mailbox=Sent bytes=+1024000 (10%) messages=0 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota warning: bytes=10240000 (100%) messages=0 reverse=no command=quota-warning 100 user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota warning: bytes=9728000 (95%) messages=0 reverse=no command=quota-warning 95 user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota warning: bytes=9216000 (90%) messages=0 reverse=no command=quota-warning 90 user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota warning: bytes=8192000 (80%) messages=0 reverse=no command=quota-warning 80 user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota grace: root=User Quota bytes=1024000 (10%) 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: quota-dict: user=user1(a)mail-server.cc, uri=proxy::sqluserquota, noenforcing=0 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(proxy): dict created (uri=proxy::sqluserquota, base_dir=/var/run/dovecot) 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/srv/vmail/mail-server.cc/user1/maildir 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: maildir++: root=/srv/vmail/mail-server.cc/user1/maildir, index=, indexpvt=, control=, inbox=/srv/vmail/mail-server.cc/user1/maildir,alt= 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: initializing backend with data: vfile 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: acl username = user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: owner = 1 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl vfile: Global ACLs disabled 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Namespace : type=shared, prefix=shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=maildir:/srv/vmail/%d/%n/maildir:INDEX=~/maildir/shared/%u:CONTROL=~/maildir/shared/%u 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: shared: root=/var/run/dovecot, index=, indexpvt=, control=, inbox=, alt= 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: initializing backend with data: vfile 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: acl username = user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: owner = 0 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl vfile: Global ACLs disabled 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: quota: quota_over_flag check: quota_over_script unset - skipping 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Mailbox INBOX: Mailbox opened because: POP3 INBOX 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl vfile: file /srv/vmail/mail-server.cc/user1/maildir/dovecot-acl not found 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Info: Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0, bytes=12/43 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(proxy): Waiting for dict to finish pending operations 2022.01.10 02:22:25 pop3-login: Debug: SSL alert: close notify 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(file): dict destroyed 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(proxy): Waiting for dict to finish pending operations 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(proxy): dict destroyed 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x10, ret=1: before SSL initialization 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=-1: before SSL initialization 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read client hello 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server hello 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write certificate 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write key exchange 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read client key exchange 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read change cipher spec 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read finished 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write session ticket 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write change cipher spec 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write finished 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x20, ret=1: SSL negotiation finished successfully 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully 2022.01.10 02:23:00 imap-login: Info: Login: user=<user1(a)mail-server.cc>, method=PLAIN, rip=178.189.103.34, lip=195.88.238.13, mpid=1696, TLS, TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Loading modules from directory: /usr/lib/dovecot/modules 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib01_acl_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib02_imap_acl_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib11_imap_quota_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib15_notify_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_mail_log_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_replication_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_virtual_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_zlib_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib95_imap_sieve_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Added userdb setting: plugin/quota_rule=*:bytes=10240000 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Effective uid=5000, gid=5000, home=/srv/vmail/mail-server.cc/user1/ 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: dict(file): dict created (uri=file:/srv/vmail/shared-mailboxes.db, base_dir=/var/run/dovecot) 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota root: name=User Quota backend=dict args=:proxy::sqluserquota 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota rule: root=User Quota mailbox=* bytes=10240000 messages=0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota rule: root=User Quota mailbox=Trash bytes=+1024000 (10%) messages=0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota rule: root=User Quota mailbox=Sent bytes=+1024000 (10%) messages=0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota warning: bytes=10240000 (100%) messages=0 reverse=no command=quota-warning 100 user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota warning: bytes=9728000 (95%) messages=0 reverse=no command=quota-warning 95 user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota warning: bytes=9216000 (90%) messages=0 reverse=no command=quota-warning 90 user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota warning: bytes=8192000 (80%) messages=0 reverse=no command=quota-warning 80 user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota grace: root=User Quota bytes=1024000 (10%) 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: quota-dict: user=user1(a)mail-server.cc, uri=proxy::sqluserquota, noenforcing=0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: dict(proxy): dict created (uri=proxy::sqluserquota, base_dir=/var/run/dovecot) 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/srv/vmail/mail-server.cc/user1/maildir 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: maildir++: root=/srv/vmail/mail-server.cc/user1/maildir, index=, indexpvt=, control=, inbox=/srv/vmail/mail-server.cc/user1/maildir,alt= 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: initializing backend with data: vfile 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: acl username = user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: owner = 1 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl vfile: Global ACLs disabled 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Namespace : type=shared, prefix=shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=maildir:/srv/vmail/%d/%n/maildir:INDEX=~/maildir/shared/%u:CONTROL=~/maildir/shared/%u 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: shared: root=/var/run/dovecot, index=, indexpvt=, control=, inbox=, alt= 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: initializing backend with data: vfile 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: acl username = user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: owner = 0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl vfile: Global ACLs disabled 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: quota: quota_over_flag check: quota_over_script unset - skipping 2022.01.10 02:23:00 imap-login: Debug: SSL error: Connection closed 2022.01.10 02:23:00 imap-login: Debug: SSL alert: close notify 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl vfile: file /srv/vmail/mail-server.cc/user1/maildir/dovecot-acl not found 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Info: Disconnected: Connection closed (IDLE running for 0.001 + waiting input for 0.001 secs, 2 B in + 10 B out, state=wait-input) in=11 out=461 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: dict(file): dict destroyed 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: dict(proxy): Waiting for dict to finish pending operations 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: dict(proxy): dict destroyed thx, Alex

2 1

Patch: assertion failed in doveadm fts lookup
by John Fawcett 09 Jan '22

09 Jan '22

Hi I'm reposting this patch, which I have been applying locally since I originally posted it. Hopefully it can be considered for inclusion in the official release. It was tested on dovecot 2.3.16 but applies against the latest version 2.3.17.1. This is the "assertion failed" that it addresses doveadm fts lookup -u john(a)voipsupport.it body "text to look for" doveadm(john(a)voipsupport.it): Panic: file mail-storage.c: line 2108 (mailbox_get_open_status): assertion failed: (box->opened) doveadm(john(a)voipsupport.it): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7ff624fa7072] -> /usr/local/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7ff624fa718e] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xffc3b) [0x7ff624fb3c3b] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xffc71) [0x7ff624fb3c71] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x5536f) [0x7ff624f0936f] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0x3fc31) [0x7ff6250bcc31] -> /usr/local/lib/dovecot/lib21_fts_solr_plugin.so(+0x540d) [0x7ff62244f40d] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(fts_backend_lookup+0x4d) [0x7ff6246b624d] -> /usr/local/lib/dovecot/doveadm/lib20_doveadm_fts_plugin.so(+0x2e8c) [0x7ff62240ce8c] -> doveadm(+0x31ded) [0x55f0c7f3aded] -> doveadm(+0x32862) [0x55f0c7f3b862] -> doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x22d) [0x55f0c7f3c6fd] -> doveadm(doveadm_cmd_run_ver2+0x4d8) [0x55f0c7f4d158] -> doveadm(doveadm_cmd_try_run_ver2+0x3a) [0x55f0c7f4d1aa] -> doveadm(main+0x1f6) [0x55f0c7f2b606] -> /lib64/libc.so.6(__libc_start_main+0xd5) [0x7ff624bc8b75] -> doveadm(_start+0x2e) [0x55f0c7f2ba0e] Aborted (core dumped) Here's the patch: diff -ur dovecot-2.3.17.1-orig/src/plugins/fts/doveadm-fts.c dovecot-2.3.17.1-new/src/plugins/fts/doveadm-fts.c --- dovecot-2.3.17.1-orig/src/plugins/fts/doveadm-fts.c 2021-12-03 12:48:47.000000000 +0100 +++ dovecot-2.3.17.1-new/src/plugins/fts/doveadm-fts.c 2022-01-09 01:33:23.396342025 +0100 @@ -47,6 +47,14 @@ i_array_init(&result.scores, 16); box = mailbox_alloc(info->ns->list, info->vname, 0); + mailbox_set_reason(box,"fts search"); + if (mailbox_open(box) < 0) { + i_error("Couldn't open mailbox: %s", + mailbox_get_last_internal_error(box, NULL)); + doveadm_mail_failed_error(ctx, MAIL_ERROR_TEMP); + return -1; + } + if (fts_backend_lookup(backend, box, ctx->search_args->args, FTS_LOOKUP_FLAG_AND_ARGS, &result) < 0) { i_error("fts lookup failed"); John

2 1

Non-user logins?
by Ken Wright 09 Jan '22

09 Jan '22

My Dovecot issues continue. Right now I see at least two issues: first, my logs consistently show non-users trying (and failing) to log in, and I'm still unable to log in from my email client (Evolution or Roundcube, either one). I'll post about the second issue later; right now I wonder why I'm getting so many non-users trying to log in. Am I the subject of concerted hacking attacks, or is there something else going on? Some of the attempted logins are more-or-less random names claiming to be @mydomain, but at least one is a username that's really on my server, to wit: Jan 7 22:52:01 grace dovecot: lmtp(776281): Error: lmtp-server: conn unix:pid=776262,uid=117 [3]: rcpt www-data(a)mydomain.com: Failed to lookup user www-data(a)mydomain.com: Internal error occurred. Refer to server log for more information. (Another quick question: which server log should I check?) So, if anyone can tell me what's going on with all these logins, I'd be much obliged! Ken

9 16

Patch: enhancements for solr/tika integration
by John Fawcett 09 Jan '22

09 Jan '22

Hi here's a patch with some enhancements that I am applying locally for solr/tika integration. Hopefully this can be considered for inclusion. I've tested up to 2.3.16 and this patch applies against latest version 2.3.17.1. The contents are: 1. Allow username and password in tika configuration (as is already supported for solr). For example: fts_tika = https://user:password@tika_host:tika_port/tika/tika This means that tika can be more easily located on a different server to dovecot. Locating Solr and Tika on separate servers can isolate the Dovecot server from issues that may happen on Solr or Tika (like out of memory). 2. Introduce an optional configurable limit on the size of emails whose message bodies will be indexed with solr via a new setting fts_max_size, to be put in the plugin section. For example plugin { ... fts_max_size = 2M ... } Message body indexing is skipped for messages that are larger than this setting. 3. Introduce an optional configurable limit on the size of emails whose attachments will be sent to tika for keyword extraction, via a new setting fts_max_size_tika, to be put in the plugin section. For example: plugin { ... fts_max_size_tika = 1M } I noticed that some very large attachments are being sent to tika and these often do not have any useful content to index. For simplicity the check is done on message size not individual or total attachment size. Here's the patch: diff -ur dovecot-2.3.17.1-orig/src/plugins/fts/fts-build-mail.c dovecot-2.3.17.1-new/src/plugins/fts/fts-build-mail.c --- dovecot-2.3.17.1-orig/src/plugins/fts/fts-build-mail.c 2021-12-03 12:48:47.000000000 +0100 +++ dovecot-2.3.17.1-new/src/plugins/fts/fts-build-mail.c 2022-01-09 01:33:23.398341998 +0100 @@ -17,6 +17,7 @@ #include "fts-filter.h" #include "fts-api-private.h" #include "fts-build-mail.h" +#include "settings-parser.h" /* there are other characters as well, but this doesn't have to be exact */ #define IS_WORD_WHITESPACE(c) \ @@ -25,6 +26,8 @@ wherever */ #define MAX_WORD_SIZE 1024 +static bool debug = FALSE; + struct fts_mail_build_context { struct mail *mail; struct fts_backend_update_context *update_ctx; @@ -34,6 +37,7 @@ buffer_t *word_buf, *pending_input; struct fts_user_language *cur_user_lang; + bool oversized_tika; }; static int fts_build_data(struct fts_mail_build_context *ctx, @@ -223,7 +227,7 @@ parser_context.user = mail_storage_get_user(storage); parser_context.content_disposition = ctx->content_disposition; - + parser_context.oversized_tika = ctx->oversized_tika; if (fts_parser_init(&parser_context, &ctx->body_parser)) { /* extract text using the the returned parser */ *binary_body_r = TRUE; @@ -496,7 +500,32 @@ bool binary_body; const char *error; int ret; - + uoff_t msg_size; + uoff_t fts_max_size = 0; + uoff_t fts_max_size_tika = 0; + const char * fts_max_size_setting; + const char * fts_max_size_tika_setting; + bool oversized_msg; + bool oversized_tika; + + fts_max_size_setting = mail_user_plugin_getenv(update_ctx->backend->ns->user, "fts_max_size"); + if (fts_max_size_setting != NULL) { + if (debug) i_debug("fts_max_size %s",fts_max_size_setting); + if (settings_get_size(fts_max_size_setting, &fts_max_size, &error) < 0) { + i_error("%s",error); + fts_max_size = 0; + } + if (debug) i_debug("fts_max_size (value) %"PRIuUOFF_T,fts_max_size); + } + fts_max_size_tika_setting = mail_user_plugin_getenv(update_ctx->backend->ns->user, "fts_max_size_tika"); + if (fts_max_size_tika_setting != NULL) { + if (debug) i_debug("fts_max_size_tika %s",fts_max_size_tika_setting); + if (settings_get_size(fts_max_size_tika_setting, &fts_max_size_tika, &error) < 0) { + i_error("%s",error); + fts_max_size_tika = 0; + } + if (debug) i_debug("fts_max_size_tika (value) %"PRIuUOFF_T,fts_max_size_tika); + } *may_need_retry_r = FALSE; if (mail_get_stream_because(mail, NULL, NULL, "fts indexing", &input) < 0) { if (mail->expunged) @@ -505,10 +534,21 @@ mailbox_get_last_internal_error(mail->box, NULL)); return -1; } - + oversized_msg = FALSE; + oversized_tika = FALSE; + i_stream_get_size(input,TRUE,&msg_size); + if (fts_max_size > 0 && msg_size > fts_max_size) { + i_info("Skipping message body indexing because size %"PRIuUOFF_T" exceeds setting fts_max_size %s",msg_size,fts_max_size_setting); + oversized_msg = TRUE; + } + if (fts_max_size_tika > 0 && msg_size > fts_max_size_tika) { + i_info("Skipping message attachment indexing because size %"PRIuUOFF_T" exceeds setting fts_max_size_tika %s",msg_size,fts_max_size_tika_setting); + oversized_tika = TRUE; + } i_zero(&ctx); ctx.update_ctx = update_ctx; ctx.mail = mail; + ctx.oversized_tika = oversized_tika; if ((update_ctx->backend->flags & FTS_BACKEND_FLAG_TOKENIZED_INPUT) != 0) ctx.pending_input = buffer_create_dynamic(default_pool, 128); @@ -563,7 +603,7 @@ message_decoder_set_return_binary(decoder, TRUE); body_part = TRUE; } else { - if (skip_body) + if (skip_body ||oversized_msg) continue; } @@ -597,7 +637,7 @@ else (void)fts_parser_deinit(&ctx.body_parser, NULL); } - if (ret == 0 && body_part && !skip_body && !body_added) { + if (ret == 0 && body_part && !skip_body && !oversized_msg && !body_added) { /* make sure body is added even when it doesn't exist */ block.data = NULL; block.size = 0; ret = fts_build_body_block(&ctx, &block, TRUE); diff -ur dovecot-2.3.17.1-orig/src/plugins/fts/fts-parser.h dovecot-2.3.17.1-new/src/plugins/fts/fts-parser.h --- dovecot-2.3.17.1-orig/src/plugins/fts/fts-parser.h 2021-12-03 12:48:47.000000000 +0100 +++ dovecot-2.3.17.1-new/src/plugins/fts/fts-parser.h 2022-01-09 01:33:23.399341985 +0100 @@ -10,6 +10,7 @@ /* Can't be NULL */ const char *content_type; const char *content_disposition; + bool oversized_tika; }; struct fts_parser_vfuncs { diff -ur dovecot-2.3.17.1-orig/src/plugins/fts/fts-parser-tika.c dovecot-2.3.17.1-new/src/plugins/fts/fts-parser-tika.c --- dovecot-2.3.17.1-orig/src/plugins/fts/fts-parser-tika.c 2021-12-03 12:48:47.000000000 +0100 +++ dovecot-2.3.17.1-new/src/plugins/fts/fts-parser-tika.c 2022-01-09 01:33:23.400341972 +0100 @@ -57,7 +57,7 @@ tuser = p_new(user->pool, struct fts_parser_tika_user, 1); MODULE_CONTEXT_SET(user, fts_parser_tika_user_module, tuser); - if (http_url_parse(url, NULL, 0, user->pool, + if (http_url_parse(url, NULL, HTTP_URL_ALLOW_USERINFO_PART, user->pool, &tuser->http_url, &error) < 0) { i_error("fts_tika: Failed to parse HTTP url %s: %s", url, error); return -1; @@ -148,6 +148,10 @@ if (tika_get_http_client_url(parser_context->user, &http_url) < 0) return NULL; + if (parser_context->oversized_tika) { + i_info("skipping tika parser due to oversized message"); + return NULL; + } if (http_url->path == NULL) http_url->path = "/"; @@ -159,6 +163,11 @@ http_url->host.name, t_strconcat(http_url->path, http_url->enc_query, NULL), fts_tika_parser_response, parser); + if (http_url->user != NULL) { + http_client_request_set_auth_simple( + http_req, http_url->user, http_url->password); + } + http_client_request_set_port(http_req, http_url->port); http_client_request_set_ssl(http_req, http_url->have_ssl); if (parser_context->content_type != NULL) John

1 0

Patch: safeguard against too large value for uid being sent to solr for single mailbox searches
by John Fawcett 09 Jan '22

09 Jan '22

Hi I'm reposting a patch for solr integration which I have been applying locally. It applies against 2.3.17.1. Dovecot already has a mechanism when doing solr fts searches on multiple mailboxes that prevents a too large value for maximum rows being sent to solr. #define SOLR_MAX_MULTI_ROWS 100000 (defined and used in plugins/fts-solr/fts-backend-solr.c) However on single mailbox searches Dovecot uses the last uid of the mailbox, which can be too large for solr. My suggested patch is to also limit maximum rows to return on single mailbox searches. Here is the patch: diff -ur dovecot-2.3.17.1-orig/src/plugins/fts-solr/fts-backend-solr.c dovecot-2.3.17.1-new/src/plugins/fts-solr/fts-backend-solr.c --- dovecot-2.3.17.1-orig/src/plugins/fts-solr/fts-backend-solr.c 2021-12-03 12:48:47.000000000 +0100 +++ dovecot-2.3.17.1-new/src/plugins/fts-solr/fts-backend-solr.c 2022-01-09 01:33:23.401341959 +0100 @@ -837,7 +837,7 @@ str = t_str_new(256); str_printfa(str, "wt=xml&fl=uid,score&rows=%u&sort=uid+asc&q=%%7b!lucene+q.op%%3dAND%%7d", - status.uidnext); + I_MIN(status.uidnext,SOLR_MAX_MULTI_ROWS)); prefix_len = str_len(str); if (solr_add_definite_query_args(str, args, and_args)) { John

1 0

Can't log in from Evolution or Roundcube
by Ken Wright 09 Jan '22

09 Jan '22

When I try to log in to my mail server (ubuntu 20.04, Postfix 3.4.13, Dovecot 2.3.7.2) I get a response saying "Source stream returned no data”. At least to me, that's not particularly informative. Is it any more informative to anyone else? Ken

3 10

Sv: banning
by Sebastian Nielsen 08 Jan '22

08 Jan '22

I would say, lock accounts to for example IP address, ASN or GeoIP. This can be accomplished simply by a custom login handler, which also checks IP against database. And first time users, and those who change country/ISP/IP have to simply logon to a web interface (where 2FA can be required and also Captcha) and add their IPs/ASNs/Geo's. For a larger user base, I would recommend GeoIP and no web interface, save country of first login to database, and subsequent logins must originate from same country. Users that want to reset have to contact support. If you are a web hotel who only sell service to a specific country at all, lock the ports in firewall to that GeoIP. For smaller user base, like 50-100 users, I would recommend locking to ASN and providing a web interface where multiple ASN can be added. So people syncing from mobile and home can succeed. For very small user base, like 10's of users, just plan lock to IP. By connecting IP to accounts, you greatly reduce the attack surface.

1 0

TLS connection closed unexpectedly
by Ken Wright 08 Jan '22

08 Jan '22

I reinstalled Dovecot this evening, because I haven't been able to receive emails recently. After configuring and adjusting for the use of PostfixAdmin, I get the following error message in Evolution:; Failed to open folder. The reported error was "Failed to authenticate: TLS connection closed unexpectedly". Does anyone recognize this error? Ken

6 8

Update from 2.3.16 to 2.3.17 Received invalid SSL certificate: unable to get certificate CRL
by Salatiel Filho 08 Jan '22

08 Jan '22

Hi, after updating from dovecot.x86_64 2:2.3.16-2 to 2:2.3.17.1-1 on AlmaLinux 8 my dovecot replication stopped working. Log is full of Error: doveadm server disconnected before handshake: Received invalid SSL certificate: unable to get certificate CRL: /CN=my.domain.redacted (check ssl_client_ca_* settings?) No configuration has changed on my side. My certificate is a wildcard certificate ( not sure if related ). I am also replicating over tcps. Anyone else facing this issue? Atenciosamente/Kind regards, Salatiel

1 0

Sieve scripts igniored
by Sam R 07 Jan '22

07 Jan '22

Hello, I have an issue with Sieve plugin, I can drive rules remotely with sieve:// myserver.fr:4190/?tls=YES, the rules are well created under /home/vmail/name.firstname, but these are never executed. I have also read https://doc.dovecot.org/configuration_manual/sieve/troubleshooting/, but I don't see any evident mistake. here is my dovecot -n : # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.10.0-8-amd64 x86_64 Debian 11.0 ext4 # Hostname: mail.xxx.fr auth_debug = yes auth_gssapi_hostname = $ALL auth_krb5_keytab = /etc/dovecot/dovecot.keytab auth_mechanisms = login plain gssapi mail_location = maildir:/home/vmail/%n/Maildir/ mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relationa l regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttex t 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 } passdb { driver = pam } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap lmtp sieve pop3" service lmtp { executable = lmtp -L unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } ssl = required ssl_cert = </etc/letsencrypt/live/mail.xxx.fr/fullchain.pem ssl_client_ca_dir = /etc/ssl/certs ssl_client_ca_file = /etc/letsencrypt/live/mail.xxx.fr/chain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } userdb { args = uid=vmail gid=vmail home=/home/vmail/%u allow_all_users=yes driver = static } userdb { driver = passwd } protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = " sieve" } Thanks for helping. kind regards. Samuel

3 3

feature-request: make received-header on submission optional or at least drop the ip in it
by dc-ml＠dvl.werbittewas.de 07 Jan '22

07 Jan '22

hi. we're just trying to re-structure a system and want to use dovcots submission-ability. because the github-repository have no entry for any issues at all, we're sending this feature-fequest to this ML. unfortunately there doesn't seem to be any option to drop the received-header at all or at least hide the IP of the user. because the client-ip is covered by GDPR as personal data and so it should never shown to others without a certain reason, we want to hide it, but there's no "submission_add_received_header"-option like for lmtp and it doesn't seem to be any other option to hide this information. maybe this is possible to implement in near future? thanks a lot. best regards d.

8 18

Dovecot fixing maildir message size?
by Grant Keller 07 Jan '22

07 Jan '22

We recently updated dovecot from 2.1.17 to 2.3.10. It used to be when we encountered the following error: Jan 6 15:29:20 d.imapd.sonic.net dovecot: imap(momomo): session=aBd2O/LULMu4F6ia Error: Mailbox INBOX: UID=1: read(/var/spool/mail/07/00/momomo/cur/1510707300.12345_0.a.spam,S=1234:2,) failed: Cached message size larger than expected (1234 > 704, box=INBOX, UID=1) (read reason=) Dovecot would fix the size by renaming the file. Now this doesn't appear to be the case. Was there a change in behaviour, or is there an option I need to enable now to have dovecot auto fix this?

1 0

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

07 Jan '22

Hello, I made serveral tests, never had a problemm woth dovecot version 2.3.4 with 2.3.13 things get worse and dovecot crashes. I might have read someting in the release notes of dovecot 2.3.13. that there is a problem. Regards Oliver > On 1/2/22 3:08 PM, John Fawcett wrote: >> 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. >> > > This Solr instance is not configured properly for dovecot.? Most of the > fields are configured as multiValued (which is why you see an array > rather than a single value), and the response is JSON.? A Solr instance > that is properly configured for dovecot would return XML, not JSON. > > You're going to want to provide a proper solrconfig.xml and > managed-schema file, restart Solr or reload the core for dovecot, and > do > a full reindex.? At the following URL, you can find the shell script > that I use to do a full reindex: > > https://apaste.info/tK1B > > At the following URL are links to the solrconfig.xml and schema that > are > appropriate for dovecot.? These instructions say to name the schema > file > "schema.xml" ... this will work, as long as Solr has read-write access > to the conf directory so it can rename the file to "managed-schema".? > If > it doesn't, then you should name the file "managed-schema" yourself. > > https://doc.dovecot.org/configuration_manual/fts/solr/ > > Thanks, > Shawn

2 2

Doveadm auth test fails
by Ken Wright 07 Jan '22

07 Jan '22

I've been having trouble logging into my email server (postfix 3.4.13, dovecot 2.3.7.2, postfixadmin 3.3.8). I decided to try the doveadm auth test, and got the following result: kwright@grace:~$ sudo doveadm auth test me(a)mydomain.com Password: passdb: me(a)mydomain.com auth failed extra fields: user=me(a)mydomain.com I logged in to PostfixAdmin and made sure I was using the correct password, but got exactly the same result afterward. Should I have restarted Dovecot after changing the password? I'm totally confused by this problem; any and all suggestions will be gratefully received! Ken

3 6

Enable push notifications for all users
by Felix Ingram 06 Jan '22

06 Jan '22

Hello all, Is there a way to enable push notifications for all users, rather than having to enable them one by one? My thinking was to set mail_attribute_dict to a static file but I can’t work out what I would need to put in it. (I’ve now realised that that will not allow me to have other attributes to be different per user, but that’s not a real issue with my use case) If a flat file isn’t the answer, then is a SQL dict my best bet? Thanks in advance, Felix

2 4

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

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

How to set LMTP over TLS for incoming emails in exim and dovecot
by Zakaria 01 Jan '22

01 Jan '22

1 0

cumulative resource limit exceeded
by Mats Mellstrand 31 Dec '21

31 Dec '21

Hi I’m running dovecot-2.3.15 and dovecot-pigeonhole-0.5.15 on FreeBSD 13 To day i suddenly get errors in my personal logfile (.dovecot.sieve.log) sieve: info: started log at Dec 29 20:26:42. .dovecot: error: cumulative resource usage limit exceeded. Is there anything I can do about this error? /mm

3 2

modernizing dovecot.conf
by Laura Steynes 30 Dec '21

30 Dec '21

Happy Holidays, And if you like me are working throughout so more senior engineers get their holidays, my condolences hah Taking the time to bring our dovecot.conf into the 2021/22 era .since its quiet time of year, Do I read it right that where we have things like service imap { process_limit = 1024 executable = imap imap-postlogin are not needed now ? and process limit is a global option? things like pop3/imap_client_workarounds = fooy are now global options, not to be in protocol { } sections ? I am reading the example conf files and see these outside the protocol sections where they have in the past lived, this is what makes me think they are now global and not needed in sub sections. but I may be missing some linking going from file to file , we have forever updated our single config file, just fixing whatever breaks when major versions break something, easier to find options in one file, rather than trying to sift through 40 included files like I am looking at now :-)

4 7

Six failed tests on openindiana (Opensolaris derivative)
by Friedrich Kink 29 Dec '21

29 Dec '21

Hi all, I'm new to this list, so please forgive me if I violate netiquette (and let me know how to improve, because it is not at all my intent). I want to create two packages (dovecot and dovecot-2.3-pigeonhole) hosted by openindiana.org. First of all, everything compiles fine and works as expected, but (there is always a but ;-)) 6 out of 41540 tests failed. To build a clean package I'd like to understand the nature of the failed tests and even more would like to fix the tests. I tried to find some hints how to tackle down the issue but was not successful so far. dovecot version 2.3.17.1, gcc version (OpenIndiana 7.5.0-il-0) 7.5.0 configure options: --sysconfdir=/etc \ --with-gssapi=plugin \ --with-ldap=plugin \ --with-sql=plugin \ --with-lua=plugin \ --with-ssl=openssl \ --with-sodium \ --with-mysql \ --with-pgsql failed tests: array_free ........................................................... : ok $(SOURCE_DIR)/src/lib/test-backtrace.c:21: Assert failed: strstr(str_c(bt), "main") != NULL backtrace_append ..................................................... : FAILED $(SOURCE_DIR)/src/lib/test-backtrace.c:45: Assert failed: strstr(bt, "main") != NULL backtrace_get ........................................................ : FAILED base32_encode() with padding ......................................... : ok buffer_replace() ..................................................... : ok $(SOURCE_DIR)/src/lib/test-buffer-istream.c:55: Assert failed: buffer_append_full_file(result, TEST_FILENAME, SIZE_MAX, &error) == BUFFER_APPEND_READ_ERROR $(SOURCE_DIR)/src/lib/test-buffer-istream.c:56: Assert failed: error != NULL && *error != '\0' buffer_append_full_file .............................................. : FAILED buffer_append_full_istream ........................................... : ok connection idle kill ................................................. : ok $(SOURCE_DIR)/src/lib/test-connection.c:563: Assert failed: !received_quit $(SOURCE_DIR)/src/lib/test-connection.c:563: Assert failed: !received_quit connection handshake failed (version) ................................ : FAILED connection handshake failed (handshake_args) ......................... : ok file_cache_switch_fd ................................................. : ok $(SOURCE_DIR)/src/lib-test/test-common.c:245: Assert failed: suppress == TRUE Error: fstat(.test_file_cache) failed: Bad file number $(SOURCE_DIR)/src/lib-test/test-common.c:245: Assert failed: suppress == TRUE Error: mmap_anon(.test_file_cache, 4096) failed: Not enough space $(SOURCE_DIR)/src/lib-test/test-common.c:245: Assert failed: suppress == TRUE Error: mremap_anon(.test_file_cache, 8192) failed: Not enough space file_cache_errors .................................................... : FAILED file_create_locked() ................................................. : ok ostream file send istream file ....................................... : ok $(SOURCE_DIR)/src/lib/test-ostream-file.c:172: Assert failed: input2->v_offset == 10 $(SOURCE_DIR)/src/lib/test-ostream-file.c:173: Assert failed: output->offset == 14 ostream file send istream sendfile() ................................. : FAILED ostream multiplex (simple) ........................................... : ok Again, compilation works clean without any warning. If you could provide some hints how to start would be great. I know I'm kind of inch picker but want to provide best experience to possible users and not give any chance to complain back to dovecot community. kind regards, Fritz

2 1

dovecot panic
by tobisworld＠gmail.com 27 Dec '21

27 Dec '21

Hi list since today I receive dovecot panics in my mail logs, whenever I want to access on my inbox in my mailclient (evolution) Details: dovecot --version 2.3.17.1 (476cd46418) Centos 7 (latest updates) x86 architecture mailbox stored in NFS > Panic: file mail-index-transaction-finish.c: line 185 (mail_index_transaction_get_uid): assertion failed: (seq <= t->view- >map->hdr.messages_count) > Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7fb86f592142] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7fb86f59224e] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf72fe) [0x7fb86f5a02fe] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf73a1) [0x7fb86f5a03a1] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fb86f4eee38] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xf438d) [0x7fb86f95b38d] - > /usr/lib64/dovecot/libdovecot-storage.so.0(+0xf43da) [0x7fb86f95b3da] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_index_transaction_finish+0x177) [0x7fb86f95ba87] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xf9ad6) [0x7fb86f960ad6] - > /usr/lib64/dovecot/libdovecot- storage.so.0(mail_index_transaction_commit_full+0x9d) [0x7fb86f960fad] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_index_transaction_commit+0x1c) [0x7fb86f96106c] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_cache_set_seq_corrupted_reason+0x61) [0x7fb86f94a921] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_set_mail_cache_corrupted+0xed) [0x7fb86f8b9bbd] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x7a3e9) [0x7fb86f8e13e9] - > /usr/lib64/dovecot/libdovecot-storage.so.0(+0x7a6b0) [0x7fb86f8e16b0] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_get_physical_size+0x38) [0x7fb86f8a6ba8] -> /usr/libexec/dovecot//lib20_mail_log_plugin.so(+0x2465) [0x7fb86e49b465] -> /usr/libexec/dovecot//lib15_notify_plugin.so(notify_contexts_mail_copy+ 0x5c) [0x7fb86e69f3ec] -> /usr/libexec/dovecot//lib15_notify_plugin.so(+0x25d4) [0x7fb86e6a05d4] -> /usr/libexec/dovecot//lib10_quota_plugin.so(+0x102ae) [0x7fb86eab72ae] -> /usr/libexec/dovecot//lib01_acl_plugin.so(+0xef3e) [0x7fb86eccef3e] -> /usr/lib64/dovecot/libdovecot- storage.so.0(+0x50c4c) [0x7fb86f8b7c4c] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_move+0x58) [0x7fb86f8b7ec8] -> dovecot/imap(+0x1175b) [0x55a2b1a5375b] -> dovecot/imap(command_exec+0x64) [0x55a2b1a61f04] -> dovecot/imap(+0x1dde2) [0x55a2b1a5fde2] -> dovecot/imap(+0x1de71) [0x55a2b1a5fe71] -> dovecot/imap(+0x1e039) [0x55a2b1a60039] -> dovecot/imap(client_handle_input+0x205) [0x55a2b1a602f5] -> dovecot/imap(client_input+0x79) [0x55a2b1a608d9] I attached output from dovecot-sysreport here to this report Best regards tobi

1 1

Re: Dovecot does not start on MacOS 12.01
by Steven Smith 19 Dec '21

19 Dec '21

Re: https://www.mail-archive.com/dovecot@dovecot.org/msg84784.html <https://www.mail-archive.com/dovecot@dovecot.org/msg84784.html> I just upgraded to macOS 12.1, ran into this issue, and discovered this thread from the error message. Is there a viable workaround or patch yet? I tried the workaround in this thread, and still see these issues. Set default_vsz_limit = 0 in ./conf.d/10-master.conf. Observe that: dovecot now launches without the setrlimit(RLIMIT_DATA, 268435456) error at the command line However, the mail-err.log is still filled with these errors (below), perhaps for the child processes. Steve > Dec 19 11:22:06 imap-login: Error: Dec 19 11:22:06 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > Dec 19 11:22:06 imap-login: Error: Dec 19 11:22:06 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > Dec 19 11:22:06 imap-login: Error: Dec 19 11:22:06 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > Dec 19 11:22:06 imap-login: Error: Dec 19 11:22:06 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > Dec 19 11:22:06 imap-login: Error: Dec 19 11:22:06 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > Dec 19 11:22:06 imap-login: Fatal: master: service(imap-login): child 4629 returned error 89 (Fatal failure) > Dec 19 11:22:06 master: Error: service(imap-login): command startup failed, throttling for 2.000 secs > Dec 19 11:22:06 imap-login: Fatal: master: service(imap-login): child 4630 returned error 89 (Fatal failure) > Dec 19 11:22:06 imap-login: Fatal: master: service(imap-login): child 4628 returned error 89 (Fatal failure) > Dec 19 11:22:06 imap-login: Fatal: master: service(imap-login): child 4627 returned error 89 (Fatal failure) > Dec 19 11:22:06 imap-login: Fatal: master: service(imap-login): child 4619 returned error 89 (Fatal failure) > Dec 19 11:22:06 imap-login: Error: Dec 19 11:22:06 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > Dec 19 11:22:06 imap-login: Fatal: master: service(imap-login): child 4631 returned error 89 (Fatal failure) > Dec 19 11:22:09 imap-login: Error: Dec 19 11:22:09 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > Dec 19 11:22:09 imap-login: Fatal: master: service(imap-login): child 4638 returned error 89 (Fatal failure) > Dec 19 11:22:09 master: Error: service(imap-login): command startup failed, throttling for 4.000 secs > On Mon, 1 Nov 2021 14:55:25 +0200, Aki Tuomi said: > > I think this is happening because MacOS no longer supports RLIMIT_DATA. We'll > try to look into this. default_vsz_limit = 0 seems good enough workaround. > Aki

1 2

Undefined symbol using fts-flatcurve with repo.dovecot.org packages
by Mike Acar 18 Dec '21

18 Dec '21

Hi, I'm trying to use dovecot-fts-flatcurve with dovecot 2:2.3.15-1+debian10 from repo.dovecot.org, but it looks like the package doesn't include ICU, which fts-flatcurve requires. After compilation and installation, I get an error from doveadm: doveadm fts-flatcurve stats -u user INBOX Fatal: Couldn't load required plugin /usr/lib/dovecot/modules/lib21_fts_flatcurve_plugin.so: dlopen() failed: /usr/lib/dovecot/modules/lib21_fts_flatcurve_plugin.so: undefined symbol: _ZTIN6icu_638ByteSinkE Unmangled, I think that's this symbol: U typeinfo for icu_63::ByteSink I checked the rules file from dovecot_2.3.15-1%2Bdebian10.debian.tar.xz and it appears that configure doesn't include --with-icu. Is there a plan to include this in a future release? -- | Mike Acar | | mike at waspfactory dot org |

1 0

Re: Re: invalid vsize-hdr
by Станислав Дырив 17 Dec '21

17 Dec '21

it helps for me (dovecot 2.2.36 @ centos7): #delete index files: find /path/to/user/maildir/ -type f -name dovecot.index* -delete find /path/to/user/maildir/ -type f -name dovecot-uidlist -delete #then re-create index by command: doveadm force-resync -u "user(a)domain.com" '*'

1 0

Can dovecot be leveraged to exploit Solr/Log4shell?
by Joseph Tam 15 Dec '21

15 Dec '21

I'm surprised I haven't seen this mentioned yet. An internet red alert went out Friday on a new zero-day exploit. It is an input validation problem where Java's Log4j module can be instructed via a specially crafted string to fetch and execute code from a remote LDAP server. It has been designated the Log4shell exploit (CVE-2021-44228). Although I don't use it, I immediately thought of Solr, which provides some dovecot installations with search indexing. Can dovecot be made to pass on arbitrary loggable strings to affected versions of Solr (7.4.0-7.7.3, 8.0.0-8.11.0)? Those running Solr to implement Dovecot FTS should look at https://solr.apache.org/security.html#apache-solr-affected-by-apache-log4j-… Joseph Tam <jtam.home(a)gmail.com>

6 8

quota warnings not sent out anymore
by mj 15 Dec '21

15 Dec '21

Hi, We suddenly realised that our maildir quota warnings are no longer sent out. We don't understand why not. This is dovecot 2.3.4.1 on debian 10.11. We use a script to send out the notification, adapted from the dovecot wiki here: (https://doc.dovecot.org/configuration_manual/quota/) Our quota notification script is: > #!/bin/sh > PERCENT=$1 > USER=$2 > cat << EOF | /usr/lib/dovecot/dovecot-lda -d $USER -o "plugin/quota=maildir::noenforcing" > From: noreply(a)domain.com > Subject: quota warning > > Your mailbox is now $PERCENT% full. > > Please delete or archive items to decrease your mailbox size. Our complete doveconf -n output is at the end of this email. When calling the script manually as user root, it works perfectly. But as user vmail or dovecot, no notifications are sent at all. I guess this is relevant: > root@dovecot:/etc/dovecot# ls -l /var/run/dovecot/ > total 8 > srw------- 1 root root 0 Dec 6 00:00 anvil > srw------- 1 root root 0 Dec 6 00:00 anvil-auth-penalty > srw------- 1 dovecot root 0 Dec 6 11:34 auth-client > srw------- 1 dovecot root 0 Dec 6 11:34 auth-login > srw------- 1 root root 0 Dec 6 11:34 auth-master > -rw------- 1 root root 32 Jul 19 17:39 auth-token-secret.dat > srw-rw-rw- 1 vmail vmail 0 Dec 6 11:34 auth-userdb > srw------- 1 dovecot root 0 Dec 6 11:34 auth-worker > srw------- 1 root root 0 Dec 6 11:34 config > srw-rw---- 1 root dovecot 0 Dec 6 11:34 dict > srw-rw---- 1 root dovecot 0 Dec 6 11:34 dict-async > srw------- 1 root root 0 Dec 6 11:34 director-admin > srw-rw-rw- 1 root root 0 Dec 6 11:34 dns-client > srw------- 1 root root 0 Dec 6 11:34 doveadm-server > lrwxrwxrwx 1 root root 25 Dec 6 00:00 dovecot.conf -> /etc/dovecot/dovecot.conf > drwxr-xr-x 2 root root 40 Jul 19 17:39 empty > srw-rw---- 1 root dovecot 0 Dec 6 11:34 imap-hibernate > srw------- 1 root root 0 Dec 6 11:34 imap-master > srw-rw-rw- 1 root root 0 Dec 6 11:34 imap-urlauth > srw------- 1 dovecot root 0 Dec 6 11:34 imap-urlauth-worker > srw-rw-rw- 1 root root 0 Dec 6 11:34 indexer > srw------- 1 dovecot root 0 Dec 6 11:34 indexer-worker > srw------- 1 dovecot root 0 Dec 6 11:34 ipc > srw-rw-rw- 1 root root 0 Dec 6 11:34 lmtp > srw------- 1 root root 0 Dec 6 11:34 log-errors > drwxr-x--- 2 root nogroup 120 Dec 6 11:34 login > srw------- 1 root root 0 Dec 6 11:34 master > -rw------- 1 root root 6 Dec 6 00:00 master.pid > srw------- 1 root root 0 Dec 6 11:34 old-stats > prw------- 1 root root 0 Dec 6 11:34 old-stats-mail > prw------- 1 root root 0 Dec 6 11:34 old-stats-user > srw------- 1 vmail root 0 Dec 6 11:34 quota-warning > srw------- 1 root root 0 Dec 6 11:34 replication-notify > prw------- 1 root root 0 Dec 6 11:34 replication-notify-fifo > srw------- 1 dovecot root 0 Dec 6 11:34 replicator > srw-rw---- 1 vmail vmail 0 Dec 6 11:34 stats-reader > srw-rw---- 1 vmail vmail 0 Dec 6 11:34 stats-writer > drwxr-x--- 2 root nogroup 80 Dec 6 11:34 token-login Can anyone help, and explain what is going on here? Thank you very much in advance for a reply! MJ The doveconf -n output: > root@imap:/etc/dovecot# doveconf -n > # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.5.4 () > # OS: Linux 4.19.0-17-amd64 x86_64 Debian 10.11 xfs > # Hostname: mail.company.com > auth_debug = yes > auth_failure_delay = 10 secs > auth_master_user_separator = * > auth_mechanisms = plain login > auth_username_format = %Ln > auth_verbose = yes > auth_verbose_passwords = sha1 > default_vsz_limit = 512 M > deliver_log_format = %f | %s | msgid=%m: %$ > lda_mailbox_autocreate = yes > lda_mailbox_autosubscribe = yes > login_greeting = Dovecot ready. > login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c lport=%a > mail_gid = vmail > mail_location = maildir:/var/vmail/%Ln/Maildir:LAYOUT=fs:DIRNAME=mAildir > mail_plugins = acl lazy_expunge zlib quota mail_log notify > mail_shared_explicit_inbox = yes > 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 ihave > namespace { > list = children > location = maildir:/var/vmail/%%u/Maildir:LAYOUT=fs:DIRNAME=mAildir:INDEX=/var/vmail/%u/shared/%%u > prefix = shared/%%n/ > separator = / > subscriptions = no > type = shared > } > namespace inbox { > inbox = yes > location = > mailbox "Deleted items" { > special_use = \Trash > } > mailbox Drafts { > special_use = \Drafts > } > mailbox Junk { > special_use = \Junk > } > mailbox Sent { > special_use = \Sent > } > mailbox "Sent items" { > special_use = \Sent > } > mailbox Trash { > special_use = \Trash > } > mailbox inbox { > auto = subscribe > } > prefix = > separator = / > type = private > } > passdb { > args = /etc/dovecot/deny.imap > deny = yes > driver = passwd-file > } > passdb { > args = /etc/dovecot/master-users > driver = passwd-file > master = yes > } > passdb { > args = /etc/dovecot/dovecot-ldap.conf.ext > driver = ldap > result_failure = return-fail > } > plugin { > acl = vfile > acl_shared_dict = file:/var/lib/dovecot/db/shared-mailboxes.db > mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename append > mail_log_fields = uid box msgid from subject > quota = maildir > quota_rule = ?:storage=5G > quota_rule2 = Trash:storage=+100M > quota_warning = storage=97%% quota-warning 97 %u > quota_warning2 = storage=95%% quota-warning 95 %u > quota_warning3 = storage=90%% quota-warning 90 %u > quota_warning4 = storage=85%% quota-warning 85 %u > quota_warning5 = storage=80%% quota-warning 80 %u > quota_warning6 = -storage=100%% quota-warning below %u > sieve = ~/.dovecot.sieve > sieve_default = /var/lib/dovecot/default.sieve > sieve_dir = ~/sieve > } > protocols = imap lmtp sieve > service auth { > unix_listener /var/spool/postfix/private/auth { > mode = 0666 > } > unix_listener auth-userdb { > group = vmail > mode = 0666 > user = vmail > } > } > service imap-login { > process_limit = 500 > process_min_avail = 2 > } > service quota-warning { > executable = script /usr/local/bin/quota-warning.sh > unix_listener quota-warning { > user = vmail > } > user = dovecot > } > service stats { > unix_listener stats-reader { > group = vmail > mode = 0660 > user = vmail > } > unix_listener stats-writer { > group = vmail > mode = 0660 > user = vmail > } > } > shutdown_clients = no > ssl = required > ssl_cert = </etc/ssl/letsencrypt/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 > userdb { > args = uid=vmail gid=vmail home=/var/vmail/%n allow_all_users=yes > driver = static > } > userdb { > args = /etc/dovecot/dovecot-ldap.conf.ext > driver = ldap > } > verbose_proctitle = yes > protocol lda { > mail_plugins = acl lazy_expunge zlib quota mail_log notify sieve quota > } > protocol imap { > imap_max_line_length = 2 M > mail_max_userip_connections = 40 > mail_plugins = acl lazy_expunge zlib quota mail_log notify imap_quota imap_acl > }

2 5

dovecot-2.3.17: "Panic: file ioloop.c: line 865"
by Piper Andreas 14 Dec '21

14 Dec '21

Hello, since the upgrade from dovecot-2.3.16 to 2.3.17 I get 'Panic'-errors in the system-log of my replicator hosts. See below for log messages, doveconf-output and gdb-backtrace. Storage filesystem is ZFS. The error seems to be correlated with exactly one user-mailbox, this user is repeatedly noted as 'failed' in replication status, although replication of this mailbox seems to work, as the mailbox status shows always the identical size on both replicators. The error can be produced by forcing replication of this individual mailbox. Is there anything I can do to repair this mailbox? Thanks for any hints, Andreas Example log-messages: Nov 11 07:17:50 vhrz311 dovecot: doveadm(119455): Error: write(<local>) failed: Timed out after 60 seconds Nov 11 07:17:50 vhrz311 dovecot: doveadm(119455): Panic: file ioloop.c: line 865 (io_loop_destroy): assertion failed: (ioloop == cur rent_ioloop) Nov 11 07:17:50 vhrz311 dovecot: doveadm(119455): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7 f4e59419182] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f4e5941929e] -> /usr/lib/dovecot/libdovecot.so.0(+0xf8a5e) [0x7f4e59427a5e] -> /usr/lib/dovecot/libdovecot.so.0(+0xf8b01) [0x7f4e59427b01] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f 4e593744a7] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_destroy+0x2dc) [0x7f4e5944121c] -> dovecot/doveadm-server(+0x46fb6) [0x563d0 150ffb6] -> dovecot/doveadm-server(doveadm_print+0x27) [0x563d01508fb7] -> dovecot/doveadm-server(+0x2b427) [0x563d014f4427] -> dove cot/doveadm-server(+0x2da44) [0x563d014f6a44] -> dovecot/doveadm-server(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x2cf) [0x563d014f7c6f] -> dovecot/doveadm-server(doveadm_cmd_run_ver2+0x43b) [0x563d01508c1b] -> dovecot/doveadm-server(+0x44612) [0x563d0150d612] -> /usr /lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f4e594406d9] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal +0x134) [0x7f4e59442034] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) [0x7f4e594407e0] -> /usr/lib/dovecot/libdovec ot.so.0(io_loop_run+0x38) [0x7f4e59440a18] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f4e593a6a23] -> dovecot/ doveadm-server(main+0x102) [0x563d014e6922] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f4e58bc1bf7] -> dovecot/d oveadm-server(_start+0x2a) [0x563d014e69aa] Nov 11 07:17:50 vhrz311 dovecot: doveadm(119455): Fatal: master: service(doveadm): child 119455 killed with signal 6 (core dumped) 'doveconf -n': # 2.3.17 (e2aa53df5b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.17 (054dddfa) # OS: Linux 4.15.0-162-generic x86_64 Ubuntu 18.04.6 LTS # Hostname: vhrz311.HRZ.Uni-Marburg.DE auth_cache_negative_ttl = 0 auth_cache_size = 10 M auth_master_user_separator = * auth_worker_max_count = 1024 base_dir = /var/run/dovecot/ default_client_limit = 10000 default_vsz_limit = 6 G doveadm_password = # hidden, use -P to show it doveadm_port = 12345 first_valid_gid = 10000 first_valid_uid = 10000 imap_max_line_length = 640 k last_valid_gid = 10000 last_valid_uid = 10000 mail_attribute_dict = file:%h/mdbox/dovecot-attributes mail_gid = 10000 mail_location = mdbox:%h/mdbox mail_plugins = " mail_log notify zlib notify replication" mail_privileged_group = mail mail_uid = 10000 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 { hidden = no inbox = yes list = yes location = prefix = separator = / subscriptions = yes type = private } passdb { args = /etc/dovecot.deny deny = yes driver = passwd-file } passdb { args = /etc/dovecot/private/passwd.masterusers driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap.hrz.conf.ext driver = ldap name = passdb_ldap_hrz } passdb { args = /etc/dovecot/dovecot-ldap.staff.conf.ext driver = ldap name = passdb_ldap_staff } passdb { args = /etc/dovecot/dovecot-ldap.students.conf.ext driver = ldap name = passdb_ldap_students } plugin { mail_replica = tcp:172.25.1.95 sieve = file:~/sieve;active=~/.dovecot.sieve sieve_default = /var/lib/dovecot/default.sieve sieve_max_actions = 55 sieve_max_redirects = 50 } pop3_uidl_format = %08Xv%08Xu postmaster_address = postmaster(a)hrz.uni-marburg.de protocols = imap pop3 lmtp sieve replication_dsync_parameters = -d -n INBOX -l 30 -U replication_max_conns = 20 service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service auth-worker { user = $default_internal_user } service auth { client_limit = 10000 } service config { process_min_avail = 8 } service doveadm { inet_listener { port = 12345 } vsz_limit = 6 G } service imap-login { process_min_avail = 64 service_count = 0 } service imap { process_limit = 8192 } service lmtp { inet_listener lmtp { port = 24 } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 8 service_count = 0 } service pop3-login { process_min_avail = 8 service_count = 0 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } service submission-login { service_count = 0 } ssl = required ssl_ca = </etc/ssl/certs/umr-chain.pem ssl_cert = </etc/ssl/certs/vhrz311.hrz.uni-marburg.de.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_require_crl = no userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf.ext driver = ldap name = userdb_ldap } protocol imap { imap_metadata = yes mail_max_userip_connections = 25 mail_plugins = " mail_log notify zlib notify replication imap_zlib" } protocol lmtp { mail_plugins = " mail_log notify zlib notify replication sieve" } gdb: gdb /usr/lib/dovecot/doveadm-server /var/vmail/system-cores/core GNU gdb (Ubuntu 8.1.1-0ubuntu1) 8.1.1 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/lib/dovecot/doveadm-server...(no debugging symbols found)...done. [New LWP 119455] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/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:51 51 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x00007f4e58be0921 in __GI_abort () at abort.c:79 #2 0x00007f4e59427a11 in ?? () from /usr/lib/dovecot/libdovecot.so.0 #3 0x00007f4e59427b01 in ?? () from /usr/lib/dovecot/libdovecot.so.0 #4 0x00007f4e593744a7 in i_panic () from /usr/lib/dovecot/libdovecot.so.0 #5 0x00007f4e5944121c in io_loop_destroy () from /usr/lib/dovecot/libdovecot.so.0 #6 0x0000563d0150ffb6 in ?? () #7 0x0000563d01508fb7 in doveadm_print () #8 0x0000563d014f4427 in ?? () #9 0x0000563d014f6a44 in ?? () #10 0x0000563d014f7c6f in doveadm_cmd_ver2_to_mail_cmd_wrapper () #11 0x0000563d01508c1b in doveadm_cmd_run_ver2 () #12 0x0000563d0150d612 in ?? () #13 0x00007f4e594406d9 in io_loop_call_io () from /usr/lib/dovecot/libdovecot.so.0 #14 0x00007f4e59442034 in io_loop_handler_run_internal () from /usr/lib/dovecot/libdovecot.so.0 #15 0x00007f4e594407e0 in io_loop_handler_run () from /usr/lib/dovecot/libdovecot.so.0 #16 0x00007f4e59440a18 in io_loop_run () from /usr/lib/dovecot/libdovecot.so.0 #17 0x00007f4e593a6a23 in master_service_run () from /usr/lib/dovecot/libdovecot.so.0 #18 0x0000563d014e6922 in main ()

4 5

Dovecot, Solr (FTS) and iOS body search
by Ben Howard 13 Dec '21

13 Dec '21

I had a question about full text search with Dovecot, Solr with iOS as a client (the built in default mail client). Does anyone happen to know if it's possible to get the iOS mail client to search bodies of email via IMAP with Dovecot and Solr on the server? I've looked at the IMAP queries being sent to Solr and regardless of iOS settings only the subject or to/cc/from seem to get queried. i.e.: test search query: Foobar Request [dovecot] webapp=/solr path=/select params={q={!lucene+q.op%3DAND}subject:Foobar&fl=uid,score&sort=uid+asc (trimmed for space) test search query with 'message' selected as search via the GUI in iOS mail app: Foobar 2021-12-12 22:16:43.840 INFO (qtp1309129055-21) [ x:dovecot] o.a.s.c.S.Request [dovecot] webapp=/solr path=/select params={q={!lucene+q.op%3DAND}to:Foobar+OR+cc:Foobar+OR+from:Foobar+OR+subject:Foobar&fl=uid,score&sort=uid+asc (trimmed for space) I also put Wireshark between an iOS device and the mail server to see the IMAP commands being issued client side and it matches with what Dovecot is seeing - i.e. only to/cc/from/subject no body queries. dovecot version: 2.3.17.1 (476cd46418), solr 8.11.0 and fts_enforced = yes Is it just not possible for the iOS mail client to search for keywords within the body of emails via IMAP/Dovecot/Solr? Any pointers, or just knowing I should give up, would be most gratefully received. Thanks

1 0

Re: 2.3.17: Panic on LMTP deliveries
by Volker ********* 13 Dec '21

13 Dec '21

It WORKS!!! :-) Great, thanks! Best regards Volker Am 12.12.2021 um 13:00 schrieb Volker: > That´s a good message, thank you very much! > > I will try the patch! > > Kind regards > Volker > > Am 12.12.2021 um 12:48 schrieb Aki Tuomi: >>>> Hello! >>>> >>>> While searching for an explanation for the fact that after updating to >>>> Dovecot 2.3.17_1 (FreeBSD 12.2) I suddenly stopped receiving emails and >>>> following error messages appeared in the dovecot.log, >>>> >>>> /Error: lmtp-server: conn unix:uid=125 [1]: rcptuser(a)domain.tld: >>>> duplicate db: Useruser(a)domain.tld doesn't have home dir set, disabling >>>> duplicate database// >>>> // >>>> //Dec 12 08:42:54 lmtp(user(a)domain.tld)<80363><z7AxDf6ntWHrOQEAp6O1gg>: >>>> Panic: file imem.c: line 65 (i_strconcat): assertion failed: (str1 != NULL) >>>> >>>> /I found your answer here >>>> <https://www.mail-archive.com/dovecot@dovecot.org/msg84893.html>: >>>> >>>> /Problem confirmed. This is a 2.3.17 regression. Tracking internally as >>>> DOP-2659./ >>>> / >>>> Regards, >>>> Stephan./ >>>> >>>> >>>> But what exactly does your answer mean for those affected? >>>> >>>> That all users who use Dovecot and use the whole thing without >>>> "mail_home" and only with "mail_location", must wait until a BugFix >>>> appears to be able to receive emails again? >>>> >>>> >>>> Thanks in advance and have a nice advent sunday >>>> Volker >>>> >>>> P. S.: >>>> In my case dovecot -n shows >>>> >>>> /mail_location = maildir:/var/mail/vhosts/%d/%n// >>>> //mail_home = /var/mail/vhosts/%d/%n >>>> >>>> /so mail_home is even set!/ >>>> / >>>> >>> You can roll back to 2.3.16 as well? >>> >>> Aki >> After looking bit more, this issue is fixed and will be in 2.3.18. If you want, you can try applying >> >> https://github.com/dovecot/core/compare/98f709de%5E..d36d2c59.patch >> >> which should fix this issue. >> >> Aki >

1 0

Send to mailbox + alias??
by postfix＠aecperformance.com 12 Dec '21

12 Dec '21

Is there any way to set postfix/dovecot to: 1. Deliver email to the mailbox -> ie. bob(a)test.com <mailto:bob@test.com> AND 2. Set the email as an alias and send it to the forwarded address -> bobs.boss(a)bosses.com <mailto:bobs.boss@bosses.com> This would be given that both email accounts are set up as virtual_users in MySql. Right now if I set up an alias and mailbox for the same email the alias overrides the mailbox and the email is delivered to the forwarded account and not to the email's mailbox. If the mailbox exists I need the email sent to both the mailbox and the forwarded mailbox. Can I do that? If so, how?

2 1

submission Connection failed: Failed to connect to remote server
by fugee ohu 12 Dec '21

12 Dec '21

I'm getting this error when I try to send mail mail dovecot: submission(username-here)<113012><tY+KjubSZJJHvuNn>: Debug: smtp-client: conn 127.0.0.1:25 [1]: Connection failed: Failed to connect to remote server

2 1

Re[7]: Replicator bug report
by Daniel Miller 12 Dec '21

12 Dec '21

On 12/7/2021 12:29:49 PM, "Daniel Miller" <dmiller(a)amfes.com> wrote: >>service replicator { >> vsz_limit = 2G >>} >> >>Aki >> >Tried that - got another one. I just tried setting service replicator { vcsz_limit = 5G } and I still get: Dec 7 15:08:25 bubba dovecot: replicator: Panic: data stack: Out of memory when allocating 4294967336 bytes -- Daniel

3 4

2.3.17: Panic on LMTP deliveries
by Volker 12 Dec '21

12 Dec '21

Hello! While searching for an explanation for the fact that after updating to Dovecot 2.3.17_1 (FreeBSD 12.2) I suddenly stopped receiving emails and following error messages appeared in the dovecot.log, /Error: lmtp-server: conn unix:uid=125 [1]: rcpt user(a)domain.tld: duplicate db: User user(a)domain.tld doesn't have home dir set, disabling duplicate database// // //Dec 12 08:42:54 lmtp(user(a)domain.tld)<80363><z7AxDf6ntWHrOQEAp6O1gg>: Panic: file imem.c: line 65 (i_strconcat): assertion failed: (str1 != NULL) /I found your answer here <https://www.mail-archive.com/dovecot@dovecot.org/msg84893.html>: /Problem confirmed. This is a 2.3.17 regression. Tracking internally as DOP-2659./ / Regards, Stephan./ But what exactly does your answer mean for those affected? That all users who use Dovecot and use the whole thing without "mail_home" and only with "mail_location", must wait until a BugFix appears to be able to receive emails again? Thanks in advance and have a nice advent sunday Volker P. S.: In my case dovecot -n shows /mail_location = maildir:/var/mail/vhosts/%d/%n// //mail_home = /var/mail/vhosts/%d/%n /so mail_home is even set!/ /

2 2

dovecot error
by Rajesh M 11 Dec '21

11 Dec '21

hello all we were seeing an error as such in dovecot.log for the first time we use sogo for active sync dovecot: master: Warning: service(dict): process_limit (100) reached, client connections are being dropped once we restarted sogo service this issue got resolved could someone please guide us on how to resolve the above please find below dovecot config file ####################################### # More details about Dovecot settings: # - http://wiki2.dovecot.org/ # - http://wiki2.dovecot.org/Variables # Listen addresses. # - '*' means all available IPv4 addresses. # - '[::]' means all available IPv6 addresses. # Listen on all available addresses by default listen = * #base_dir = /var/run/dovecot mail_plugins = quota mailbox_alias acl mail_log notify stats # Enabled mail protocols. protocols = pop3 imap sieve lmtp default_client_limit = 2400 # User/group who owns the message files: mail_uid = 2000 mail_gid = 2000 # Assign uid to virtual users. first_valid_uid = 2000 last_valid_uid = 2000 # Logging. Reference: http://wiki2.dovecot.org/Logging # # Use syslog syslog_facility = local5 # Log file path if we use internal log system #log_path = /var/log/dovecot/dovecot.log # Debug #mail_debug = yes #auth_verbose = yes #auth_debug = yes #auth_debug_passwords = yes # Possible values: no, plain, sha1. #auth_verbose_passwords = no # SSL: Global settings. # Refer to wiki site for per protocol, ip, server name SSL settings: # http://wiki2.dovecot.org/SSL/DovecotConfiguration ssl_protocols = !SSLv3 ssl = required verbose_ssl = no #ssl_ca = </path/to/ca ssl_cert = </etc/ssl/certificate_key.crt ssl_key = </etc/ssl/certificate_key.crt # Fix 'The Logjam Attack' ssl_cipher_list = ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5 ssl_prefer_server_ciphers = yes # With disable_plaintext_auth=yes AND ssl=required, STARTTLS is mandatory. # Set disable_plaintext_auth=no AND ssl=yes to allow plain password transmitted # insecurely. disable_plaintext_auth = no ssl=yes # Allow plain text password per IP address/net #remote 192.168.0.0/24 { # disable_plaintext_auth = no #} # Mail location and mailbox format. mail_location = maildir:%Lh/Maildir/:INDEX=%Lh/Maildir/ # Authentication related settings. # Append this domain name if client gives empty realm. #auth_default_realm = aaaonlinux.net # Authentication mechanisms. auth_mechanisms = PLAIN LOGIN # Limits the number of users that can be logging in at the same time. # Default is 100. This can be overridden by `process_limit =` in # `service [protocol]` block. # e.g. # protocol imap-login { # ... # process_limit = 500 # } #default_process_limit = 100 # Mail delivery log format deliver_log_format = from=%{from}, envelope_sender=%{from_envelope}, subject=%{subject}, msgid=%m, size=%{size}, %$ service auth { unix_listener /var/spool/postfix/private/dovecot-auth { user = postfix group = postfix mode = 0666 } unix_listener auth-master { user = vmail group = vmail mode = 0666 } unix_listener auth-userdb { user = vmail group = vmail mode = 0660 } } # LMTP server (Local Mail Transfer Protocol). # Reference: http://wiki2.dovecot.org/LMTP service lmtp { user = vmail # For higher volume sites, it may be desirable to increase the number of # active listener processes. A range of 5 to 20 is probably good for most # sites. process_min_avail = 5 # Logging. # Require 'log_path =' in 'protocol lmtp {}' block. executable = lmtp -L # Listening on socket file and TCP unix_listener /var/spool/postfix/private/dovecot-lmtp { user = postfix group = postfix mode = 0600 } inet_listener lmtp { # Listen on localhost (ipv4) address = 127.0.0.1 port = 24 } } # Virtual mail accounts. userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } # Master user. # Master users are able to log in as other users. It's also possible to # directly log in as any user using a master password, although this isn't # recommended. # Reference: http://wiki2.dovecot.org/Authentication/MasterUsers auth_master_user_separator = * passdb { driver = passwd-file args = /etc/dovecot/dovecot-master-users master = yes } plugin { # Quota configuration. # Reference: http://wiki2.dovecot.org/Quota/Configuration quota = dict:user::proxy::quotadict # Set default quota rule if no quota returned from SQL/LDAP query. #quota_rule = *:storage=1G #quota_rule2 = *:messages=0 #quota_rule3 = Trash:storage=1G #quota_rule4 = Junk:ignore # Quota warning. # # If user suddenly receives a huge mail and the quota jumps from # 85% to 95%, only the 95% script is executed. # # Only the command for the first exceeded limit is executed, so configure # the highest limit first. quota_warning = storage=100%% quota-warning 100 %u quota_warning2 = storage=95%% quota-warning 95 %u quota_warning3 = storage=90%% quota-warning 90 %u quota_warning4 = storage=85%% quota-warning 85 %u # allow user to become max 10% (or 50 MB) over quota quota_grace = 10%% #quota_grace = 50 M # Custom Quota Exceeded Message. # You can specify the message directly or read the message from a file. #quota_exceeded_message = Quota exceeded, please try again later. #quota_exceeded_message = </path/to/quota_exceeded_message.txt # Plugin: expire. #expire = Trash 7 Trash/* 7 Junk 30 #expire_dict = proxy::expire # ACL and share folder acl = vfile acl_shared_dict = proxy::acl # By default Dovecot doesn't allow using the IMAP "anyone" or # "authenticated" identifier, because it would be an easy way to spam # other users in the system. If you wish to allow it, #acl_anyone = allow # Pigeonhole managesieve service. # Reference: http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration # Per-user sieve settings. sieve_dir = ~/sieve sieve = ~/sieve/dovecot.sieve # Global sieve settings. sieve_global_dir = /var/vmail/sieve # Note: if user has personal sieve script, global sieve rules defined in # sieve_default will be ignored. Please use sieve_before or # sieve_after instead. #sieve_default = sieve_before = /var/vmail/sieve/dovecot.sieve #sieve_after = # The maximum number of redirect actions that can be performed during a # single script execution. # The meaning of 0 differs based on your version. For pigeonhole-0.3.0 and # beyond this means that redirect is prohibited. For older versions, # however, this means that the number of redirects is unlimited. sieve_max_redirects = 30 # Use recipient as vacation message sender instead of null sender (<>). sieve_vacation_send_from_recipient = yes # Reference: http://wiki2.dovecot.org/Plugins/MailboxAlias mailbox_alias_old = Sent mailbox_alias_new = Sent Messages mailbox_alias_old2 = Sent mailbox_alias_new2 = Sent Items # Events to log. `autoexpunge` is included in `expunge` # Defined in https://github.com/dovecot/core/blob/master/src/plugins/mail-log/mail-log-p… mail_log_events = delete undelete expunge mailbox_delete mailbox_rename mail_log_fields = uid box msgid size from subject # stats # # how often to session statistics (must be set) stats_refresh = 30 secs # track per-IMAP command statistics (optional) stats_track_cmds = yes } service stats { fifo_listener stats-mail { user = vmail mode = 0644 } inet_listener { address = 127.0.0.1 port = 24242 } } service quota-warning { executable = script /usr/local/bin/dovecot-quota-warning.sh unix_listener quota-warning { user = vmail group = vmail mode = 0660 } } service dict { unix_listener dict { mode = 0660 user = vmail group = vmail } } dict { #expire = db:/var/lib/dovecot/expire/expire.db quotadict = mysql:/etc/dovecot/dovecot-used-quota.conf acl = mysql:/etc/dovecot/dovecot-share-folder.conf } protocol lda { # Reference: http://wiki2.dovecot.org/LDA mail_plugins = $mail_plugins sieve lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes # Log file path if we use internal log system #log_path = /var/log/dovecot/sieve.log } protocol lmtp { # Log file path if we use internal log system #log_path = /var/log/dovecot/lmtp.log # Plugins mail_plugins = quota sieve # Address extension delivery lmtp_save_to_detail_mailbox = yes recipient_delimiter = + } protocol imap { mail_plugins = $mail_plugins imap_quota imap_acl imap_stats imap_client_workarounds = tb-extra-mailbox-sep #process_limit = 1000 # Maximum number of IMAP connections allowed for a user from each IP address. # NOTE: The username is compared case-sensitively. # Default is 10. # Increase it to avoid issue like below: # "Maximum number of concurrent IMAP connections exceeded" mail_max_userip_connections = 100 } protocol pop3 { mail_plugins = $mail_plugins pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv # Maximum number of IMAP connections allowed for a user from each IP address. # NOTE: The username is compared case-sensitively. # Default is 10. mail_max_userip_connections = 100 #process_limit = 1000 # POP3 logout format string: # %i - total number of bytes read from client # %o - total number of bytes sent to client # %t - number of TOP commands # %p - number of bytes sent to client as a result of TOP command # %r - number of RETR commands # %b - number of bytes sent to client as a result of RETR command # %d - number of deleted messages # %m - number of messages (before deletion) # %s - mailbox size in bytes (before deletion) # Default format doesn't have 'in=%i, out=%o'. #pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s, in=%i, out=%o } # Login processes. Refer to Dovecot wiki for more details: # http://wiki2.dovecot.org/LoginProcess ################### LAST LOGIN START protocol imap { # Append plugin name `last_login` here mail_plugins = last_login } protocol pop3 { # Append plugin name `last_login` here mail_plugins = last_login } dict { # Add this line. For FreeBSD, please replace the path by # /usr/local/etc/dovecot/dovecot-last-login.conf lastlogin = mysql:/etc/dovecot/dovecot-last-login.conf } plugin { # Add 2 lines last_login_dict = proxy::lastlogin last_login_key = last-login/%s/%u/%d/%r/%l } ################### LAST LOGIN END # Login processes. Refer to Dovecot wiki for more details: # http://wiki2.dovecot.org/LoginProcess ###################### service imap-login { service_count = 0 process_min_avail = 50 process_limit = 256 } service imap { process_limit = 2048 process_min_avail = 50 service_count = 1 vsz_limit = 512 M } ######################## service pop3-login { service_count = 0 process_min_avail = 25 process_limit = 256 } service pop3 { service_count = 1 process_limit = 256 process_min_avail = 25 } ########################## ############## #service imap-login { #inet_listener imap { # port = 143 #} #inet_listener imaps { # port = 993 # ssl = yes #} # service_count = 1 # To avoid startup latency for new client connections, set process_min_avail # to higher than zero. That many idling processes are always kept around # waiting for new connections. #process_min_avail = 0 # number of simultaneous IMAP connections # process_limit = 500 # vsz_limit should be fine at its default 64MB value #vsz_limit = 64M #} #service pop3-login { #inet_listener pop3 { # port = 110 #} #inet_listener pop3s { # port = 995 # ssl = yes #} # service_count = 1 # number of simultaneous POP3 connections #process_limit = 500 #} ############## Commented by service managesieve-login { inet_listener sieve { # Listen on localhost (ipv4) address = 127.0.0.1 port = 4190 } } namespace { type = private separator = / prefix = inbox = yes # Refer to document for more details about alias mailbox: # http://wiki2.dovecot.org/MailboxSettings # # Sent mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox "Sent Items" { auto = no special_use = \Sent } mailbox Drafts { auto = subscribe special_use = \Drafts } # Trash mailbox Trash { auto = subscribe special_use = \Trash } mailbox "Deleted Messages" { auto = no special_use = \Trash } # Junk mailbox Junk { auto = subscribe special_use = \Junk } mailbox Spam { auto = no special_use = \Junk } mailbox "Junk E-mail" { auto = no special_use = \Junk } # Archive mailbox Archive { auto = no special_use = \Archive } mailbox Archives { auto = no special_use = \Archive } } namespace { type = shared separator = / prefix = Shared/%%u/ location = maildir:%%Lh/Maildir/:INDEX=%%Lh/Maildir/Shared/%%Ld/%%Ln # this namespace should handle its own subscriptions or not. subscriptions = yes list = children } # Public mailboxes. # Refer to Dovecot wiki page for more details: # http://wiki2.dovecot.org/SharedMailboxes/Public #namespace { # type = public # separator = / # prefix = Public/ # location = maildir:/var/vmail/public:CONTROL=%Lh/Maildir/public:INDEXPVT=%Lh/Maildir/public # # # Allow users to subscribe to the public folders. # subscriptions = yes #} !include_try /etc/dovecot/iredmail/*.conf ################################## many thanks rajesh

2 1

dovecot error
by Rajesh M 10 Dec '21

10 Dec '21

1 0

RE: virtual mailbox domains??
by postfix＠aecperformance.com 09 Dec '21

09 Dec '21

Thanks *so much* for all your help. Another complete rebuild and I think I’ve finally got it. I was able to log into mail.sizzelicks.com for smoker1(a)sizzelicks.com <mailto:smoker1@sizzelicks.com> this time with no trouble. I sent an email to smoker1(a)sizzelicks.com <mailto:smoker1@sizzelicks.com> from a gmail account and was able to retrieve it in Thunderbird. I replied to the gmail email and in gmail.com I got the response. Now I can add email accounts to the database for any of our domains and they work! I've added responses below. -----Original Message----- From: owner-postfix-users(a)postfix.org <owner-postfix-users(a)postfix.org> On Behalf Of raf Sent: Thursday, December 9, 2021 1:07 AM To: postfix-users(a)postfix.org Subject: Re: virtual mailbox domains?? On Tue, Dec 07, 2021 at 10:25:44AM -0500, <mailto:postfix@aecperformance.com> postfix(a)aecperformance.com wrote: > Sorry I sent this from the wrong email address. > > VPS Ubuntu 20.04 postfix 3.4.13 and dovecot 2.3.7.2 > > I'm making progress but still not there. > > Any help would be greatly appreciated. > > I'm getting the errors: > > warning: SASL: Connect to private/auth failed: Connection refused > > fatal: no SASL authentication mechanisms > > > > I have a param in main.cf: smtpd_sasl_path = private/auth > > I do not have a folder /etc/postfix/private/auth > > I do have a folder /etc/postfix/auth but nothing is in it. > > How can I fix this error? The reference to private/auth is referring to dovecot's authentication socket under postfix's chroot directory. It's in /var/spool/postfix/private/auth, not /etc/postfix. You have set that up in dovecot's config: service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } My version of that looks like: service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } So it looks like that should be OK. Does /var/spool/postfix/private/auth exist? Mine has root as owner/group. Yours should have postfix as owner/group. But that shouldn't matter as long as the mode is 0666. I must of changed the mode to 0660 but per your suggestion I changed it to 0666. Thanks. Yes it does exist. ls -l /var/spool/postfix/private/auth srw-rw---- 1 postfix postfix 0 Dec 8 21:50 /var/spool/postfix/private/auth If not, check dovecot's log messages for problems with it. But I don't know what to look for. The dovecot mailing list folks might be more useful for that. It should exist and be used by dovecot. If you have lsof installed, you can check that: > sudo lsof /var/spool/postfix/private/auth COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME dovecot 17341 root 53u unix 0xffff8e43c69f7400 0t0 16873340 /var/spool/postfix/private/auth type=STREAM auth 1521507 dovecot 13u unix 0xffff8e43c69f7400 0t0 16873340 /var/spool/postfix/private/auth type=STREAM auth 1521507 dovecot 21u unix 0xffff8e43c417c800 0t0 69451443 /var/spool/postfix/private/auth type=STREAM auth 1521507 dovecot 22u unix 0xffff8e43c9fc2400 0t0 69453124 /var/spool/postfix/private/auth type=STREAM sudo lsof /var/spool/postfix/private/auth COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME dovecot 4550 root 58u unix 0x0000000000000000 0t0 1305802532 /var/spool/postfix/private/auth type=STREAM Something else that might or might not be a (different) problem is that the TLS certificate at mail.sizzlelicks.com doesn't certify the domain mail.sizzlelicks.com. Its list of domains contains sizzelicks.com and <http://www.sizzelicks.com> www.sizzelicks.com but not mail.sizzelicks.com. That might cause problems with Thunderbird trying to connect for IMAPS. I think you reported such an error message earlier. So you might want to add the mail.sizzelicks.com domain to that certificate. But that's not related to the failure to connect to the dovecot auth socket. You are correct and I sure wish I saw *this* a week ago😊. I did a rebuild due to lots of trouble trying to add the certs. Now I’ve got it all back up with the certificates for all of the mail.mydomain.com MX records. THANK YOU cheers, raf > -----Original Message----- > From: <mailto:owner-postfix-users@postfix.org> owner-postfix-users(a)postfix.org > < <mailto:owner-postfix-users@postfix.org> mailto:owner-postfix-users@postfix.org> > <owner-postfix-users(a)postfix.org > < <mailto:owner-postfix-users@postfix.org> mailto:owner-postfix-users@postfix.org> > On Behalf Of Wietse Venema > Sent: Monday, December 6, 2021 11:04 AM > To: Postfix users <postfix-users(a)postfix.org > < <mailto:postfix-users@postfix.org> mailto:postfix-users@postfix.org> > > Subject: Re: virtual mailbox domains?? > > > > < <mailto:postfix@aecperformance.com> mailto:postfix@aecperformance.com> <mailto:postfix@aecperformance.com> postfix(a)aecperformance.com: > > > Command: sudo postfix status > > > postfix/postfix-script: the Postfix mail system is running: PID: > > 38284 > > > > Good. > > > > > I attempted to send an email to < <mailto:smoker1@sizzelicks.com> mailto:smoker1@sizzelicks.com> > <mailto:smoker1@sizzelicks.com> smoker1(a)sizzelicks.com > > > < < <mailto:smoker1@sizzelicks.com> mailto:smoker1@sizzelicks.com> <mailto:smoker1@sizzelicks.com> mailto:smoker1@sizzelicks.com> . > > It > bounced. > > > > What is the Postfix logging for this? Be sure to include more than > only the delivery error (i.e. logging from pickup or smtpd; cleanup; qmgr; ...). > > > > This is the first problem that you need to fix. > > > > > In the log I see a few attempts to connect from spammers. I do not > > see > > > my laptop IP or anything at all about what I did. > > > > That is the second problem to fix. I suspect a firewalling or routing > problem. > > > > Wietse >

1 0

Force clients to use pgp encryption when sending email?
by Austin Witmer 09 Dec '21

09 Dec '21

Hello all! I am looking for a way to force imap clients to encrypt their messages with the public keys of the recipients before sending them. Would a post-login script in dovecot work for something like this? I am using postfix and dovecot on my mail server. Basically I want the server to check if the message being sent is encrypted with OpenGPG and either proceed or reject the message based on that criteria. If the message is rejected, the user could then encrypt the outgoing email message with the recipient public key and try again. Does anybody have a suggestion on how to implement something like this? Would there be a way that the the client software (thunderbird) could show an alert asking the user to encrypt the message and then attempt to resend the message? I realize that you can tell a client (like thunderbird) to automatically encrypt outgoing messages with pgp but I would like to have some way to enforce that policy at the server level before the email is sent. I want to have all messages end-to-end encrypted, hence my desire for functionality like this. Any suggestions are welcome. Thanks in advance for your help!

3 4

Mailbox connection fails: Connection closed (No commands sent) Help please
by postfix＠aecperformance.com 09 Dec '21

09 Dec '21

I would greatly appreciate help with this. VPS ubuntu 20.04 postfix 3.4.13 dovecot 2.3.7.2 I'm trying to set up postfix with dovecot for virtual mailboxes using mysql I have a database mailserver with tables virtual_domains, virtual_users & virtual_aliases Using postmap I've tested all connections and gotten correct responses (1, 1, smoker1(a)sizzelicks.com <mailto:smoker1@sizzelicks.com> ) I have a domain: sizzelicks.com and an email address smoker1(a)sizzelicks.com <mailto:smoker1@sizzelicks.com> The password for the user is encrypted with sha512-CRYPT My VPS IP is: 194.163.45.150 MX test from: https://mxtoolbox.com/SuperTool.aspx?action=mx%3asizzelicks.com&run=toolpage I set up a mailbox for smoker1(a)sizzelicks.com <mailto:smoker1@sizzelicks.com> in Thunderbird: IMAP and SMTP server: mail.sizzelicks.com IMAP port: 993 SMTP port: 587 IMAP connection security: SSL/TLS SMTP connection security: STARTTLS When I try to connect to the mailbox Thunderbird returns this: server mail.sizzelicks.com has disconnected. The server may have gone down or there may be a network problem. mail.log Dec 7 21:16:02 softlinksys dovecot: imap-login: Login: user=, method=PLAIN, rip=67.8.3.170, lip=194.163.45.150, mpid=63115, TLS, session= Dec 7 21:16:02 softlinksys dovecot: imap(smoker1(a)sizzelicks.com)<63115>: Connection closed (No commands sent) in=0 out=388 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Dec 7 21:16:04 softlinksys dovecot: imap-login: Login: user=, method=PLAIN, rip=67.8.3.170, lip=194.163.45.150, mpid=63117, TLS, session= Dec 7 21:16:04 softlinksys dovecot: imap(smoker1(a)sizzelicks.com)<63117>: Connection closed (No commands sent) in=0 out=388 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Dovecot -n # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0 x86_64 Ubuntu 20.04.3 LTS ext4 # Hostname: softlinksys.com auth_mechanisms = plain login mail_location = maildir:/var/mail/vhosts/%d/%n mail_privileged_group = mail 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 } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } postmaster_address = postmaster at aecperformance.com protocols = imap pop3 lmtp service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { port = 995 ssl = yes } } ssl = required ssl_cert = </etc/letsencrypt/live/aecperformance.com/fullchain.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } userdb { args = uid=vmail gid=vmail home=/var/mail/vhosts/%d/%n driver = static } Kristy Atkins ViviData SaaS

5 8

Unexpected variable expand behavior
by Евгений Бахтин 09 Dec '21

09 Dec '21

2 1

No source packages in APT repo?
by Shawn Heisey 08 Dec '21

08 Dec '21

I added a deb-src entry to my APT config matching the deb entry: deb https://repo.dovecot.org/ce-2.3-latest/ubuntu/focal focal main deb-src https://repo.dovecot.org/ce-2.3-latest/ubuntu/focal focal main When this is there, I see a warning when running "apt update". W: Skipping acquire of configured file 'main/source/Sources' as repository 'https://repo.dovecot.org/ce-2.3-latest/ubuntu/focal focal InRelease' does not seem to provide it (sources.list entry misspelt?) Were source packages excluded deliberately? The github repo for dovecot does not have a "debian" directory, which is the other route that would allow me to build packages. Thanks, Shawn

3 6

#define DUPLICATE_LOCK_MAX_LOCKS 100
by Vladimir Gulas 08 Dec '21

08 Dec '21

Hello, dovecot --version 2.3.17 (e2aa53df5b) debug log: Debug: duplicate db: transaction: Too many duplicate IDs locked Debug: duplicate db: transaction: Check ID: too many IDs locked - .sieve with 100+ redirects ( 201 actually ) #define DUPLICATE_LOCK_MAX_LOCKS 100 It's not corresponding with sieve_max_redirects = 310 or sieve_max_actions = 320 On dovecot 2.3.16 version DUPLICATE_LOCK_MAX_LOCKS is not implemented and redirects work correctly. Thank you. Vladimir Gulas.

1 0

app-specific passwords for dovecot
by mj 08 Dec '21

08 Dec '21

Hi all, I have read these documents on the subject of app-specific passwords: > https://www.dgsiegel.net/news/2013_05_21-application_specific_passwords_for… > https://www.happyassassin.net/posts/2014/08/26/adding-application-specific-… But since both articles are rather old, I'd like to ask if there are other/new ways of implementing app-specific passwords for dovecot/imap and postfix/smtp. Also perhaps (web?) GUI's exist, to make it possible for the users themselves to generate/edit those passwords..? Thanks for your suggestions! MJ

1 0

vsz_limit
by Daniel Miller 07 Dec '21

07 Dec '21

I just noticed, that when checking "doveconf -a" - all vsz_limit settings that are not explicitly given have a value of: 18446744073709551615 B I have this on two servers, one with an implicit default_vsz_limit=256M, the other with an explicit default_vsz_limit=2G. Is this correct? -- Daniel

1 0

Replicator bug report
by Daniel Miller 07 Dec '21

07 Dec '21

I've run dovecot-sysreport -o <core> and generated a file - but it's a few gigs in size. Am I generating the core dump incorrectly? Should I do something different? -- Daniel

3 6

Pigeonhole v0.5.17.1 Released
by Aki Tuomi 07 Dec '21

07 Dec '21

We are happy to announce 0.5.17.1 patch release of Pigeonhole. This contains some fixes for issues found after 0.5.17 release. https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.17.1… https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.17.1… Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy --- - managesieve: Dovecot failed to start if ssl_ca was too large. - lib-sieve-tool: Binaries failed to run if ssl_ca was too large.

1 0

LDAP and user duplicated with replication
by Claudio Corvino 07 Dec '21

07 Dec '21

Hi, I have two IMAP/LMTP Dovecot server in replica (version 2.3.4.1), I use LDAP/AD for /userdb, /replica is working. When I do a search like: /doveadm replicator status '*'/ I receive user duplicated, with and without the domain part, for example: /test/ /test(a)domain.com/ but they are the same user; this lead the replicator doing twice the work of replication. I think this is related to //etc/dovecot/dovecot-ldap.conf/ that is configured in this way: /hosts = xxx/ /base = dc=xxx,dc=xxx ldap_version=3 auth_bind = yes dn = cn=xxx,cn=Users,dc=xxx,dc=xxx dnpass = xxx scope = subtree user_attrs = sAMAccountName=home=/mnt/mail-storage-lv0007/%$,=uid=501,=gid=501 pass_attrs = sAMAccountName=user user_filter = (&(objectclass=person)(samaccountname=%n)) pass_filter= (&(objectclass=person)(samaccountname=%n)) iterate_attrs = sAMAccountName=user # With following filter we exclude all objects without an email address, all computers and all inactive accounts / /iterate_filter = (&(objectCategory=person)(mail=*)(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2))) / I think that *iterate_attrs* and *iterate_filter* should be fixed, but I don't know how/./ Please could someone give me any hints? Thanks/ / Regards/ /

2 3

public folders, ACLs
by Stefan G. Weichinger 06 Dec '21

06 Dec '21

greetings ... I got the following request from a customer where we run dovecot-2.3.15 on a debian server: They have a public folder with all their project-related subfolders inside: namespace { location = maildir:/home/vmail/oeffentlich prefix = Oeffentlich/ separator = / subscriptions = yes type = public } So far we don't have the mail_plugin ACL enabled. They want to be able to create projectfolders that aren't move/delete/rename-able by the users, only by some admins. But the users should be allowed to move mails between different projectfolders etc As far as I understand we can do that with Dovecot ACLs (although I am still figuring out how to properly design them ...). My questions: * if I enable the mail_plugin for ACLs, does that in any way change the behavior of existing mailboxes? afai understand: no. Only if ACL-lists exist in the various mailboxes, these get applied, right? I don't want to break things, and I want to avoid additional complexity for the non-public user mailboxes etc Maybe I can enable the plugin only for that public namespace? * maybe someone has a link to a similar setup? thanks in advance, Stefan

2 8

Errors after upgrade to v2.3.17
by Aurel Mihai 06 Dec '21

06 Dec '21

Hello, after upgrade to version 2.3.17, we enconter a lot of errors, such as: Dec 2 13:41:22 mail5 dovecot: lmtp(user@domain)<41944><EFw6IuKwqGHYowAAF7/xgA>: Error: lmtp-server: conn unix:pid=40487,uid=107 [22]: rcpt user@domain: stat(/home/virtual0/domain/user/.dovecot.lda-dupes/tmp) failed: Not a directory Here is my config: #dovecot -n # 2.3.17 (e2aa53df5b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.17 (054dddfa) # OS: Linux 4.19.0-18-amd64 x86_64 Debian 10.11 nfs # Hostname: auth_cache_verify_password_with_worker = yes auth_failure_delay = 5 secs auth_mechanisms = plain login auth_verbose = yes auth_worker_max_count = 256 default_client_limit = 10000 default_process_limit = 10000 default_vsz_limit = 1 G dict { lastlogin = mysql:/etc/dovecot/mysql/dovecot-dict-lastlogin.conf quotadict = mysql:/etc/dovecot/mysql/dovecot-dict-quota.conf } disable_plaintext_auth = no first_valid_uid = 100 imap_hibernate_timeout = 5 secs imap_idle_notify_interval = 3 mins log_timestamp = "%Y-%m-%d %H:%M:%S " login_log_format_elements = user=<%u> method=%m rip=%r lip=%l pid=%p %c login_trusted_networks = xxxx mail_fsync = always mail_location = maildir:/home/virtual0/%d/%u mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = zlib quota mail_log notify mail_privileged_group = mail maildir_stat_dirs = yes 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 ihave metric imap_command { filter = event=imap_command_finished AND tagged_reply_state=OK group_by = cmd_name } metric imap_select_no { filter = event=imap_command_finished AND cmd_name=SELECT AND tagged_reply_state=NO } metric imap_select_no_notfound { filter = event=imap_command_finished AND cmd_name=SELECT AND tagged_reply="NO*Mailbox doesn't exist:*" } metric storage_http_gets { filter = event=http_request_finished AND category=storage AND method=get } mmap_disable = yes namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Trash { auto = subscribe autoexpunge = 60 days special_use = \Trash } mailbox virtual/All { special_use = \All } prefix = } passdb { args = /etc/dovecot/mysql/dovecot-sql.conf driver = sql } plugin { last_login_dict = proxy::lastlogin last_login_key = # hidden, use -P to show it mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size quota = dict:user::proxy::quotadict quota_rule2 = Trash:ignore quota_rule3 = Spam:ignore quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 The email account that you tried to reach is over quota quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = ~/.dovecot.sieve sieve_before = /etc/dovecot/sieve/default.sieve sieve_dir = ~/sieve trash = /etc/dovecot/dovecot-trash.conf zlib_save = gz zlib_save_level = 6 } protocols = imap sieve pop3 lmtp service anvil { client_limit = 50000 unix_listener anvil-auth-penalty { mode = 00 } } service auth { client_limit = 50000 unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { group = mail mode = 0660 user = vmail } user = root vsz_limit = 1 G } service dict { unix_listener dict { mode = 0660 user = vmail } } service imap-hibernate { unix_listener imap-hibernate { group = $default_internal_group mode = 0660 } } service imap-login { inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 993 } process_min_avail = 16 service_count = 1 } service imap { extra_groups = $default_internal_group process_min_avail = 16 unix_listener imap-master { user = $default_internal_user } vsz_limit = 2 G } service lmtp { process_min_avail = 16 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } vsz_limit = 1 G } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 16 service_count = 1 } service managesieve { vsz_limit = 1 G } service pop3-login { inet_listener pop3 { address = * port = 110 } inet_listener pop3s { address = * port = 995 } process_min_avail = 16 service_count = 1 } service pop3 { process_min_avail = 16 vsz_limit = 1 G } service quota-status { executable = /usr/lib/dovecot/quota-status -p postfix process_min_avail = 16 unix_listener /var/spool/postfix/private/quota-status { group = postfix mode = 0666 user = postfix } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { mode = 0660 user = vmail } user = vmail } service stats { unix_listener stats-reader { mode = 0660 user = vmail } unix_listener stats-writer { mode = 0666 user = vmail } } ssl_cert = </etc/dovecot/ssl/domain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1 userdb { args = /etc/dovecot/mysql/dovecot-sql.conf driver = sql } protocol imap { imap_max_line_length = 64 k mail_max_userip_connections = 16 mail_plugins = zlib quota mail_log notify trash imap_quota last_login } protocol pop3 { mail_max_userip_connections = 10 mail_plugins = zlib quota mail_log notify last_login pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_fast_size_lookups = yes pop3_no_flag_updates = yes pop3_uidl_format = %08Xu%08Xv } protocol sieve { mail_max_userip_connections = 10 managesieve_max_compile_errors = 5 } protocol lda { auth_socket_path = /var/run/dovecot/auth-master mail_plugins = zlib quota mail_log notify sieve sendmail_path = /usr/lib/sendmail syslog_facility = mail } protocol lmtp { mail_plugins = zlib quota mail_log notify sieve syslog_facility = mail } Any help please? Aurel

3 4

Re[5]: Replication weirdness
by Daniel Miller - CLOUD 05 Dec '21

05 Dec '21

Another update. I dug deeper into the mailboxes - and found the "subscriptions" and actual mailboxes weren't correct in all cases. I guess when I shifted to the explicit INBOX/ namespace not all the existing boxes migrated correctly. So...after manually correcting all the "subscription" files, and manually moving the duplicated "Archives" folders to the correct locations nearly all the errors have gone. I wish I'd gotten more inforrmative error messages, and processes certainly shouldn't have crashed, but since I obviously created the problem due to manually poking things and improper configuration I guess I can't complain too much. I still have problems using the "-N" flag for syncing - but things seem to be working with the multiple explicit "-n" namespaces. I do still have the locking error appearing during long-running syncs - I don't see why Dovecot doesn't know that it's already syncing a given user before trying to start a second process. Probably something else I setup wrong but I don't know what. -- Daniel

1 0

Re[4]: Replication weirdness
by Daniel Miller 04 Dec '21

04 Dec '21

And some more messages... Dec 3 15:10:58 bubba dovecot: doveadm(obfuscated)<1901><UGoeMgGkqmFtBwAAnbWsyw>: Error: Mailbox Sent sync: mailbox_rename failed: Can't rename mailbox while it has aliases Dec 3 15:10:58 bubba dovecot: doveadm(obfuscated)<1900><YVHxLACkqmFsBwAAnbWsyw>: Error: Duplicate mailbox GUID f4338038839caa613a1a0500b88bfabe for mailboxes INBOX/Sent Messages and INBOX/Sent - giving a new GUID bcf4f82702a4aa616c0700009db5accb to INBOX/Sent -- Daniel ------ Original Message ------ From: "Daniel Miller" <dmiller(a)amfes.com> To: "Daniel Miller" <dmiller(a)amfes.com>; dovecot(a)dovecot.org Sent: 12/3/2021 3:13:55 PM Subject: Re[3]: Replication weirdness >And... > >The user who has both a "Sent" and a "Sent Messages" now has: > >drwx------ 3 vmail mail 24 Dec 3 09:56 Sent >lrwxrwxrwx 1 vmail mail 4 Nov 30 17:51 'Sent Messages' -> Sent >drwx------ 3 vmail mail 24 Dec 3 15:10 'Sent Messages-temp-1' >drwx------ 3 vmail mail 24 Dec 3 15:10 'Sent >Messages-temp-fc30bd0a3a9aaa61c1180500b88bfabe' > >and I got the following errors: > >Dec 3 15:10:46 cloud1 dovecot: >doveadm(obfuscated)<336247><EMEQBvWjqmF3IQUAuIv6vg>: Error: Duplicate >mailbox GUID 6aae8c39f3a3aa615a0700009db5accb for mailboxes Sent and >Sent Messages-temp-1 - giving a new GUID >63481f29f6a3aa6177210500b88bfabe to Sent >Dec 3 15:10:50 cloud1 dovecot: >doveadm(obfuscated)<336245><HrHeOPOjqmF1IQUAuIv6vg>: Panic: file >dsync-brain-mailbox.c: line 851 (dsync_brain_slave_recv_mailbox): >assertion failed: (memcmp(dsync_box->mailbox_guid, >local_dsync_box.mailbox_guid, sizeof(dsync_box->mailbox_guid)) == 0) >Dec 3 15:10:50 cloud1 dovecot: >doveadm(obfuscated)<336245><HrHeOPOjqmF1IQUAuIv6vg>: Error: Raw >backtrace: #0 fatal_handler_real[0x7fde7fd20060] -> #1 >i_internal_fatal_handler[0x7fde7fd20190] -> #2 i_panic[0x7fde7fc731ff] >-> #3 dsync_brain_slave_recv_mailbox[0x55dde7b22900] -> #4 >dsync_brain_run[0x55dde7b20380] -> #5 >dsync_brain_run_io[0x55dde7b20b50] -> #6 >dsync_ibc_stream_input[0x55dde7b329c0] -> #7 >io_loop_call_io[0x7fde7fd36500] -> #8 >io_loop_handler_run_internal[0x7fde7fd37ac0] -> #9 >io_loop_handler_run[0x7fde7fd365c0] -> #10 io_loop_run[0x7fde7fd36740] >-> #11 cmd_dsync_server_run[0x55dde7b04f60] -> #12 >doveadm_mail_next_user[0x55dde7b06850] -> #13 >doveadm_cmd_ver2_to_mail_cmd_wrapper[0x55dde7b077e0] -> #14 >doveadm_cmd_run_ver2[0x55dde7b17f00] -> #15 >client_connection_tcp_input[0x55dde7b1c6b0] -> #16 >io_loop_call_io[0x7fde7fd36500] -> #17 >io_loop_handler_run_internal[0x7fde7fd37ac0] -> #18 >io_loop_handler_run[0x7fde7fd365c0] -> #19 io_loop_run[0x7fde7fd36740] >-> #20 master_service_run[0x7fde7fca87d0] -> #21 main[0x55dde7af7770] >-> #22 __libc_start_main[0x7fde7f8f9fc0] -> #23 _start[0x55dde7af78d0] >Dec 3 15:10:50 cloud1 dovecot: >doveadm(obfuscated)<336245><HrHeOPOjqmF1IQUAuIv6vg>: Fatal: master: >service(doveadm): child 336245 killed with signal 6 (core dumped) >Dec 3 15:10:52 cloud1 dovecot: >doveadm(obfuscated)<336253><2VTpM/ujqmF9IQUAuIv6vg>: Error: Duplicate >mailbox GUID 63481f29f6a3aa6177210500b88bfabe for mailboxes INBOX/Sent >and INBOX/Sent Messages-temp-1 - giving a new GUID >cba35507fca3aa617d210500b88bfabe to INBOX/Sent >Dec 3 15:10:58 cloud1 dovecot: >doveadm(obfuscated)<336258><ykbQAAGkqmGCIQUAuIv6vg>: Error: Duplicate >mailbox GUID dc3b4434fba3aa61660700009db5accb for mailboxes Sent and >Sent Messages-temp-1 - giving a new GUID >60ad190102a4aa6182210500b88bfabe to Sent > >-- >Daniel > >------ Original Message ------ >From: "Daniel Miller" <dmiller(a)amfes.com> >To: "Daniel Miller" <dmiller(a)amfes.com>; dovecot(a)dovecot.org >Sent: 12/3/2021 2:42:12 PM >Subject: Re[2]: Replication weirdness > >>And...one more. >> >>I'm now seeing (again) messages like: >> >>Dec 3 14:29:14 cloud1 dovecot: >>doveadm(obfuscated)<334017><e3FHNjmaqmHBGAUAuIv6vg>: Error: Duplicate >>mailbox GUID bcb9ca36ae36aa617f0a00009db5accb for mailboxes INBOX/Sent >>Messages and INBOX/Sent - giving a new GUID >>fc30bd0a3a9aaa61c1180500b88bfabe to INBOX/Sent >>Dec 3 14:38:59 cloud1 dovecot: >>doveadm(obfuscated)<334394><an5KIoOcqmE6GgUAuIv6vg>: Error: Duplicate >>mailbox GUID fc30bd0a3a9aaa61c1180500b88bfabe for mailboxes INBOX/Sent >>Messages and INBOX/Sent - giving a new GUID >>f4338038839caa613a1a0500b88bfabe to INBOX/Sent >> >>Having one message for the initial sync I suppose is reasonable. A >>second...maybe? But I'm getting nervous I'm about to start seeing the >>endless temp folders again. >>-- >>Daniel >> >>------ Original Message ------ >>From: "Daniel Miller" <dmiller(a)amfes.com> >>To: "Daniel Miller" <dmiller(a)amfes.com>; dovecot(a)dovecot.org >>Sent: 12/3/2021 2:39:25 PM >>Subject: Re: Replication weirdness >> >>>Another item. >>> >>>Again, it may be a 2.3.13 issue and I'm now on 2.3.17. But...I had >>>problem when using the "-N" parameter for dsync. So - I just have >>>(had): >>> >>>replication_dsync_parameters = -d -l 30 -U -x INBOX/virtual -x >>>INBOX/shared >>> >>>Now that things are working - I wanted to have my other namespaces >>>sync as well. So I went to: >>> >>>replication_dsync_parameters = -d -l 30 -U -n INBOX -n INBOX/Archives >>>-n INBOX/Lists -x INBOX/virtual -x INBOX/shared >>> >>>This appears to be working (the sync is just starting)...but I'm >>>seeing lock errors in the logs such as: >>>Dec 3 14:34:24 bubba dovecot: >>>doveadm(dmiller(a)amfes.com)<31785><TV+0LlGbqmEpfAAAnbWsyw>: Error: >>>Couldn't lock /var/mail/amfes.com/dmiller/.dovecot-sync.lock: >>>fcntl(/var/mail/amfes.com/dmiller/.dovecot-sync.lock, write-lock, >>>F_SETLKW) locking failed: Timed out after 30 seconds (WRITE lock held >>>by pid 31373) >>> >>>Checking the pid in question I see it's actively syncing a folder in >>>my mailbox. So I'm guessing, purely guessing, that by having multiple >>>namespaces explicitly directed to sync Dovecot is trying to start a >>>sync process for each of those namespaces - but all of them share a >>>common lock and therefore only one operation is allowed at a time. >>> >>>Am I correct, and whether or not I am - how can I correct these >>>errors? Do I dare try going back to just "-N"? >>> >>>-- >>>Daniel >>> >>>------ Original Message ------ >>>From: "Daniel Miller" <dmiller(a)amfes.com> >>>To: dovecot(a)dovecot.org >>>Sent: 12/3/2021 2:16:28 PM >>>Subject: Replication weirdness >>> >>>>First, I have to say this. After configuring everything correctly - >>>>and that means *everything* correctly - Dovecot replication Just >>>>Works. I'm not sure how (yes I do - Timo & Co. Magic) - but it does. >>>>Real-time new sync is near instantaneous. >>>> >>>>Now the problem. Or the background for the problem. My primary >>>>server uses sdbox for primary storage, mdbox for archival storage, >>>>and fts-solr. I spun up a second server, using sdbox, mdbox, and >>>>fts-flatcurve. My namespaces are as defined below. As best I can >>>>tell (based on diff comparing two 'doveconf -n' outputs) my >>>>namespaces are the same on both servers. >>>> >>>>namespace archives { >>>> list = children >>>> location = mdbox:/var/mail/%d/%n/Archives/mdbox >>>> mailbox Unsorted { >>>> auto = no >>>> special_use = \Archive >>>> } >>>> prefix = INBOX/Archives/ >>>> separator = / >>>> subscriptions = no >>>> type = private >>>>} >>>>namespace inbox { >>>> alias_for = >>>> hidden = no >>>> inbox = yes >>>> list = yes >>>> location = >>>> mailbox "Deleted Messages" { >>>> auto = no >>>> autoexpunge = 30 days >>>> special_use = \Trash >>>> } >>>> mailbox Drafts { >>>> auto = subscribe >>>> special_use = \Drafts >>>> } >>>> mailbox Sent { >>>> auto = subscribe >>>> special_use = \Sent >>>> } >>>> mailbox Trash { >>>> auto = subscribe >>>> autoexpunge = 30 days >>>> special_use = \Trash >>>> } >>>> prefix = INBOX/ >>>> separator = / >>>> subscriptions = no >>>> type = private >>>>} >>>>namespace lists { >>>> list = children >>>> location = mdbox:/var/mail/%d/%n/Lists/mdbox >>>> prefix = INBOX/Lists/ >>>> separator = / >>>> subscriptions = no >>>> type = private >>>>} >>>>namespace subscriptions { >>>> hidden = yes >>>> list = no >>>> location = >>>> prefix = >>>> separator = / >>>> subscriptions = yes >>>> type = private >>>>} >>>>namespace usershares { >>>> list = yes >>>> location = sdbox:/var/mail/%%d/%%n/sdbox:NO-NOSELECT >>>> prefix = INBOX/shared/%%d/%%n/ >>>> separator = / >>>> subscriptions = no >>>> type = shared >>>>} >>>>namespace virtual { >>>> list = children >>>> location = virtual:/var/mail/%d/%n/virtual >>>> mailbox Flagged { >>>> comment = All my flagged messages >>>> special_use = \Flagged >>>> } >>>> prefix = INBOX/virtual/ >>>> separator = / >>>> subscriptions = no >>>>} >>>> >>>>I also have: >>>>plugin { >>>> mailbox_alias_new = Sent Messages >>>> mailbox_alias_new2 = Sent Items >>>> mailbox_alias_new3 = Deleted Messages >>>> mailbox_alias_old = Sent >>>> mailbox_alias_old2 = Sent >>>> mailbox_alias_old3 = Trash >>>>} >>>> >>>>This setup worked fine with my single server. Then I enabled >>>>replication - just on the primary. Dsync went to work (it seemed to >>>>take forever for the initial sync but that's what happens with large >>>>mailboxes and slow internet connections). >>>> >>>>The problem came up with certain subfolders. And I believe it only >>>>happens with subfolders that have spaces in their names. I had two >>>>user's mailboxes (under Sent), one of which had a "Sent Messages" >>>>symlink alias for "Sent", that started generating tens or hundreds >>>>of duplicates during sync. Fortunately those subfolders only had a >>>>few mails in them. But I had trees looking like: >>>> >>>>[...] (below is under /var/mail/domain/user/sdbox/mailboxes/Sent/) >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-1-temp-f80b1a00ce9aa961a86-temp-2 >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-1-temp-f80b1a00ce9aa961a86-temp-3 >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-023fa4271c9ca9611ade0400b88bfabe >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-023fa4271c9ca9611ad-temp-1 >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-1 >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-2 >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-2-temp-1-temp-1 >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-3 >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-4 >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-5 >>>>Proposal >>>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-e2aa0f35c99ba961356500009db5accb >>>>[...] >>>> >>>>I kept stopping, cleaning up the folders, and re-starting - and they >>>>kept regenerating. I tried renaming the folders to eliminate the >>>>spaces and I think that helped in one case - for the others I just >>>>moved the folders outside of the mail area completely to let the >>>>sync finish. >>>> >>>>Now that it's been stable for a day or two - I enabled sync in the >>>>other direction. And after setting *all* the required parameters >>>>instead of just most of them...it's working. But...I'm nervous about >>>>moving the problem folders back over. I will say, if it makes any >>>>difference, my primary server *was* running version 2.3.13 and I >>>>just updated it to 2.3.17. The remote is also 2.3.17. >>>> >>>>-- >>>>Daniel

1 0

Re[3]: Replication weirdness
by Daniel Miller 04 Dec '21

04 Dec '21

And... The user who has both a "Sent" and a "Sent Messages" now has: drwx------ 3 vmail mail 24 Dec 3 09:56 Sent lrwxrwxrwx 1 vmail mail 4 Nov 30 17:51 'Sent Messages' -> Sent drwx------ 3 vmail mail 24 Dec 3 15:10 'Sent Messages-temp-1' drwx------ 3 vmail mail 24 Dec 3 15:10 'Sent Messages-temp-fc30bd0a3a9aaa61c1180500b88bfabe' and I got the following errors: Dec 3 15:10:46 cloud1 dovecot: doveadm(obfuscated)<336247><EMEQBvWjqmF3IQUAuIv6vg>: Error: Duplicate mailbox GUID 6aae8c39f3a3aa615a0700009db5accb for mailboxes Sent and Sent Messages-temp-1 - giving a new GUID 63481f29f6a3aa6177210500b88bfabe to Sent Dec 3 15:10:50 cloud1 dovecot: doveadm(obfuscated)<336245><HrHeOPOjqmF1IQUAuIv6vg>: Panic: file dsync-brain-mailbox.c: line 851 (dsync_brain_slave_recv_mailbox): assertion failed: (memcmp(dsync_box->mailbox_guid, local_dsync_box.mailbox_guid, sizeof(dsync_box->mailbox_guid)) == 0) Dec 3 15:10:50 cloud1 dovecot: doveadm(obfuscated)<336245><HrHeOPOjqmF1IQUAuIv6vg>: Error: Raw backtrace: #0 fatal_handler_real[0x7fde7fd20060] -> #1 i_internal_fatal_handler[0x7fde7fd20190] -> #2 i_panic[0x7fde7fc731ff] -> #3 dsync_brain_slave_recv_mailbox[0x55dde7b22900] -> #4 dsync_brain_run[0x55dde7b20380] -> #5 dsync_brain_run_io[0x55dde7b20b50] -> #6 dsync_ibc_stream_input[0x55dde7b329c0] -> #7 io_loop_call_io[0x7fde7fd36500] -> #8 io_loop_handler_run_internal[0x7fde7fd37ac0] -> #9 io_loop_handler_run[0x7fde7fd365c0] -> #10 io_loop_run[0x7fde7fd36740] -> #11 cmd_dsync_server_run[0x55dde7b04f60] -> #12 doveadm_mail_next_user[0x55dde7b06850] -> #13 doveadm_cmd_ver2_to_mail_cmd_wrapper[0x55dde7b077e0] -> #14 doveadm_cmd_run_ver2[0x55dde7b17f00] -> #15 client_connection_tcp_input[0x55dde7b1c6b0] -> #16 io_loop_call_io[0x7fde7fd36500] -> #17 io_loop_handler_run_internal[0x7fde7fd37ac0] -> #18 io_loop_handler_run[0x7fde7fd365c0] -> #19 io_loop_run[0x7fde7fd36740] -> #20 master_service_run[0x7fde7fca87d0] -> #21 main[0x55dde7af7770] -> #22 __libc_start_main[0x7fde7f8f9fc0] -> #23 _start[0x55dde7af78d0] Dec 3 15:10:50 cloud1 dovecot: doveadm(obfuscated)<336245><HrHeOPOjqmF1IQUAuIv6vg>: Fatal: master: service(doveadm): child 336245 killed with signal 6 (core dumped) Dec 3 15:10:52 cloud1 dovecot: doveadm(obfuscated)<336253><2VTpM/ujqmF9IQUAuIv6vg>: Error: Duplicate mailbox GUID 63481f29f6a3aa6177210500b88bfabe for mailboxes INBOX/Sent and INBOX/Sent Messages-temp-1 - giving a new GUID cba35507fca3aa617d210500b88bfabe to INBOX/Sent Dec 3 15:10:58 cloud1 dovecot: doveadm(obfuscated)<336258><ykbQAAGkqmGCIQUAuIv6vg>: Error: Duplicate mailbox GUID dc3b4434fba3aa61660700009db5accb for mailboxes Sent and Sent Messages-temp-1 - giving a new GUID 60ad190102a4aa6182210500b88bfabe to Sent -- Daniel ------ Original Message ------ From: "Daniel Miller" <dmiller(a)amfes.com> To: "Daniel Miller" <dmiller(a)amfes.com>; dovecot(a)dovecot.org Sent: 12/3/2021 2:42:12 PM Subject: Re[2]: Replication weirdness >And...one more. > >I'm now seeing (again) messages like: > >Dec 3 14:29:14 cloud1 dovecot: >doveadm(obfuscated)<334017><e3FHNjmaqmHBGAUAuIv6vg>: Error: Duplicate >mailbox GUID bcb9ca36ae36aa617f0a00009db5accb for mailboxes INBOX/Sent >Messages and INBOX/Sent - giving a new GUID >fc30bd0a3a9aaa61c1180500b88bfabe to INBOX/Sent >Dec 3 14:38:59 cloud1 dovecot: >doveadm(obfuscated)<334394><an5KIoOcqmE6GgUAuIv6vg>: Error: Duplicate >mailbox GUID fc30bd0a3a9aaa61c1180500b88bfabe for mailboxes INBOX/Sent >Messages and INBOX/Sent - giving a new GUID >f4338038839caa613a1a0500b88bfabe to INBOX/Sent > >Having one message for the initial sync I suppose is reasonable. A >second...maybe? But I'm getting nervous I'm about to start seeing the >endless temp folders again. >-- >Daniel > >------ Original Message ------ >From: "Daniel Miller" <dmiller(a)amfes.com> >To: "Daniel Miller" <dmiller(a)amfes.com>; dovecot(a)dovecot.org >Sent: 12/3/2021 2:39:25 PM >Subject: Re: Replication weirdness > >>Another item. >> >>Again, it may be a 2.3.13 issue and I'm now on 2.3.17. But...I had >>problem when using the "-N" parameter for dsync. So - I just have >>(had): >> >>replication_dsync_parameters = -d -l 30 -U -x INBOX/virtual -x >>INBOX/shared >> >>Now that things are working - I wanted to have my other namespaces >>sync as well. So I went to: >> >>replication_dsync_parameters = -d -l 30 -U -n INBOX -n INBOX/Archives >>-n INBOX/Lists -x INBOX/virtual -x INBOX/shared >> >>This appears to be working (the sync is just starting)...but I'm >>seeing lock errors in the logs such as: >>Dec 3 14:34:24 bubba dovecot: >>doveadm(dmiller(a)amfes.com)<31785><TV+0LlGbqmEpfAAAnbWsyw>: Error: >>Couldn't lock /var/mail/amfes.com/dmiller/.dovecot-sync.lock: >>fcntl(/var/mail/amfes.com/dmiller/.dovecot-sync.lock, write-lock, >>F_SETLKW) locking failed: Timed out after 30 seconds (WRITE lock held >>by pid 31373) >> >>Checking the pid in question I see it's actively syncing a folder in >>my mailbox. So I'm guessing, purely guessing, that by having multiple >>namespaces explicitly directed to sync Dovecot is trying to start a >>sync process for each of those namespaces - but all of them share a >>common lock and therefore only one operation is allowed at a time. >> >>Am I correct, and whether or not I am - how can I correct these >>errors? Do I dare try going back to just "-N"? >> >>-- >>Daniel >> >>------ Original Message ------ >>From: "Daniel Miller" <dmiller(a)amfes.com> >>To: dovecot(a)dovecot.org >>Sent: 12/3/2021 2:16:28 PM >>Subject: Replication weirdness >> >>>First, I have to say this. After configuring everything correctly - >>>and that means *everything* correctly - Dovecot replication Just >>>Works. I'm not sure how (yes I do - Timo & Co. Magic) - but it does. >>>Real-time new sync is near instantaneous. >>> >>>Now the problem. Or the background for the problem. My primary server >>>uses sdbox for primary storage, mdbox for archival storage, and >>>fts-solr. I spun up a second server, using sdbox, mdbox, and >>>fts-flatcurve. My namespaces are as defined below. As best I can tell >>>(based on diff comparing two 'doveconf -n' outputs) my namespaces are >>>the same on both servers. >>> >>>namespace archives { >>> list = children >>> location = mdbox:/var/mail/%d/%n/Archives/mdbox >>> mailbox Unsorted { >>> auto = no >>> special_use = \Archive >>> } >>> prefix = INBOX/Archives/ >>> separator = / >>> subscriptions = no >>> type = private >>>} >>>namespace inbox { >>> alias_for = >>> hidden = no >>> inbox = yes >>> list = yes >>> location = >>> mailbox "Deleted Messages" { >>> auto = no >>> autoexpunge = 30 days >>> special_use = \Trash >>> } >>> mailbox Drafts { >>> auto = subscribe >>> special_use = \Drafts >>> } >>> mailbox Sent { >>> auto = subscribe >>> special_use = \Sent >>> } >>> mailbox Trash { >>> auto = subscribe >>> autoexpunge = 30 days >>> special_use = \Trash >>> } >>> prefix = INBOX/ >>> separator = / >>> subscriptions = no >>> type = private >>>} >>>namespace lists { >>> list = children >>> location = mdbox:/var/mail/%d/%n/Lists/mdbox >>> prefix = INBOX/Lists/ >>> separator = / >>> subscriptions = no >>> type = private >>>} >>>namespace subscriptions { >>> hidden = yes >>> list = no >>> location = >>> prefix = >>> separator = / >>> subscriptions = yes >>> type = private >>>} >>>namespace usershares { >>> list = yes >>> location = sdbox:/var/mail/%%d/%%n/sdbox:NO-NOSELECT >>> prefix = INBOX/shared/%%d/%%n/ >>> separator = / >>> subscriptions = no >>> type = shared >>>} >>>namespace virtual { >>> list = children >>> location = virtual:/var/mail/%d/%n/virtual >>> mailbox Flagged { >>> comment = All my flagged messages >>> special_use = \Flagged >>> } >>> prefix = INBOX/virtual/ >>> separator = / >>> subscriptions = no >>>} >>> >>>I also have: >>>plugin { >>> mailbox_alias_new = Sent Messages >>> mailbox_alias_new2 = Sent Items >>> mailbox_alias_new3 = Deleted Messages >>> mailbox_alias_old = Sent >>> mailbox_alias_old2 = Sent >>> mailbox_alias_old3 = Trash >>>} >>> >>>This setup worked fine with my single server. Then I enabled >>>replication - just on the primary. Dsync went to work (it seemed to >>>take forever for the initial sync but that's what happens with large >>>mailboxes and slow internet connections). >>> >>>The problem came up with certain subfolders. And I believe it only >>>happens with subfolders that have spaces in their names. I had two >>>user's mailboxes (under Sent), one of which had a "Sent Messages" >>>symlink alias for "Sent", that started generating tens or hundreds of >>>duplicates during sync. Fortunately those subfolders only had a few >>>mails in them. But I had trees looking like: >>> >>>[...] (below is under /var/mail/domain/user/sdbox/mailboxes/Sent/) >>>Proposal >>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-1-temp-f80b1a00ce9aa961a86-temp-2 >>>Proposal >>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-1-temp-f80b1a00ce9aa961a86-temp-3 >>>Proposal >>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-023fa4271c9ca9611ade0400b88bfabe >>>Proposal >>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-023fa4271c9ca9611ad-temp-1 >>>Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-1 >>>Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-2 >>>Proposal >>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-2-temp-1-temp-1 >>>Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-3 >>>Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-4 >>>Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-5 >>>Proposal >>>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-e2aa0f35c99ba961356500009db5accb >>>[...] >>> >>>I kept stopping, cleaning up the folders, and re-starting - and they >>>kept regenerating. I tried renaming the folders to eliminate the >>>spaces and I think that helped in one case - for the others I just >>>moved the folders outside of the mail area completely to let the sync >>>finish. >>> >>>Now that it's been stable for a day or two - I enabled sync in the >>>other direction. And after setting *all* the required parameters >>>instead of just most of them...it's working. But...I'm nervous about >>>moving the problem folders back over. I will say, if it makes any >>>difference, my primary server *was* running version 2.3.13 and I just >>>updated it to 2.3.17. The remote is also 2.3.17. >>> >>>-- >>>Daniel

1 0

Re[2]: Replication weirdness
by Daniel Miller 04 Dec '21

04 Dec '21

And...one more. I'm now seeing (again) messages like: Dec 3 14:29:14 cloud1 dovecot: doveadm(obfuscated)<334017><e3FHNjmaqmHBGAUAuIv6vg>: Error: Duplicate mailbox GUID bcb9ca36ae36aa617f0a00009db5accb for mailboxes INBOX/Sent Messages and INBOX/Sent - giving a new GUID fc30bd0a3a9aaa61c1180500b88bfabe to INBOX/Sent Dec 3 14:38:59 cloud1 dovecot: doveadm(obfuscated)<334394><an5KIoOcqmE6GgUAuIv6vg>: Error: Duplicate mailbox GUID fc30bd0a3a9aaa61c1180500b88bfabe for mailboxes INBOX/Sent Messages and INBOX/Sent - giving a new GUID f4338038839caa613a1a0500b88bfabe to INBOX/Sent Having one message for the initial sync I suppose is reasonable. A second...maybe? But I'm getting nervous I'm about to start seeing the endless temp folders again. -- Daniel ------ Original Message ------ From: "Daniel Miller" <dmiller(a)amfes.com> To: "Daniel Miller" <dmiller(a)amfes.com>; dovecot(a)dovecot.org Sent: 12/3/2021 2:39:25 PM Subject: Re: Replication weirdness >Another item. > >Again, it may be a 2.3.13 issue and I'm now on 2.3.17. But...I had >problem when using the "-N" parameter for dsync. So - I just have >(had): > >replication_dsync_parameters = -d -l 30 -U -x INBOX/virtual -x >INBOX/shared > >Now that things are working - I wanted to have my other namespaces sync >as well. So I went to: > >replication_dsync_parameters = -d -l 30 -U -n INBOX -n INBOX/Archives >-n INBOX/Lists -x INBOX/virtual -x INBOX/shared > >This appears to be working (the sync is just starting)...but I'm seeing >lock errors in the logs such as: >Dec 3 14:34:24 bubba dovecot: >doveadm(dmiller(a)amfes.com)<31785><TV+0LlGbqmEpfAAAnbWsyw>: Error: >Couldn't lock /var/mail/amfes.com/dmiller/.dovecot-sync.lock: >fcntl(/var/mail/amfes.com/dmiller/.dovecot-sync.lock, write-lock, >F_SETLKW) locking failed: Timed out after 30 seconds (WRITE lock held >by pid 31373) > >Checking the pid in question I see it's actively syncing a folder in my >mailbox. So I'm guessing, purely guessing, that by having multiple >namespaces explicitly directed to sync Dovecot is trying to start a >sync process for each of those namespaces - but all of them share a >common lock and therefore only one operation is allowed at a time. > >Am I correct, and whether or not I am - how can I correct these errors? >Do I dare try going back to just "-N"? > >-- >Daniel > >------ Original Message ------ >From: "Daniel Miller" <dmiller(a)amfes.com> >To: dovecot(a)dovecot.org >Sent: 12/3/2021 2:16:28 PM >Subject: Replication weirdness > >>First, I have to say this. After configuring everything correctly - >>and that means *everything* correctly - Dovecot replication Just >>Works. I'm not sure how (yes I do - Timo & Co. Magic) - but it does. >>Real-time new sync is near instantaneous. >> >>Now the problem. Or the background for the problem. My primary server >>uses sdbox for primary storage, mdbox for archival storage, and >>fts-solr. I spun up a second server, using sdbox, mdbox, and >>fts-flatcurve. My namespaces are as defined below. As best I can tell >>(based on diff comparing two 'doveconf -n' outputs) my namespaces are >>the same on both servers. >> >>namespace archives { >> list = children >> location = mdbox:/var/mail/%d/%n/Archives/mdbox >> mailbox Unsorted { >> auto = no >> special_use = \Archive >> } >> prefix = INBOX/Archives/ >> separator = / >> subscriptions = no >> type = private >>} >>namespace inbox { >> alias_for = >> hidden = no >> inbox = yes >> list = yes >> location = >> mailbox "Deleted Messages" { >> auto = no >> autoexpunge = 30 days >> special_use = \Trash >> } >> mailbox Drafts { >> auto = subscribe >> special_use = \Drafts >> } >> mailbox Sent { >> auto = subscribe >> special_use = \Sent >> } >> mailbox Trash { >> auto = subscribe >> autoexpunge = 30 days >> special_use = \Trash >> } >> prefix = INBOX/ >> separator = / >> subscriptions = no >> type = private >>} >>namespace lists { >> list = children >> location = mdbox:/var/mail/%d/%n/Lists/mdbox >> prefix = INBOX/Lists/ >> separator = / >> subscriptions = no >> type = private >>} >>namespace subscriptions { >> hidden = yes >> list = no >> location = >> prefix = >> separator = / >> subscriptions = yes >> type = private >>} >>namespace usershares { >> list = yes >> location = sdbox:/var/mail/%%d/%%n/sdbox:NO-NOSELECT >> prefix = INBOX/shared/%%d/%%n/ >> separator = / >> subscriptions = no >> type = shared >>} >>namespace virtual { >> list = children >> location = virtual:/var/mail/%d/%n/virtual >> mailbox Flagged { >> comment = All my flagged messages >> special_use = \Flagged >> } >> prefix = INBOX/virtual/ >> separator = / >> subscriptions = no >>} >> >>I also have: >>plugin { >> mailbox_alias_new = Sent Messages >> mailbox_alias_new2 = Sent Items >> mailbox_alias_new3 = Deleted Messages >> mailbox_alias_old = Sent >> mailbox_alias_old2 = Sent >> mailbox_alias_old3 = Trash >>} >> >>This setup worked fine with my single server. Then I enabled >>replication - just on the primary. Dsync went to work (it seemed to >>take forever for the initial sync but that's what happens with large >>mailboxes and slow internet connections). >> >>The problem came up with certain subfolders. And I believe it only >>happens with subfolders that have spaces in their names. I had two >>user's mailboxes (under Sent), one of which had a "Sent Messages" >>symlink alias for "Sent", that started generating tens or hundreds of >>duplicates during sync. Fortunately those subfolders only had a few >>mails in them. But I had trees looking like: >> >>[...] (below is under /var/mail/domain/user/sdbox/mailboxes/Sent/) >>Proposal >>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-1-temp-f80b1a00ce9aa961a86-temp-2 >>Proposal >>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-1-temp-f80b1a00ce9aa961a86-temp-3 >>Proposal >>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-023fa4271c9ca9611ade0400b88bfabe >>Proposal >>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-023fa4271c9ca9611ad-temp-1 >>Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-1 >>Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-2 >>Proposal >>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-2-temp-1-temp-1 >>Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-3 >>Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-4 >>Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-5 >>Proposal >>Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-e2aa0f35c99ba961356500009db5accb >>[...] >> >>I kept stopping, cleaning up the folders, and re-starting - and they >>kept regenerating. I tried renaming the folders to eliminate the >>spaces and I think that helped in one case - for the others I just >>moved the folders outside of the mail area completely to let the sync >>finish. >> >>Now that it's been stable for a day or two - I enabled sync in the >>other direction. And after setting *all* the required parameters >>instead of just most of them...it's working. But...I'm nervous about >>moving the problem folders back over. I will say, if it makes any >>difference, my primary server *was* running version 2.3.13 and I just >>updated it to 2.3.17. The remote is also 2.3.17. >> >>-- >>Daniel

1 0

Re: Replication weirdness
by Daniel Miller 04 Dec '21

04 Dec '21

Another item. Again, it may be a 2.3.13 issue and I'm now on 2.3.17. But...I had problem when using the "-N" parameter for dsync. So - I just have (had): replication_dsync_parameters = -d -l 30 -U -x INBOX/virtual -x INBOX/shared Now that things are working - I wanted to have my other namespaces sync as well. So I went to: replication_dsync_parameters = -d -l 30 -U -n INBOX -n INBOX/Archives -n INBOX/Lists -x INBOX/virtual -x INBOX/shared This appears to be working (the sync is just starting)...but I'm seeing lock errors in the logs such as: Dec 3 14:34:24 bubba dovecot: doveadm(dmiller(a)amfes.com)<31785><TV+0LlGbqmEpfAAAnbWsyw>: Error: Couldn't lock /var/mail/amfes.com/dmiller/.dovecot-sync.lock: fcntl(/var/mail/amfes.com/dmiller/.dovecot-sync.lock, write-lock, F_SETLKW) locking failed: Timed out after 30 seconds (WRITE lock held by pid 31373) Checking the pid in question I see it's actively syncing a folder in my mailbox. So I'm guessing, purely guessing, that by having multiple namespaces explicitly directed to sync Dovecot is trying to start a sync process for each of those namespaces - but all of them share a common lock and therefore only one operation is allowed at a time. Am I correct, and whether or not I am - how can I correct these errors? Do I dare try going back to just "-N"? -- Daniel ------ Original Message ------ From: "Daniel Miller" <dmiller(a)amfes.com> To: dovecot(a)dovecot.org Sent: 12/3/2021 2:16:28 PM Subject: Replication weirdness >First, I have to say this. After configuring everything correctly - and >that means *everything* correctly - Dovecot replication Just Works. I'm >not sure how (yes I do - Timo & Co. Magic) - but it does. Real-time new >sync is near instantaneous. > >Now the problem. Or the background for the problem. My primary server >uses sdbox for primary storage, mdbox for archival storage, and >fts-solr. I spun up a second server, using sdbox, mdbox, and >fts-flatcurve. My namespaces are as defined below. As best I can tell >(based on diff comparing two 'doveconf -n' outputs) my namespaces are >the same on both servers. > >namespace archives { > list = children > location = mdbox:/var/mail/%d/%n/Archives/mdbox > mailbox Unsorted { > auto = no > special_use = \Archive > } > prefix = INBOX/Archives/ > separator = / > subscriptions = no > type = private >} >namespace inbox { > alias_for = > hidden = no > inbox = yes > list = yes > location = > mailbox "Deleted Messages" { > auto = no > autoexpunge = 30 days > special_use = \Trash > } > mailbox Drafts { > auto = subscribe > special_use = \Drafts > } > mailbox Sent { > auto = subscribe > special_use = \Sent > } > mailbox Trash { > auto = subscribe > autoexpunge = 30 days > special_use = \Trash > } > prefix = INBOX/ > separator = / > subscriptions = no > type = private >} >namespace lists { > list = children > location = mdbox:/var/mail/%d/%n/Lists/mdbox > prefix = INBOX/Lists/ > separator = / > subscriptions = no > type = private >} >namespace subscriptions { > hidden = yes > list = no > location = > prefix = > separator = / > subscriptions = yes > type = private >} >namespace usershares { > list = yes > location = sdbox:/var/mail/%%d/%%n/sdbox:NO-NOSELECT > prefix = INBOX/shared/%%d/%%n/ > separator = / > subscriptions = no > type = shared >} >namespace virtual { > list = children > location = virtual:/var/mail/%d/%n/virtual > mailbox Flagged { > comment = All my flagged messages > special_use = \Flagged > } > prefix = INBOX/virtual/ > separator = / > subscriptions = no >} > >I also have: >plugin { > mailbox_alias_new = Sent Messages > mailbox_alias_new2 = Sent Items > mailbox_alias_new3 = Deleted Messages > mailbox_alias_old = Sent > mailbox_alias_old2 = Sent > mailbox_alias_old3 = Trash >} > >This setup worked fine with my single server. Then I enabled >replication - just on the primary. Dsync went to work (it seemed to >take forever for the initial sync but that's what happens with large >mailboxes and slow internet connections). > >The problem came up with certain subfolders. And I believe it only >happens with subfolders that have spaces in their names. I had two >user's mailboxes (under Sent), one of which had a "Sent Messages" >symlink alias for "Sent", that started generating tens or hundreds of >duplicates during sync. Fortunately those subfolders only had a few >mails in them. But I had trees looking like: > >[...] (below is under /var/mail/domain/user/sdbox/mailboxes/Sent/) >Proposal >Requests-temp-c6e003375e64a961c93d00009db5accb-temp-1-temp-f80b1a00ce9aa961a86-temp-2 >Proposal >Requests-temp-c6e003375e64a961c93d00009db5accb-temp-1-temp-f80b1a00ce9aa961a86-temp-3 >Proposal >Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-023fa4271c9ca9611ade0400b88bfabe >Proposal >Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-023fa4271c9ca9611ad-temp-1 >Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-1 >Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-2 >Proposal >Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-2-temp-1-temp-1 >Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-3 >Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-4 >Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-5 >Proposal >Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-e2aa0f35c99ba961356500009db5accb >[...] > >I kept stopping, cleaning up the folders, and re-starting - and they >kept regenerating. I tried renaming the folders to eliminate the spaces >and I think that helped in one case - for the others I just moved the >folders outside of the mail area completely to let the sync finish. > >Now that it's been stable for a day or two - I enabled sync in the >other direction. And after setting *all* the required parameters >instead of just most of them...it's working. But...I'm nervous about >moving the problem folders back over. I will say, if it makes any >difference, my primary server *was* running version 2.3.13 and I just >updated it to 2.3.17. The remote is also 2.3.17. > >-- >Daniel

1 0

Replication weirdness
by Daniel Miller 04 Dec '21

04 Dec '21

First, I have to say this. After configuring everything correctly - and that means *everything* correctly - Dovecot replication Just Works. I'm not sure how (yes I do - Timo & Co. Magic) - but it does. Real-time new sync is near instantaneous. Now the problem. Or the background for the problem. My primary server uses sdbox for primary storage, mdbox for archival storage, and fts-solr. I spun up a second server, using sdbox, mdbox, and fts-flatcurve. My namespaces are as defined below. As best I can tell (based on diff comparing two 'doveconf -n' outputs) my namespaces are the same on both servers. namespace archives { list = children location = mdbox:/var/mail/%d/%n/Archives/mdbox mailbox Unsorted { auto = no special_use = \Archive } prefix = INBOX/Archives/ separator = / subscriptions = no type = private } namespace inbox { alias_for = hidden = no inbox = yes list = yes location = mailbox "Deleted Messages" { auto = no autoexpunge = 30 days special_use = \Trash } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe autoexpunge = 30 days special_use = \Trash } prefix = INBOX/ separator = / subscriptions = no type = private } namespace lists { list = children location = mdbox:/var/mail/%d/%n/Lists/mdbox prefix = INBOX/Lists/ separator = / subscriptions = no type = private } namespace subscriptions { hidden = yes list = no location = prefix = separator = / subscriptions = yes type = private } namespace usershares { list = yes location = sdbox:/var/mail/%%d/%%n/sdbox:NO-NOSELECT prefix = INBOX/shared/%%d/%%n/ separator = / subscriptions = no type = shared } namespace virtual { list = children location = virtual:/var/mail/%d/%n/virtual mailbox Flagged { comment = All my flagged messages special_use = \Flagged } prefix = INBOX/virtual/ separator = / subscriptions = no } I also have: plugin { mailbox_alias_new = Sent Messages mailbox_alias_new2 = Sent Items mailbox_alias_new3 = Deleted Messages mailbox_alias_old = Sent mailbox_alias_old2 = Sent mailbox_alias_old3 = Trash } This setup worked fine with my single server. Then I enabled replication - just on the primary. Dsync went to work (it seemed to take forever for the initial sync but that's what happens with large mailboxes and slow internet connections). The problem came up with certain subfolders. And I believe it only happens with subfolders that have spaces in their names. I had two user's mailboxes (under Sent), one of which had a "Sent Messages" symlink alias for "Sent", that started generating tens or hundreds of duplicates during sync. Fortunately those subfolders only had a few mails in them. But I had trees looking like: [...] (below is under /var/mail/domain/user/sdbox/mailboxes/Sent/) Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-1-temp-f80b1a00ce9aa961a86-temp-2 Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-1-temp-f80b1a00ce9aa961a86-temp-3 Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-023fa4271c9ca9611ade0400b88bfabe Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-023fa4271c9ca9611ad-temp-1 Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-1 Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-2 Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-2-temp-1-temp-1 Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-3 Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-4 Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-5 Proposal Requests-temp-c6e003375e64a961c93d00009db5accb-temp-2-temp-e2aa0f35c99ba961356500009db5accb [...] I kept stopping, cleaning up the folders, and re-starting - and they kept regenerating. I tried renaming the folders to eliminate the spaces and I think that helped in one case - for the others I just moved the folders outside of the mail area completely to let the sync finish. Now that it's been stable for a day or two - I enabled sync in the other direction. And after setting *all* the required parameters instead of just most of them...it's working. But...I'm nervous about moving the problem folders back over. I will say, if it makes any difference, my primary server *was* running version 2.3.13 and I just updated it to 2.3.17. The remote is also 2.3.17. -- Daniel

1 0

Searching 30 GB mailbox
by Einar Bjarni Halldórsson 03 Dec '21

03 Dec '21

Hi, We're migrating our mailboxes from Zimbra to dovecot, running on FreeBSD 12.2. We're using mdbox and solr for fts. dovecot version 2.3.17. One of our mailboxes gets a bcc of every outgoing mail from our system and it currently holds ~4.5 million messages taking 30 GB. One of the ways we use the mailbox is that when outgoing mail is sent, we store the Message-ID in our database, and in our admin interface we can open the mail and it's fetched from IMAP by doing a 'SEARCH HEADER Message-ID <MSG_ID>'. In Zimbra this was reasonably fast, but after migrating the mailbox to dovecot it's 30 seconds which I think we can reduce. After turning on mail_debug I see this in our log https://pastebin.com/kP9H7gSB Looks like solr finishes searching instantly, then there's ~30 seconds of silence in the logs, and then more log lines about fetching data from mail cache. The same thing happens if I use telnet and just issue a 'SEARCH HEADER...' command. How can I find out what dovecot is doing in those 30 seconds? .einar

5 14

Expunged message reappeared
by Claudio Corvino 03 Dec '21

03 Dec '21

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

1 1

Re: new bee needs starter docs
by Gene Heskett 03 Dec '21

03 Dec '21

On Fri, 3 Dec, 2021 at 3:50 AM, Christian Mack <christian.mack(a)uni-konstanz.de> wrote: To: dovecot(a)dovecot.org Hello What you need is probably 'doveadm sync'. Check its manual with man doveadm-sync I did, that's equ to my climbing El Capitan at 87 yo. 'taint gonna happen. So I think I'll try to make my old method work, so back to the kde-pim list. Kind regards, Christian Mack Thank you Christian

1 0

Issue with SCRAM-SHA Authorization
by Thomas Schmid 03 Dec '21

03 Dec '21

Hi, I was debugging a bug report for my sieve editor implementation concerning an issue with SCRAM-SHA Authorization. But I am a bit unsure about my findings. It seems to be a server side bug. But I am wondering if I missed something. What puzzles me a bit is that SCRAM-SHA is out since ages and obviously no one ran into this issue. Which feels odd. When I try to connect to a dovecot server with enabled Authorization, then SCRAM SHA1 or SHA256 fail with a channel binding error. Authorization via SASL PLAIN works perfectly fine. So I digged into the logs. The trace is below also my findings/conclusion. The username and authorization in the trace are set to "user" the password is "pencil". Nov 24 14:00:06 auth: Debug: client in: AUTH 1 SCRAM-SHA-256 service=sieve secured=tlssession=sI9yRonRZISsEQAB lip=172.17.0.2 rip=172.17.0.1 lport=4190 rport=33892 resp=bixhPXVzZXIsbj11c2VyLHI9ZmEzZGY1NjNlZjczZTY3YjQzZThhZWRiZjUzNGI1NWIxNzIwNzU3OThjZmJiMjExNmMyMTNkMWM4NDE4MmZkOQ== (previous base64 data may contain sensitive data) Nov 24 14:00:06 auth: Debug: passwd-file(user,172.17.0.1,<sI9yRonRZISsEQAB>): Performing passdb lookup Nov 24 14:00:06 auth: Debug: passwd-file(user,172.17.0.1,<sI9yRonRZISsEQAB>): lookup: user=user file=/etc/dovecot/users Nov 24 14:00:06 auth: Debug: passwd-file(user,172.17.0.1,<sI9yRonRZISsEQAB>): Generating SCRAM-SHA-256 from user 'user', password 'pencil' Nov 24 14:00:06 auth: Debug: passwd-file(user,172.17.0.1,<sI9yRonRZISsEQAB>): Finished passdb lookup Nov 24 14:00:06 auth: Debug: Credentials: 343039362c326b3934364452546c326431765a37434b6d556c32513d3d2c46444d364f7173577035464c446e394151666554316547585045427a47566d6965673842427331456d37633d2c79766e5a4169376250392f59706c4a71597872356a79794f7a6e4c664730667636485155325a7a6975376b3d Nov 24 14:00:06 auth: Debug: client passdb out: CONT 1 cj1mYTNkZjU2M2VmNzNlNjdiNDNlOGFlZGJmNTM0YjU1YjE3MjA3NTc5OGNmYmIyMTE2YzIxM2QxYzg0MTgyZmQ5J2Q9NCskV2NuWEFVTnZxOU1EZENgM2UheVguXFw3O2JgKlg0X29gKDtBXnJrTi1xUmQ2IXgiQX5+eGU8ZlJHWSxzPTJrOTQ2RFJUbDJkMXZaN0NLbVVsMlE9PSxpPTQwOTY= Nov 24 14:00:06 auth: Debug: client in: CONT 1 Yz1iaXhoUFhWelpYSXMscj1mYTNkZjU2M2VmNzNlNjdiNDNlOGFlZGJmNTM0YjU1YjE3MjA3NTc5OGNmYmIyMTE2YzIxM2QxYzg0MTgyZmQ5J2Q9NCskV2NuWEFVTnZxOU1EZENgM2UheVguXFw3O2JgKlg0X29gKDtBXnJrTi1xUmQ2IXgiQX5+eGU8ZlJHWSxwPUcvZGZWUUlGZy9NMkpSMlpEMXM0cms4MS9jTmFMa0tuMzZFYzFlTTN1enc9 (previous base64 data may contain sensitive data) Nov 24 14:00:06 auth: Info: scram-sha-256(user,172.17.0.1,<sI9yRonRZISsEQAB>): Invalid channel binding data Nov 24 14:00:06 auth: Debug: auth(user,172.17.0.1,<sI9yRonRZISsEQAB>): Auth request finished Nov 24 14:00:08 auth: Debug: client passdb out: FAIL 1 user=user Nov 24 14:00:08 managesieve-login: Info: Disconnected: Aborted login by logging out (auth failed, 1 attempts in 2 secs): user=<user>, method=SCRAM-SHA-256, rip=172.17.0.1, lip=172.17.0.2, TLS, session=<sI9yRonRZISsEQAB> Nov 24 14:00:08 managesieve-login: Debug: SSL alert: close notify The matching trace from the client, a sieve editor (https://github.com/thsmi/sieve) is as follows: [15:000:06.192 kw53213a-qc7kf99m1lp] Client -> Server: AUTHENTICATE "SCRAM-SHA-256" "bixhPXVzZXIsbj11c2VyLHI9ZmEzZGY1NjNlZjczZTY3YjQzZThhZWRiZjUzNGI1NWIxNzIwNzU3OThjZmJiMjExNmMyMTNkMWM4NDE4MmZkOQ==" [15:000:06.202 kw53213a-qc7kf99m1lp] Server -> Client "cj1mYTNkZjU2M2VmNzNlNjdiNDNlOGFlZGJmNTM0YjU1YjE3MjA3NTc5OGNmYmIyMTE2YzIxM2QxYzg0MTgyZmQ5J2Q9NCskV2NuWEFVTnZxOU1EZENgM2UheVguXFw3O2JgKlg0X29gKDtBXnJrTi1xUmQ2IXgiQX5+eGU8ZlJHWSxzPTJrOTQ2RFJUbDJkMXZaN0NLbVVsMlE9PSxpPTQwOTY=" [15:000:06.209 kw53213a-qc7kf99m1lp] Client -> Server: "Yz1iaXhoUFhWelpYSXMscj1mYTNkZjU2M2VmNzNlNjdiNDNlOGFlZGJmNTM0YjU1YjE3MjA3NTc5OGNmYmIyMTE2YzIxM2QxYzg0MTgyZmQ5J2Q9NCskV2NuWEFVTnZxOU1EZENgM2UheVguXFw3O2JgKlg0X29gKDtBXnJrTi1xUmQ2IXgiQX5+eGU8ZlJHWSxwPUcvZGZWUUlGZy9NMkpSMlpEMXM0cms4MS9jTmFMa0tuMzZFYzFlTTN1enc9" [15:000:08.215 kw53213a-qc7kf99m1lp] Server -> Client NO "Authentication failed." According to the RFC (https://datatracker.ietf.org/doc/html/rfc5802) the initial request is defined as: (("p=" cb-name) / "n" / "y") "," [ authzid ] "," client-first-message-bare This means the decoded message from the trace is: n,a=user,n=user,r=fa3df563ef73e67b43e8aedbf534b55b172075798cfbb2116c213d1c84182fd9 The final request (which is rejected by the server with the binding error) is defined as : client-final-message-without-proof = channel-binding "," nonce [","extensions] or client-final-message = client-final-message-without-proof "," proof So the request from the trace decodes into: c=bixhPXVzZXIs,r=fa3df563ef73e67b43e8aedbf534b55b172075798cfbb2116c213d1c84182fd9'd=4+$WcnXAUNvq9MDdC`3e!yX.\\7;b`*X4_o`(;A^rkN-qRd6!x"A~~xe<fRGY,p=G/dfVQIFg/M2JR2ZD1s4rk81/cNaLkKn36Ec1eM3uzw= The channel-binding and cbind-input part are defined as: channel-binding = "c=" base64(cbind-input) cbind-input = (("p=" cb-name) / "n" / "y") "," [ authzid ] "," [ cbind-data ] where cbind-data has to be absent by definition as dovecot does not support channel binding so no "p=" is possible and thus no cbind-data. This means c=bixhPXVzZXI decodes into. n,a=user, And this is where it gets strange. The dovecot code section which throws the error, implements the following: https://github.com/dovecot/core/blob/a5209c83c3a82386c94d466eec5fea394973e8… cbind_input = t_strconcat(request->gs2_cbind_flag, ",,", NULL); str = t_str_new(MAX_BASE64_ENCODED_SIZE(strlen(cbind_input))); str_append(str, "c="); base64_encode(cbind_input, strlen(cbind_input), str); if (strcmp(fields[0], str_c(str)) != 0) { *error_r = "Invalid channel binding data"; return FALSE; } As you can see it uses the bind flag which was saved to the request. But instead of the authzid, it uses always an hardcoded empty string. Thus cbind-input is "n,," instead of "n,a=user," and results in the request being rejected with an "Invalid channel binding data". Which is on the one hand a funny message because dovecot does not support channel binding at all, as describe in https://github.com/dovecot/core/blob/a5209c83c3a82386c94d466eec5fea394973e8… but it also on the other hand somehow correct because cbind-input string does not match. Which is an illegal state during channel binding negotiation which should not happen. As said previously, it looks to me like a server side bug. Or did I miss something special case in the RFC? Kind Regards Thomas Schmid

2 1

LDAP Help
by Günther J. Niederwimmer 03 Dec '21

03 Dec '21

Hello Dovecot professionals, I have a working user authentication with LDAP, now I want to allow the users to use mailAterneteAddress for their account, unfortunately I can't find any filter settings for dovecot that this works? I just can't find the right settings for LDAP (FreeIPA). Does anyone of you have any hints or links so that I can get on with it. Somehow I don't understand how I can umconvigure the dovecot-ldap.conf.ext Thank you for your help. -- mit freundlichen Grüßen / best regards Günther J. Niederwimmer

4 3

new bee needs starter docs
by Gene Heskett 03 Dec '21

03 Dec '21

Greetings all' Brand New today install of debian bullseye. I have looked at you doc pages, but don't see a good tut for a newbie to use for setting it up the first time ever. I have version 2.3.13 (89f716dc2) from the debian bullseye distro. What I want is to pull from my ISP account, which is also running dovecot, to a local mailfile. Or I can do that with fetchmail, its been doing that for a decade already. Its currently using procmail to run stuff thru spamassassin and clamd depositing the survivors into a /var/mail/mailfile, which the older tde kmail then pulled and sorted into folders holding maildirs. But I can't get tde to install on bullseye. Kudo's for any help you can supply. Cheers, Gene

2 1

execve(/usr/bin/sieve-test) failed: Argument list too long
by Patrick Cernko 03 Dec '21

03 Dec '21

Hi Dovecot developers, while debugging the above error message from sieve-test, I found out, that the content of directive ssl_ca is added as env var SSL_CA by doveconf on execve and sieve-test now uses doveconf. In our setup, ssl_ca is set to ssl_ca = </etc/ssl/certs/ca-certificates.crt on our director servers. We have backend servers with certificates signed by two different CAs and to avoid problems if a backend switches to a different CA, I decided to allow all "known" CAs. The corresponding env var SSL_CA has more than 230500 bytes, which causes execve to fail with error E2BIG. I found a workaround for the problem by setting ssl_ca = </etc/dovecot/backendCAs.pem Where this file contains only the two CAs used atm. However I would like to request a fix for this issue as others might also want to have all "known" CAs set for dovecot director backend connections. Best, -- Patrick Cernko <pcernko(a)mpi-klsb.mpg.de> +49 681 9325 5815 Joint Administration: Information Services and Technology Max-Planck-Institute fuer Informatik & Softwaresysteme

2 1