- dovecot - dovecot.org

Panic/Fatal error in lmtp when quota is full
by Alessio Cecchi 14 Sep '21

14 Sep '21

Hi, on dovecot 2.3.16 with delivery via LMTP I found many of this error when a user have the mailbox full and personal sieve rules: - lmtp.log: Sep 14 09:58:27 pop05 dovecot: lmtp(user1(a)company.com) session=<eAjRDSNWQGFCaQAAP27dBg>: sieve: deliverytime=122, msgid=<000601d7a8f8$fc350d50$f49f27f0$(a)company.com>, sender=user2(a)company.com, from=user2(a)company.com, subject="my subject 1": fileinto action: failed to store into mailbox 'INBOX/Personale': Quota exceeded (mailbox for user is full) Sep 14 09:58:27 pop05 dovecot: lmtp(user1(a)company.com) session=<eAjRDSNWQGFCaQAAP27dBg>: sieve: deliverytime=122, msgid=<000601d7a8f8$fc350d50$f49f27f0$(a)company.com>, sender=user2(a)company.com, from=user2(a)company.com, subject="my subject 1": failed to store into mailbox 'INBOX': Quota exceeded (mailbox for user is full) Sep 14 09:58:27 pop05 dovecot: lmtp(user1(a)company.com) session=<eAjRDSNWQGFCaQAAP27dBg>: sieve: Execution of script /home/vmail/domains/company.com/user1/.dovecot.sieve failed with unsuccessful implicit keep (user logfile /home/vmail/domains/company.com/user1/.dovecot.sieve.log may reveal additional details) Sep 14 09:58:27 pop05 dovecot: lmtp(26946): Panic: file mail-user.c: line 229 (mail_user_deinit): assertion failed: ((*user)->refcount == 1) Sep 14 09:58:27 pop05 dovecot: lmtp(26946): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7f52dfb4e632] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f52dfb4e73e] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf66fe) [0x7f52dfb5c6fe] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf67a1) [0x7f52dfb5c7a1] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [ 0x7f52dfaaba18] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x57567) [0x7f52dfe79567] -> dovecot/lmtp [10.0.2.26 DATA](lmtp_local_data+0x4dc) [0x55e09f333e2c] -> dovecot/lmtp [10.0.2.26 DATA](client_default_cmd_data+0x18b) [0x55e09f33273b] -> dovecot/lmtp [10.0.2.26 DATA](cmd_data_continue+0x204) [0x55e09f3324d4] -> /usr/lib64/dovecot/libdovecot.so.0(+0x5fe64) [0x7f52dfac5e64] -> /usr/li b64/dovecot/libdovecot.so.0(io_loop_call_io+0x65) [0x7f52dfb74ad5] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x12b) [0x7f52dfb7649b] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x59) [0x7f52dfb74bd9] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f52dfb74e18] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f52dfadddf3] -> dovecot/lmtp [10.0.2.26 DATA](main+0x20b) [0x55e09f330f0b] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f52df6ba555] -> dovecot/lmtp [10.0.2.26 DATA](+0x6041) [0x55e09f331041] Sep 14 09:58:27 pop05 dovecot: lmtp(26946): Fatal: master: service(lmtp): child 26946 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) - sieve.log: sieve: info: started log at 2021-09-14 10:25:54 +0200. error: deliverytime=8, msgid=<49ef01d7a942$2168a200$6439e600$(a)company.com>, sender=sender1(a)company.com, from=sender1(a)company.com, subject="I: Undelivered Mail Returned to Sender": fileinto action: failed to store into mailbox 'INBOX/Comunicazioni': Quota exceeded (mailbox for user is full). error: deliverytime=9, msgid=<49ef01d7a942$2168a200$6439e600$(a)company.com>, sender=sender1(a)company.com, from=sender1(a)company.com, subject="I: Undelivered Mail Returned to Sender": failed to store into mailbox 'INBOX': Quota exceeded (mailbox for user is full). Hope it can be fixed, Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

2 1

Password Schemes
by John Schmerold 14 Sep '21

14 Sep '21

