- dovecot - dovecot.org

How to omit the DH parameter in v2.3.3+ ( as stated in 'Upgrading Dovecot v2.2 to v2.3' )
by J. Sommersberg 27 Apr '21

27 Apr '21

Hi, i just finished tuning my dovecot setup after upgrading to 2.3.7.2. I needed to add the "ssl_dh =„ parameter to my config as stated in the online docs at dovecot.org <http://dovecot.org/>. That was no problem and is well documented there and the hint in the log on startup also helped to quickly identify the problem. After that i was curious and read more and did a lot of research. But i just could not find out how to „omit“ the DH parameter as stated in the online docs: https://doc.dovecot.org/installation_guide/upgrading/from-2.2-to-2.3/ <https://doc.dovecot.org/installation_guide/upgrading/from-2.2-to-2.3/> It says : „Since v2.3.3+ DH parameter usage is optional and can be omitted.“ I trried it in different ways. First i disallowed DH on the ssl_cipher_list like it was suggested in the example in this doc. But it will still give Errors on startup/reload of dovecot. Next i tried ssl_dh = that also did not work. I could not figure out how to „omit“ the DH parameter. Is it just my misinterpretation of the config doc? thanks for clarifying Best regards joerg

2 1

doveadm sync duplicating emails
by Paul Robinson 27 Apr '21

27 Apr '21

I'm upgrading a mail server using postfix 2.9.6 and dovecot 2.0.19 to a new server running postfix 3.4.13 and dovecot 2.3.7.2 (using Maildir format on both sides). I had trouble getting doveadm backup to work for one user, while all the others worked straight away. It would complain about problems on the old server in the Maildir/dovecot* files. I managed to get it to work by removing all the dovecot* files under Maildir for that one user (accepting that this would mean clients having to redownload emails). >From that point, a doveadm backup worked. Using roundcube to look at the new mail server, I could see everything arrived. At this point, some mail generated on the new mail server would go to the new mail server, but all other mail is going to the old mail server. I then tried to use doveadm sync -1R to update the new mail server so the new server contains all the mail from the old server plus the new mail that has been locally delivered. What then happened was that all the new emails delivered to the old server since the backup were copied to the new server, and all the emails that were locally delivered on the new mail server were still there. (So far so good). But I also saw that every email that was on the old server before the backup now appeared twice on the new mail server. Running sync again would mean I had three copies of email. The sync ran quickly - much too quickly for these extra copies to have been sent over the network. It appears that the sync made extra local copies on the new server. I see no errors in logs that can explain things. Looking at the email, the files stored in the cur directories are there multiple times; they have different names, but identical content. Trying "doveadm deduplicate -F user-list ALL" ran quickly and to no effect (where user-list is a file with a list of users). Trying "doveadm deduplicate -F user-list -m ALL" takes 100% cpu and a long time to run and still running right now after 4 hours. Judging by the disk space usage freed up, this is going to take a very long time to complete. Has anybody got any idea what might cause this and what change I should make? This was the sync command line: doveadm -vc /etc/dovecot/dovecot-migration.conf sync -1RF user-list imapc: For the backup and sync, I used this as the config: imapc_features = rfc822.size fetch-headers imapc_host = <snipped> imapc_ssl = imaps imapc_port = 993 imapc_user = %n imapc_master_user = master imapc_password = <snipped> mail_prefetch_count = 20 ssl_cipher_list = EECDH+AESGCM+AES128:EECDH+AESGCM+AES256:EECDH+CHACHA20:EDH+AESGCM+AES128:EDH+AESGCM+AES256:EDH+CHACHA20:EECDH+SHA256+AES128:EECDH+SHA384+AES256:EDH+SHA256+AES128:EDH+SHA256+AES256:EECDH+SHA1+AES128:EECDH+SHA1+AES256:EDH +SHA1+AES128:EDH+SHA1+AES256:EECDH+HIGH:EDH+HIGH:AESGCM+AES128:AESGCM+AES256:CHACHA20:SHA256+AES128:SHA256+AES256:SHA1+AES128:SHA1+AES256:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!3DES:!MD5:!PSK:!KRB5:!aECDH:!DH mail_location = maildir:~/Maildir mail_home = /var/vmail/%d/%n/ mail_fsync=never Thanks, Paul

2 1

failed: Cached message size smaller than expected
by Michael Grant 27 Apr '21

27 Apr '21

Every few days, my mailbox seizes up. No mail come in to my imap clients. I'm getting these errors over and over with my mailbox: Error: Mailbox INBOX: Deleting corrupted cache record uid=371208: UID 371208: Broken physical size in mailbox INBOX: read(/var/mail/mgrant) failed: Cached message size smaller than expected (17212 < 17222, box=INBOX, UID=371208) Error: Mailbox INBOX: UID=371208: read(/var/mail/mgrant) failed: Cached message size smaller than expected (17212 < 17222, box=INBOX, UID=371208) (FETCH BODY[]) Error: Mailbox INBOX: Deleting corrupted cache record uid=371203: UID 371203: Broken physical size in mailbox INBOX: read(/var/mail/mgrant) failed: Cached message size smaller than expected (3904 < 3914, box=INBOX, UID=371203) Error: Mailbox INBOX: UID=371203: read(/var/mail/mgrant) failed: Cached message size smaller than expected (3904 < 3914, box=INBOX, UID=371203) (FETCH BODY[]) My inbox is an mbox file. I'm running dovecot installed on Debian Bullseye, the dovecot packages are all: 1:2.3.13+dfsg1-1 I am running sendmail and using procmail for local delivery. I suspect, but am not certain, that this may be some locking issue between procmail and dovecot but I have never been able to prove that. The final procmail rule which appends messages to my mailbox looks like this, the trailing ':' causes procmail to use a lockfile: :0: /var/mail/mgrant The locking config lines in 10-mail.conf are commented, but I have also tried uncommenting them, did not help: #mbox_read_locks = fcntl #mbox_write_locks = fcntl dotlock Though sometimes it seems to fix itself after a few hours, the only way I have found to fix this quickly is to manually remove the cache files and restart dovecot: rm ~/mail/.imap/INBOX/* systemctl restart dovecot I am not even sure this is a locking issue. Something definitely gets corrupted though. I do have several IMAP clients hitting the same mailbox (phone, laptop, desktop). On the phone, I run K9 and also the gmail client which talks imap. Also using thunderbird, outlook, and w10 mail, though typically not all at the same time. You could definitely say I am stress testing this setup a bit! Any ideas on how to resolve this? Michael Grant

6 10

Dovecot integration w/ FreeIPA expired password as well as if over quota login notice; local user can't login
by Robert Kudyba 26 Apr '21

26 Apr '21