My /etc/dovecot/conf.d/auth-passwdfile.conf.ext is configured to use MD5 passdb { driver = passwd-file args = scheme=MD5 username_format=%n /etc/exim4/domains/%d/passwd } userdb { driver = passwd-file args = username_format=%n /etc/exim4/domains/%d/passwd } /home/account/conf/mail/domain.com/passwd has a mixture of MD5 & SHA512-CRYPT: scanner:{MD5}$1$M5QuU7QI$AE7Nnorb8KC5KMvyYfVcr0:account:mail::/home/account:0:userdb_quota_rule=*:storage=0M test:{SHA512-CRYPT}$6$towo0IVjzBgZ0htU$uTFbyJ3aPunrhsEEC2alHz6SEuPyBdL3JYDWc6Z0ZtA2cMFjFVJNqAwn04OKQfsu99DNcDGu21zkvdYbsPmgJ0:account:mail::/home/account:0:userdb_quota_rule=*:storage=0M Everything is working fine, is this by design? In other words does the {MD5} vs {SHA512-CRYPT} in passwd over-rule auth-passwdfile.conf.ext ? -- John Schmerold Katy Computer Systems, Inc https://katycomputer.com St Louis

3 2

Re: Storing Last Login Plugin value in SQL
by dovecot＠ptld.com 14 Sep '21

14 Sep '21

> Assuming you use MariaDB / MySQL, you create this trigger in the > database. > Assuming your int/bigint/varchar column is lastlogin and the table name > is mailacct, > the trigger will update the datetime `logindate` column whenever the > table is updated, > by whatever existing queries you have. This is your recourse when you > can't get your > queries to do the right thing in the first place. Thank you for the solution of using sql triggers. I was able to get it working that way. I hope it doesn't add too much overhead as it feels like a band-aid and duct-tape fix.

2 1

submission server fails to relay messages
by Шварц Сергей Владимирович 13 Sep '21

13 Sep '21

Hi guys! I'm using dovecot submission server for clients to send emails and relay them to postfix. Everything works fine unless a client tries to send large (40Mbs) messages. No big deal one can say just set "message_size_limit = 314572800" in postfix and it should just work, but no, it does not, client gets "552 5.2.3 Message size exceeds administrative limit.". I've increased verbosity for smtpd process and get this logs for a failed attempt Sep 12 13:43:21 mx10 postfix/smtpd[73602]: connection established > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: master_notify: status 0 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: name_mask: resource > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: name_mask: software > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: watchdog_start: 0x563f80b341b0 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_loop: time left 5 for > 0x7fdef6cf4700 0x563f80b393d0 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_loop: time left 5 for > 0x7fdef6cf4700 0x563f80b1ee10 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_loop: time left 100 for > 0x7fdef6d56b20 0x0 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_loop: time left 1000 for > 0x7fdef6cf4720 0x563f80b1ee10 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_loop: time left 1000 for > 0x7fdef6cf4720 0x563f80b393d0 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_loop: select_delay 0 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_loop: timer > 0x7fdef6cf4700 0x563f80b393d0 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: rewrite stream disconnect > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_disable_readwrite: fd 20 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_cancel_timer: > 0x7fdef6cf4700 0x563f80b393d0 -1 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_cancel_timer: > 0x7fdef6cf4720 0x563f80b393d0 985 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_loop: timer > 0x7fdef6cf4700 0x563f80b1ee10 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: proxymap stream disconnect > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_disable_readwrite: fd 10 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_cancel_timer: > 0x7fdef6cf4700 0x563f80b1ee10 -1 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_cancel_timer: > 0x7fdef6cf4720 0x563f80b1ee10 985 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: watchdog_stop: 0x563f80b341b0 > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: watchdog_start: 0x563f80b341b0 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: connect from > localhost[127.0.0.1] > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_loop: time left 85 for > 0x7fdef6d56b20 0x0 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: match_list_match: localhost: no > match > Sep 12 13:43:21 mx10 postfix/smtpd[73615]: event_loop: select_delay 85 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: match_list_match: 127.0.0.1: > no match > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: match_list_match: localhost: no > match > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: match_list_match: 127.0.0.1: > no match > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: smtp_stream_setup: maxtime=300 > enable_deadline=0 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: match_hostname: > smtpd_client_event_limit_exceptions: localhost ~? 127.0.0.0/8 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: match_hostaddr: > smtpd_client_event_limit_exceptions: 127.0.0.1 ~? 127.0.0.0/8 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: 220 > mx10 ESMTP Postfix (Debian/GNU) > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: watchdog_pat: 0x5609a03c01b0 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: vstream_fflush_some: fd 10 > flush 47 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: vstream_buf_get_ready: fd 10 > got 21 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: < localhost[127.0.0.1]: EHLO > mx10 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: match_list_match: localhost: no > match > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: match_list_match: 127.0.0.1: > no match > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: 250-mx10 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: > 250-PIPELINING > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: > 250-SIZE 314572800 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: 250-VRFY > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: 250-ETRN > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: > 250-ENHANCEDSTATUSCODES > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: > 250-8BITMIME > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: 250-DSN > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: 250 > CHUNKING > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: watchdog_pat: 0x5609a03c01b0 > Sep 12 13:43:21 mx10 postfix/smtpd[73602]: vstream_fflush_some: fd 10 > flush 138 > Sep 12 13:43:22 mx10 postfix/smtpd[73602]: vstream_buf_get_ready: fd 10 > got 6 > Sep 12 13:43:22 mx10 postfix/smtpd[73602]: < localhost[127.0.0.1]: QUIT > Sep 12 13:43:22 mx10 postfix/smtpd[73602]: > localhost[127.0.0.1]: 221 > 2.0.0 Bye > looks like submission server just quits if I configure imap client /Thunderbird to connect directly to postfix everything works just fine. doveconf -n output is attached just in case