As I continue to test freeipa-server-4.9.3-1, on Fedora 33 with dovecot-2.3.14-1 I've run into the following issues with web mail and Dovecot integration. 1. I followed https://www.freeipa.org/page/Dovecot_IMAPS_Integration_with_FreeIPA_using_S… but I couldn't get web mail to login until I used the suggestion from https://blog.delouw.ch/2017/02/19/integrate-dovecot-imap-with-freeipa-using… and changed logins auth_mechanisms = plain gssapi login which allowed logins of FreeIPA Kerberos users. 2. even with auth_mechanisms = plain gssapi login, I could then no longer login to SquirrelMail webmail with any local Unix (non-Kerberized) users. The dovecot logs show: auth: Error: policy(localuser(a)ourdomain.edu,127.0.0.1,<r2eFe+PAvut/AAAB>): Policy server HTTP error: connect(x.x.x.x:8084) failed: Connection refused auth: Debug: policy(localuser(a)ourdomain.edu,127.0.0.1,<r2eFe+PAvut/AAAB>): Policy report action finished auth: Debug: http-client[1]: request [Req2: POST https://x.x.x.x:8084/?command=report] Destroy (requests left=1) auth: Debug: http-client[1]: request [Req2: POST https://x.x.x.x:8084/?command=report] Free (requests left=0) auth: Debug: http-client: conn x.x.x.x[2]: Connection close auth: Debug: http-client: conn x.x.x.x[2]: Connection disconnect auth: Debug: http-client: conn x.x.x.x[2]: Disconnected: connect() failed: Connection refused (fd=23) auth: Debug: http-client: conn x.x.x.x[2]: Detached peer auth: Debug: http-client: conn x.x.x.x[2]: Connection destroy auth: Debug: http-client: host x.x.x.x: Idle host timed out auth: Debug: http-client: host x.x.x.x: Host destroy auth: Debug: http-client: host x.x.x.x: Host session destroy auth: Debug: http-client[1]: queue https://x.x.x.x:8084: Destroy auth: Debug: client passdb out: FAIL 1 user=localuser(a)ourdomain.edu original_user=localuser imap-login: Debug: Ignoring unknown passdb extra field: original_user imap-login: Info: Aborted login (auth failed, 1 attempts in 3 secs): user=< localuser(a)ourdomain.edu>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, session=<r2eFe+PAvut/AAAB> 3. If a user was over quota there was no way to tell on the webmail page that they were over quota but the dovecot logs show imap(ouruser): Error: mkdir(/path/to/ouruser/mail/.imap) failed: Disk quota exceeded. Would there be a security risk if the web page displayed a warning that could be generalized to inform the user to either check their quota or password reset being needed?

1 0

Live migrating index/control files
by Eirik Rye 26 Apr '21

26 Apr '21

Hello, We are running a director-based dovecot cluster where the user's maildir and the indexes/control files are, for legacy reasons, stored on separate NFS-backends, i.e.: mail_location = maildir:~/Maildir:CONTROL=/mail/control/%1u/%2u/%u:INDEX=/mail/index/%1u/%2u/%u Both ~/Maildir and /mail/{control,index}/ are separate NFS-mounts, and we now want to consolidate all files to the user's home directory instead. The end goal is to stop using NFS altogether. I have devised a four step plan for gradually migrating the index/control files into the user's maildir, on a per-user basis: 1. Kick the user in an attempt to flush the user's index files: `doveadm director kick <username>` 2. Rsync the index/control files into the user's maildir: `rsync -uav /mail/{index,control}/${user:0:1}/${user:0:2}/${user}/ /mail/${user:0:1}/${user:0:2}/${user}/Maildir/;` 3. Update the (redis-based) userdb for the specific user to override mail_location to use the default CONTROL/INDEX locations: `{"mail": "maildir:~/Maildir"}` 4. Kick the user one last time so that they reconnect using the new settings. Unfortunately, after running this for a small batch of users, we recieved a couple reports that their clients had started to resynchronize and redownload their mailboxes, which is exactly what we're trying to avoid. There are no index related error messages related to the few users that reported these issues. From my understanding, clients become confused when the control files are changed or lost (`dovecot-uidlist` and `dovecot-uidvalidity`), so I suspect the kick + rsync + kick procedure is not robust enough for this. Does anyone have any experience with performing such a migration without taking systems offline for the duration? Any suggestions to make this process more transparent for our users, so as to not induce panic when their mailboxes abruptly appear empty? Best regards, Eirik

2 5

How to Easily Set Up a Full-Featured Linux Mail Server on Ubuntu 18.04.5 LTS with iRedMail 1.4.0
by Turritopsis Dohrnii Teo En Ming 26 Apr '21

26 Apr '21

Subject: How to Easily Set Up a Full-Featured Linux Mail Server on Ubuntu 18.04.5 LTS with iRedMail 1.4.0 Good day from Singapore, I followed linuxbabe.com's Xiao Guoan's guide and successfully setup a full featured Linux mail server on Ubuntu 18.04.5 LTS with IRedMail 1.4.0. Author: Mr. Turritopsis Dohrnii Teo En Ming (TARGETED INDIVIDUAL) Country: Singapore Date: 25 April 2021 Sunday Type of Publication: PDF Manual Document Version: 20210425.01 (1st release) ***IMPORTANT NOTICE*** Please note that Turritopsis Dohrnii Teo En Ming’s guide is based on Xiao Guoan’s guide at linuxbabe.com. Reference Guide Used by Teo En Ming: How to Easily Set Up a Full-Featured Mail Server on Ubuntu 18.04 with iRedMail Link: https://www.linuxbabe.com/mail-server/ubuntu-18-04-iredmail-email-server Original Author: Xiao Guoan The following is a list of open-source software that will be automatically installed and configured by iRedMail. • Postfix SMTP server • Dovecot IMAP server • Nginx web server to serve the admin panel and webmail • OpenLDAP, MySQL/MariaDB, or PostgreSQL for storing user information • Amavised-new for DKIM signing and verification • SpamAssassin for anti-spam • ClamAV for anti-virus • Roundcube webmail • SOGo groupware, providing webmail, calendar (CalDAV), contacts (CardDAV), tasks and ActiveSync services. • Fail2ban for protecting SSH • mlmmj mailing list manager • Netdata server monitoring • iRedAPD Postfix policy server for greylisting Redundant Download Links for Teo En Ming's PDF Manual: [1] https://drive.google.com/file/d/1un8sLLmNSMIt7V6blWCvJEgwGvxMbd4B/view?usp=… [2] https://drive.google.com/file/d/1i0vY7kfYkobu563qoI3_qCZg7G7BFoYR/view?usp=… [3] https://drive.google.com/file/d/1U9MFN1EklLbA8TMweLV5ntiSJuBBVkpQ/view?usp=… [4] https://www.docdroid.net/dW70KtS/iredmail-setup-1st-release-pdf [5] https://www.mediafire.com/file/evar7j28knqyoj6/IRedMail+Setup+1st+Release.p… [6] https://www.scribd.com/document/504932780/IRedMail-Setup-1st-Release Mr. Turritopsis Dohrnii Teo En Ming, 43 years old as of 26 April 2021, is a TARGETED INDIVIDUAL living in Singapore. He is an IT Consultant with a System Integrator (SI)/computer firm in Singapore. He is an IT enthusiast. -----BEGIN EMAIL SIGNATURE----- The Gospel for all Targeted Individuals (TIs): [The New York Times] Microwave Weapons Are Prime Suspect in Ills of U.S. Embassy Workers Link: https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html ******************************************************************************************** Singaporean Targeted Individual Mr. Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 14 Feb 2019 and refugee seeking attempts at the United Nations Refugee Agency Bangkok (21 Mar 2017), in Taiwan (5 Aug 2019) and Australia (25 Dec 2019 to 9 Jan 2020): [1] https://tdtemcerts.wordpress.com/ [2] https://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming -----END EMAIL SIGNATURE-----

1 0

cannot see my mails
by Jean-Max Reymond 26 Apr '21

26 Apr '21