2 1

Storing Last Login Plugin value in SQL
by dovecot＠ptld.com 13 Sep '21

13 Sep '21

The last-login plugin sends a number (epoch seconds) as uint or string in a query to sql. If i create a column type in sql of varchar() the number is saved in the column as a string, but not very useful. I can not figure out how to get that value into a date/time column such as date, datetime or timestamp. All three cause an error of Incorrect datetime value: '1631556506' for column. Anyone have any idea how to get the last-login plugin to update a date/time column in sql?

2 3

Problem with copy e-mails via doveadm
by Christian Küppers 13 Sep '21

13 Sep '21

2 12

Restricting commands used in http api
by Christian Küppers 13 Sep '21

13 Sep '21

Hello, is it possible to restrict api methods (https://doc.dovecot.org/admin_manual/doveadm_http_api/#api-methods) without restricting doveadm usage on console. something like: service doveadm { unix_listener doveadm-server { user = vmail } inet_listener { port = 2425 allowed_commands = ALL } inet_listener http { port = 8080 allowed_commands = fetch, copy, search #ssl = yes # uncomment to enable https } } Reason for question: We want to be able to use all commands as administrators on console but some external software using the dovecot api should not be able to do admin like tasks like "doveadm director flush". our setup: multiple replicated dovecot backend servers frontend with dovecot director ring and proxy enabled (provides api endpoint) 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

1 1

SQL help please (Mysql/MariaDB).
by C. Petro 12 Sep '21

12 Sep '21

I'm trying to build a mail server for a friend using Postfix, Dovecot and Postfixadmin, using Mariadb as the backend for user information and authentication. I've got it *almost* working. (dovecot -n at the bottom because I don't think the problem is in the SQL) I have things up to the point where mail comes in, and where you can get Thunderbird to connect to Dovecot, but delivery is looking at a different directory than IMAP: root@mailserver:/var/mail/vmail# find ./ ./ ./petro(a)republicofmean.com ./petro(a)republicofmean.com/dovecot.index.log ./petro(a)republicofmean.com/dovecot-uidvalidity.6136d995 ./petro(a)republicofmean.com/tmp <...> ./petro(a)republicofmean.com/new ./petro(a)republicofmean.com/subscriptions ./republicofmean.com ./republicofmean.com/petro ./republicofmean.com/petro/tmp ./republicofmean.com/petro/cur ./republicofmean.com/petro/new ./republicofmean.com/petro/new/1630897562.Vfd00Ib40009M307139.mailserver <....> ./republicofmean.com/petro/new/1630899062.Vfd00Ib40011M264001.mailserver ./republicofmean.com/cer ./republicofmean.com/cer/tmp ./republicofmean.com/cer/cur ./republicofmean.com/cer/new ./republicofmean.com/cer/new/1630900562.Vfd00Ib40013M218855.mailserver ./republicofmean.com/cer/new/1630899062.Vfd00Ib40010M259724.mailserver The SQL I think Dovecot is using: root@mailserver:/etc/dovecot# grep -i select dovecot-sql.conf.ext | grep -v "^#" password_query = SELECT username as user, domain, password FROM mailbox WHERE username = '%u' user_query = select CONCAT("/var/mail/vmail/",maildir) as home, 500 as uid, 500 as gid from mailbox where username="%u" Here's what Postfix is using: mysql_virtual_alias_domain_catchall_maps.cf: query = SELECT goto FROM alias,alias_domain WHERE alias_domain.alias_domain = '%d' and alias.address = CONCAT('@', alias_domain.target_domain) AND alias.active = 1 AND alias_domain.active='1' mysql_virtual_alias_domain_mailbox_maps.cf: query = SELECT maildir FROM mailbox,alias_domain WHERE alias_domain.alias_domain = '%d' and mailbox.username = CONCAT('%u', '@', alias_domain.target_domain) AND mailbox.active = 1 AND alias_domain.active='1' mysql_virtual_alias_domain_maps.cf: query = SELECT goto FROM alias,alias_domain WHERE alias_domain.alias_domain = '%d' and alias.address = CONCAT('%u', '@', alias_domain.target_domain) AND alias.active = 1 AND alias_domain.active='1' mysql_virtual_alias_maps.cf: query = SELECT goto FROM alias WHERE address='%s' AND active = '1' mysql_virtual_domains_maps.cf: query = SELECT domain FROM domain WHERE domain='%s' AND active = '1' mysql_virtual_mailbox_limit_maps.cf: query = SELECT quota FROM mailbox WHERE username='%s' AND active = '1' mysql_virtual_mailbox_maps.cf: query = SELECT maildir FROM mailbox WHERE username='%s' AND active = '1' # dovecot -n # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0-81-generic x86_64 Ubuntu 20.04.3 LTS ext4 # Hostname: <redacted> auth_mechanisms = plain login log_path = /var/log/dovecot.log login_greeting = Not your mail server mail_location = maildir:/var/mail/vmail/%u/ mail_max_userip_connections = 50 mail_privileged_group = vmail 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 { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocols = " imap lmtp pop3 submission" service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { unix_listener lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } ssl_cert = </etc/letsencrypt/live/<redacted>/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 { args = /etc/dovecot/dovecot-sql.conf.ext driver =

3 5

Re: Problem with the dovecot-fts-xapian package.
by Bob Marcan 12 Sep '21

12 Sep '21

On Sun, 12 Sep 2021 11:36:46 +0100 Joan Moreau <jom(a)grosjo.net> wrote: > This is where I am for now : > > https://koji.fedoraproject.org/koji/packageinfo?packageID=34417 > > Probably, I should wait for Fedora batch programs to push that into main rep > > On 2021-09-12 11:18, Joan Moreau wrote: > > > Hi Bob, > > > > I am trying to achieve that. > > > > But do you know the process of pushing an update as a maintainer, in > fedore repositories ? > > > > Thank you > > > > On 2021-09-12 11:02, Bob Marcan wrote: > > On Sun, 12 Sep 2021 09:45:35 +0100 > > Joan Moreau <jom(a)grosjo.net> wrote: > > > > Thank you for notice. > > > > What is the process to rebuild the package with recent dovecot, as > (instead of existing 1.4.12-1) ? > > There are no (yet) 1.4.12-2 in updates-testing or > updates-testing-modular repository. > > Should i'll wait for update? > > BR, Bob Got the new version and there is no more API mismatch. It's not so important for me, since i'm retired and i'm running this on my home computer. But i think it needs more support from te dovecot group. There a lot file protection issues nad lack of documentation on dovecot side. BR, Bob

3 2

suse.de dovecot issues
by Bernhard M. Wiedemann 12 Sep '21

12 Sep '21

Hi, I am one of the people taking over our new suse.de email setup (consisting of dovecot+rspamd+postfix) and wanted to report some issues we experience: 1. we use dovecot-director to distribute users between 2 backend servers that share an NFS mount. We found that it proxies lmtp to a different backend than imap of the same user and that caused NFS stale-filehandle errors on the dovecot-uidlist. It then proceeds to re-generate the dovecot-uidlist with new UIDs that creates trouble for users. a) shouldn't dovecot use locks (fcntl or flock) to protect such files from concurrent updates? b) could it generate uidlist in a way that re-generating it, assigns the same UIDs again? E.g. via hash over file content c) how to get dovecot-director to send all traffic for a user to one backend? 2. We have 2 backends so that we can do maintenance on one of them while users can still access their emails through the other backend. However, we found that stopping dovecot on one backend left users unable to access their mails. Maybe this is related to how user auth works? How to get this HA setup right, so that we don't have a single point of failure? grep PRETTY /etc/os-release PRETTY_NAME="SUSE Linux Enterprise Server 15 SP3" rpm -q dovecot23 dovecot23-2.3.15 https://www.zq1.de/~bernhard/temp/dovecot/ has some sysreports. Ciao Bernhard M.

5 12