Hi, After a change of server, I cannot see my mails. postfix is OK and I receive emails. If I send emails, with roundcube or thunderbird, I can see these new sent emails. Access rights seems OK. Dovecot with debug trace does not complain. Any tips ? append_dot_mydomain = no biff = no broken_sasl_auth_clients = yes compatibility_level = 2 content_filter = smtp-amavis:[127.0.0.1]:10024 home_mailbox = Maildir/ local_recipient_maps = $virtual_mailbox_maps local_transport = virtual mailbox_command = /usr/lib/dovecot/deliver -c /etc/dovecot/dovecot.conf -m "${EXTENSION}" message_size_limit = 30720000 milter_default_action = accept milter_protocol = 2 mydestination = localhost non_smtpd_milters = inet:localhost:12345 readme_directory = no slow_destination_concurrency_limit = 2 slow_destination_recipient_limit = 20 smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt smtp_use_tls = yes smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) smtpd_milters = inet:localhost:12345 smtpd_recipient_restrictions = reject_unknown_sender_domain, reject_unknown_recipient_domain, reject_unauth_pipelining, permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_sasl_auth_enable = yes smtpd_sasl_authenticated_header = yes smtpd_sasl_local_domain = $myhostname smtpd_sasl_path = private/dovecot-auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_sender_restrictions = reject_unknown_sender_domain smtpd_tls_auth_only = yes smtpd_tls_cert_file = /etc/dovecot/private/dovecot.pem smtpd_tls_key_file = /etc/dovecot/private/dovecot.key smtpd_tls_mandatory_ciphers = medium smtpd_tls_mandatory_protocols = SSLv3, TLSv1 smtpd_tls_received_header = yes smtpd_use_tls = yes tls_random_source = dev:/dev/urandom transport_maps = hash:/etc/postfix/transport vacation_destination_recipient_limit = 1 virtual_alias_maps = proxy:mysql:/etc/postfix/mysql/virtual_alias_maps.cf virtual_gid_maps = static:8 virtual_mailbox_base = /home/Mails virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql/virtual_domains_maps.cf virtual_mailbox_limit = 204800000 virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql/virtual_mailbox_maps.cf virtual_minimum_uid = 8 virtual_transport = virtual virtual_uid_maps = static:8 yahoo_destination_concurrency_limit = 4 yahoo_destination_rate_delay = 1s yahoo_destination_recipient_limit = 2 yahoo_initial_destination_concurrency = 1 -- Jean-Max Reymond CKR Solutions Open Source https://www.ckr-solutions.com

3 9

Panic: file ostream.c: assertion failed when using mail_filter on RHEL8
by Martijn Brinkers (list) 24 Apr '21

24 Apr '21

Hi, I installed dovecot on a new up-to-date RHEL8 test system and configured a simple mail_filter plugin which only copies the input back to the output (i.e., the filter does nothing special). On RHEL8 I get the following panic when saving the mail. The Dovecot version that comes with RHEL8 is dovecot-2.3.8-4.el8.x86_64 The mail_filter works correctly on an Ubuntu machine )2.2.33.2- 1ubuntu4.7) Any idea what's causing this panic on RHEL8 and how to fix it? Kind regards, Martijn Brinkers Log output (panic log is at the bottom) Apr 23 10:35:54 ciphermail-webmail dovecot[18680]: master: Dovecot v2.3.8 (9df20d2db) starting up for imap Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/lib20_auth_var_expand_crypt.so Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_sqlite.so Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth: Debug: Read auth token secret from /var/run/dovecot/auth-token-secret.dat Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth: Debug: auth client connected (pid=19771) Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth: Debug: client in: AUTH 1 PLAIN service=imap secured se ssion=i7avXaHAuLh/AAAB lip=127.0.0.1 rip=127.0.0.1 lport=143 rport=47288 resp=<hidden> Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth: Debug: dict( test(a)example.com,127.0.0.1,<i7avXaHAuLh/AAAB>): Performing passdb lookup Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth-worker(19774): Debug: Loading modules from directory: /usr/lib64/dovecot/auth Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth-worker(19774): Debug: Module loaded: /usr/lib64/dovecot/auth/lib20_auth_var_expand_crypt.so Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth-worker(19774): Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_sqlite.so Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth-worker(19774): Debug: conn unix:auth-worker (pid=19773,uid=97): Server accepted connection (fd=13) Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth-worker(19774): Debug: conn unix:auth-worker (pid=19773,uid=97): Sending version handshake Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth-worker(19774): Debug: conn unix:auth-worker (pid=19773,uid=97): auth-worker<1>: Handling PASSV request Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth-worker(19774): Debug: dict(test(a)example.com,127.0.0.1,<i7avXaHAuLh/AAAB>): Performing passdb lookup Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth-worker(19774): Debug: dict(test(a)example.com,127.0.0.1,<i7avXaHAuLh/AAAB>): Lookup: shared/passdb/test(a)example.com/test = {"userdb_email":"test(a)example.com ","userdb_quota_rule":"*:bytes=1073741824","password":"{SSHA256.b64}SF5 hEeUZVO4ydasqNb040KHWGyin791L40BYR8cXf+I0EGeetzq5Cg==","userdb_password ":"test","userdb_home":" /var/vmail/test=40example.com(a)ciphermail.private","user":" test=40example.com(a)ciphermail.private"} Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth-worker(19774): Debug: dict(test(a)example.com,127.0.0.1,<i7avXaHAuLh/AAAB>): username changed test(a)example.com -> test=40example.com(a)ciphermail.private Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth-worker(19774): Debug: dict(test=40example.com(a)ciphermail.private,127.0.0.1,<i7avXaHAuL h/AAAB>): Finished passdb lookup Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth-worker(19774): Debug: conn unix:auth-worker (pid=19773,uid=97): auth-worker<1>: Finished Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth: Debug: dict( test(a)example.com,127.0.0.1,<i7avXaHAuLh/AAAB>): username changed test(a)example.com -> test=40example.com(a)ciphermail.private Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth: Debug: dict( test=40example.com(a)ciphermail.private,127.0.0.1,<i7avXaHAuLh/AAAB>): Finished passdb lookup Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth: Debug: auth( test=40example.com(a)ciphermail.private,127.0.0.1,<i7avXaHAuLh/AAAB>): Auth request finished Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth: Debug: client passdb out: OK 1 user=test=40example.com(a)ciphermail.private original_user=test(a)example.com Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth: Debug: master in: REQUEST 3373400065 19771 1 603cbf25103fc9a6 77ceabe45f077e40 session_pid=19776 request_auth_token Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth: Debug: prefetch(test=40example.com(a)ciphermail.private,127.0.0.1,<i7avXaHAuLh/A AAB>): Performing userdb lookup Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth: Debug: prefetch(test=40example.com(a)ciphermail.private,127.0.0.1,<i7avXaHAuLh/A AAB>): success Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth: Debug: prefetch(test=40example.com(a)ciphermail.private,127.0.0.1,<i7avXaHAuLh/A AAB>): Finished userdb lookup Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: auth: Debug: master userdb out: USER 3373400065 test=40example.com(a)ciphermail.private email=test(a)example.com quota_rule=*:bytes=1073741824 password=<hidden> home=/var/vmail/test=40example.com(a)ciphermail.private auth_mech= PLAIN auth_token=819d2ad4117e4e4139991fab046e13304880e935 auth_user=test(a)example.com Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap-login: Login: user=<test=40example.com(a)ciphermail.private>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=19776, secured, session=<i7avXaHAuLh/AAAB> Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap( test=40example.com(a)ciphermail.private)<19776><i7avXaHAuLh/AAAB>: Debug: Loading modules from directory: /usr/lib64/dovecot Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap( test=40example.com(a)ciphermail.private)<19776><i7avXaHAuLh/AAAB>: Debug: Module loaded: /usr/lib64/dovecot/lib10_mail_filter_plugin.so Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap( test=40example.com(a)ciphermail.private)<19776><i7avXaHAuLh/AAAB>: Debug: Module loaded: /usr/lib64/dovecot/lib10_quota_plugin.so Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap( test=40example.com(a)ciphermail.private)<19776><i7avXaHAuLh/AAAB>: Debug: Module loaded: /usr/lib64/dovecot/lib11_imap_quota_plugin.so Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap( test=40example.com(a)ciphermail.private)<19776><i7avXaHAuLh/AAAB>: Debug: Added userdb setting: plugin/auth_mech=PLAIN Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap( test=40example.com(a)ciphermail.private)<19776><i7avXaHAuLh/AAAB>: Debug: Added userdb setting: plugin/email=test(a)example.com Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap( test=40example.com(a)ciphermail.private)<19776><i7avXaHAuLh/AAAB>: Debug: Added userdb setting: plugin/password=<hidden> Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap( test=40example.com(a)ciphermail.private)<19776><i7avXaHAuLh/AAAB>: Debug: Added userdb setting: plugin/quota_rule=*:bytes=1073741824 Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap( test=40example.com(a)ciphermail.private)<19776><i7avXaHAuLh/AAAB>: Debug: Effective uid=986, gid=983, home=/var/vmail/test=40example.com(a)ciphermail.private Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap( test=40example.com(a)ciphermail.private)<19776><i7avXaHAuLh/AAAB>: Debug: mail_filter: Filtering mail_filter via socket /var/run/dovecot/mail- filter Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap( test=40example.com(a)ciphermail.private)<19776><i7avXaHAuLh/AAAB>: Debug: mail_filter: Filtering mail_filter_out via socket /var/run/dovecot/mail-filter-out Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap( test=40example.com(a)ciphermail.private)<19776><i7avXaHAuLh/AAAB>: Debug: Quota root: name=User quota backend=maildir args= Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap( test=40example.com(a)ciphermail.private)<19776><i7avXaHAuLh/AAAB>: Debug: Quota rule: root=User quota mailbox=* bytes=1073741824 messages=0 Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap( test=40example.com(a)ciphermail.private)<19776><i7avXaHAuLh/AAAB>: Debug: Quota rule: root=User quota mailbox=Trash bytes=+107374182 (10%) messages=0 Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap( test=40example.com(a)ciphermail.private)<19776><i7avXaHAuLh/AAAB>: Debug: Quota grace: root=User quota bytes=107374182 (10%) Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap( test=40example.com(a)ciphermail.private)<19776><i7avXaHAuLh/AAAB>: Debug: maildir++: root=/var/vmail/test=40example.com(a)ciphermail.private, index=, indexpvt=, control=, inbox=/var/vmail/test=40example.com(a)ciphermail.private, alt= Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap( test=40example.com(a)ciphermail.private)<19776><i7avXaHAuLh/AAAB>: Debug: quota: quota_over_flag check: quota_over_script unset - skipping Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap( test=40example.com(a)ciphermail.private)<19776><i7avXaHAuLh/AAAB>: Debug: Mailbox Drafts: Mailbox opened because: APPEND Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap( test=40example.com(a)ciphermail.private)<19776><i7avXaHAuLh/AAAB>: Panic: file ostream.c: line 201 (o_stream_flush): assertion failed: (stream- >stream_errno != 0) Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap( test=40example.com(a)ciphermail.private)<19776><i7avXaHAuLh/AAAB>: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xf895b) [0x7f8f1d3d995b] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf89f7) [0x7f8f1d3d99f7] -> /usr/lib64/dovecot/libdovecot.so.0(+0x55b05) [0x7f8f1d336b05] -> /usr/lib64/dovecot/libdovecot.so.0(+0x5a1bd) [0x7f8f1d33b1bd] -> /usr/lib64/dovecot/libdovecot- storage.so.0(maildir_save_finish+0x99) [0x7f8f1d723fa9] -> /usr/lib64/dovecot/lib10_quota_plugin.so(+0xfcee) [0x7f8f1bd5acee] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_save_finish+0x7d) [0x7f8f1d6fafdd] -> dovecot/imap(+0x132fd) [0x564a032332fd] -> dovecot/imap(command_exec+0x78) [0x564a03241cd8] -> dovecot/imap(+0x128ad) [0x564a032328ad] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x73) [0x7f8f1d3f10c3] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x135) [0x7f8f1d3f2775] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) [0x7f8f1d3f1170] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x48) [0x7f8f1d3f12d8] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x17) [0x7f8f1d368eb7] -> dovecot/imap(main+0x335) [0x564a03232445] -> /lib64/libc.so.6(__libc_start_main+0xf3) [0x7f8f1ca5b803] -> dovecot/imap(_start+0x2e) [0x564a032325fe] Apr 23 10:36:17 ciphermail-webmail dovecot[18682]: imap(test=40example.com(a)ciphermail.private)<19776><i7avXaHAuLh/AAAB>: Fatal: master: service(imap): child 19776 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set /proc/sys/fs/suid_dumpable to 2)

1 1

Why was mail-filter plugin removed in version 2.3.14?
by Martijn Brinkers (list) 23 Apr '21

23 Apr '21

Hi, Mail-filter plugin was removed in version 2.3.14. Any idea why was this removed? Is there a replacement for the mail-filter plugin? Kind regards, Martijn Brinkers

1 0

Size of transaction log file is increasing continuously if dsync is failed
by Duc Anh Do 22 Apr '21

22 Apr '21

Hi Dovecot community, I would like to share a problem I saw a few days ago. Any comment is highly appreciated. *Steps to reproduce* 0. Version of Dovecot I use is v2.3.11.3. 1. Prepare 2 Dovecot backends: - One backend is used as the source of dsync command. Other backend is used as the destination of the dsync command. - Mailbox format is Maildir. Mail dir of two test accounts is empty. 2. Prepare the test account in the source of dsync: - Send a test message to the test account. For example, I use swaks: swaks --server 127.0.0.1 --port 24 --protocol LMTP --to user1@local - Use doveadm expunge command to clean mail dir of the test account: doveadm expunge -u user1@local mailbox INBOX all 3. Prepare the test account in the destination of dsync: - Log in test account via IMAP then select INBOX first: telnet 127.0.0.1 imap ... s login user1@local 1 ... s select INBOX ... s logout - Then perform dsync: doveadm -o imapc_host=backend2.local -o imapc_port=143 -o imapc_user=user1@local -o imapc_password=1 backup -s '' -R -u user1@local imapc: - Confirm error occurs when using dsync: dsync(user1@local): Info: imapc(backend2.local:143): Connected to 192.168.100.2:143 (local 192.168.100.27:58850) dsync(user1@local): Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted. AQAAAHm4+Jk= 4. Log in the test account in dsync destination then select INBOX. Repeat many times. I can see the size of the transaction log file is increasing continuously. *Before*: -rw-------. 1 vmail vmail 456 Apr 22 10:54 dovecot.index.log *After*: -rw-------. 1 vmail vmail 544 Apr 22 10:59 dovecot.index.log -rw-------. 1 vmail vmail 632 Apr 22 11:00 dovecot.index.log -rw-------. 1 vmail vmail 720 Apr 22 11:00 dovecot.index.log *Problems* - Size of the transaction log file is increasing continuously. Do you think this is an issue of Dovecot? - The value of *mail_index_log_rotate_max_size* is 1M by default. However the transaction log file dovecot.index.log is not rotated when its size exceeds limit. - Because the size of the transaction log file is too big and it is not rotated, I think "out of memory" error will occur when I try to use IMAP SELECT or POP3 STAT command (if the virtual size limit is small enough). - If "size of the transaction log file is increasing continuously" is an issue, what should I do to avoid it or is there any workaround? I understand I should fix the error *Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted* first before doing anything next. I think removing the transaction log file is an understandable workaround. *Investigaton* - About the error *Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted*, I can understand the cause after reading this thread https://dovecot.org/pipermail/dovecot/2014-April/095588.html 2) Maildir + INBOX + backup/sync/replicate > In the test scenarios where the INBOX on one side was to be completely > removed, e.g. doveadm backup -R the dsync failed and > nothing was synced to the target. This is because before moving the source > mails to the mailbox, dsync cleans out the old ones ( > -R preserves nothing) and in Maildir the INBOX can not be removed. This is > a feature/not easily solvable, because in Maildir > INBOX is different from other folders. > - The transaction log file is rotated whenever there's any change in index file. I can confirm by sending a test message to the test account in dsync destination. I can see that logic in *src/lib-index/mail-index-sync.c* and *src/lib-index/mail-index-write.c*. After that, the size of the new transaction log file is not increasing anymore. - When the error *Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted* occurred, I tried to dump the transaction log file and I saw these records: record: offset=432, type=index-deleted (ext), size=12 record: offset=444, type=index-undeleted (ext), size=12 - Do you think these records relate to the issue that the size of the transaction log file is increasing continuously? - Did the error *Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted* make content of transaction log file incomplete/incorrect? Regards, Anh Do

1 0