- dovecot - dovecot.org

Unexpected behavior of doveadm mailbox delete -e -s
by Mar Alegre 13 Dec '20

13 Dec '20

Hello, I have encountered what I believe to be a bug, or at least inaccurate documentation. I am running version 2.3.4.1 of Dovecot (installed via the default repo for Debian 10), so my apologies if this has been fixed in a more recent version. I tried to look for changelogs but was not able to find any. The `doveadm mailbox delete` command accepts flags `-e` and `-s` (among others). The flags are described by both the man pages and the wiki as follows: - `-e`: Require mailboxes to be empty before deleting. - `-s`: Unsubscribe deleted mailboxes. Based on these descriptions, I would expect that when both of these flags are combined, a directory that is not empty would be neither deleted nor unsubscribed. However, I have discovered that when I run the command `doveadm mailbox delete -u $myusername -e -s $non_empty_dir`, the result is that the directory is not deleted, but it *is* unsubscribed. I assume this is a bug, but if it is intended, the documentation should probably be updated to more clearly communicate that the `-s` flag will cause a directory to be unsubscribed even if it is not deleted. Best, Mar Alegre

2 1

fyi: please change /var/run to /run in debian buster repository
by Michael 12 Dec '20

12 Dec '20

hey, just one minor thing: if there's any time left, please change in the repository debian/buster in the package dovecot-core in the file /lib/systemd/system/dovecot.service the line PIDFile=/var/run/dovecot/master.pid to PIDFile=/run/dovecot/master.pid because systemd always shows the following warning: Dec 12 15:46:30 mail systemd[1]: /lib/systemd/system/dovecot.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/dovecot/master.pid → /run/dovecot/master.pid; please update the unit file accordingly. creating a drop-in in /etc/systemd/system/dovecot.service.d/ doesn't do anything. greetings...

2 1

important message
by jk00100033＠gmail.com 11 Dec '20

11 Dec '20

I've invited you to fill out the following form: Untitled form To fill it out, visit: https://docs.google.com/forms/d/e/1FAIpQLSeqI7QUpet4levWQvhvUuqn1Au-fqPDo0W… Greetings! To You Mr. Joe is my name; I work in a Bank here in Benin. And I personally handle transactions of Mr. Martin Quick who eventually died on the 5th of February 2017 from injuries sustained in a road accident that happened 3 years ago. Prior to his death, Mr. Martin Quick lived and worked in Benin Republic and was doing Contracting with Benin Energy dept. He has (Four million, three hundred thousand Euros) in a fixed account with the bank with no other beneficiary. Now I write to seek your consent to present you as an oversea based partner to stand in as next of kin to the late Mr. Martin Quick. Let me know if it is ok to work with you. please email me in my private email for more details ( kukuaj001(a)gmail.com ) please email me in my private email for more details ( kukuaj001(a)gmail.com ) My best Regards Mr. Joe. Google Forms: Create and analyze surveys.

4 3

Potential issue with lmtp_rawlog_dir when using TLS
by John Fawcett 11 Dec '20

11 Dec '20

Hi not sure why this happens, but looks like lmtp_rawlog_dir blocks the successful negotiation of an lmtp starttls connection. Reproducible with openssl s_client. Two runs with only difference the presence of lmtp_rawlog_dir setting in dovecot config. Failed connection with lmtp_rawlog_dir Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Connect from ::1 Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Debug: SSL: where=0x10, ret=1: before SSL initialization Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Debug: SSL: where=0x2001, ret=1: before SSL initialization Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Debug: SSL: where=0x2002, ret=-1: before SSL initialization Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Debug: SSL: where=0x2002, ret=-1: error Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Debug: SSL error: SSL_accept() failed: error:1408F10B:SSL routines:ssl3_get_record:wrong version number Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Error: lmtp-server: conn [::1]:53876 [2]: SSL handshake failed: SSL_accept() failed: error:1408F10B:SSL routines:ssl3_get_record:wrong version number Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Debug: SSL error: SSL_accept() syscall failed: Invalid argument Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Disconnect from ::1: SSL Initialization failed (state=READY) Successful connection without lmtp_rawlog_dir Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Connect from ::1 Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x10, ret=1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL_get_servername() failed Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read client hello Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server hello Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write change cipher spec Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: TLSv1.3 write encrypted extensions Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write certificate Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: TLSv1.3 write server certificate verify Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write finished Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read finished Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x20, ret=1: SSLv3/TLS write session ticket Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write session ticket Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write session ticket Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully John

1 0

Dovecot 2.3.11.3 LMTP dropping connection after first part of multipart message received
by Steve Akerman 11 Dec '20

11 Dec '20

Good afternoon I have been using Dovecot with great success for several months now with one problem: I have received several messages (3 to date out of a much larger number) which cause Dovecot LMTP to drop the connection with sendmail after only receiving the first part of the message. Dovecot saves the first part to INBOX, and then drops the link with sendmail as it sees the rest of the data from sendmail as new (and invalid) commands Sendmail sees the delivery as unsuccessful and requeues the message, so the cycle continues until i kill the queue These messages are all Multipart MIME I have attached an extract from the log which shows the above sequence Finally, I have kept one such message from the sendmail queue (df and qf) should this be useful, but prefer not to post here as not sanitised Any help in correcting my configuration would be appreciated. Thanks Steve MAIL LOG extract ------------------------- Dec 9 12:00:10 phone dovecot[179]: lmtp(20774): Connect from local Dec 9 12:00:10 phone sm-mta-rx[20764]: STARTTLS=client, relay=localhost, version=TLSv1.3, verify=OK, cipher=TLS_AES_256_GCM_SHA384, bits=256/256 Dec 9 12:00:10 phone dovecot[179]: lmtp(20775): Connect from local Dec 9 12:00:10 phone sm-mta-rx[20763]: STARTTLS=client, relay=localhost, version=TLSv1.3, verify=OK, cipher=TLS_AES_256_GCM_SHA384, bits=256/256 Dec 9 12:00:10 phone dovecot[179]: lmtp(*********)<20775><8EieKDqu0F8nUQAA0J78UA>: msgid=<39113a86-fdbb-4cea-b1c3-d225dff93328(a)info.ameli.fr <mailto:39113a86-fdbb-4cea-b1c3-d225dff93328@info.ameli.fr>>: saved mail to INBOX Dec 9 12:00:10 phone dovecot[179]: lmtp(20775): Disconnect from local: Too many invalid commands. (state=READY) Dec 9 12:00:10 phone sm-mta-rx[20763]: STARTTLS: write error=syscall error (-1), errno=32, get_error=error:00000000:lib(0):func(0):reason(0), retry=1, ssl_err=5 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: SYSERR(root): timeout writing message to localhost: Broken pipe Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 0: fl=0x0, mode=20666: CHR: dev=30/1306024, ino=301, nlink=1, u/gid=0/0, size=0 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 1: fl=0x1, mode=20666: CHR: dev=30/1306024, ino=301, nlink=1, u/gid=0/0, size=0 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 2: fl=0x1, mode=20666: CHR: dev=30/1306024, ino=301, nlink=1, u/gid=0/0, size=0 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 3: fl=0x4002, mode=100600: dev=1/2, ino=26089780, nlink=1, u/gid=0/23, size=2041 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 4: fl=0x0, mode=20666: CHR: dev=30/1306024, ino=575, nlink=1, u/gid=0/0, size=0 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 5: fl=0x2, mode=140666: SOCK localhost->[[UNIX: /var/run/mDNSResponder]] Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 6: fl=0x0, mode=100640: dev=1/2, ino=25887976, nlink=1, u/gid=0/23, size=12288 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 7: fl=0x0, mode=100640: dev=1/2, ino=25887976, nlink=1, u/gid=0/23, size=12288 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 8: fl=0x0, mode=100600: dev=1/2, ino=26088246, nlink=1, u/gid=0/23, size=58024 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 9: fl=0x6, mode=140444: SOCK localhost->(Invalid argument) Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 10: fl=0x6, mode=140444: SOCK localhost->(Invalid argument) Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 11: fl=0x0, mode=100640: dev=1/2, ino=25768590, nlink=1, u/gid=0/23, size=12288 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: 12: fl=0x0, mode=100640: dev=1/2, ino=25768590, nlink=1, u/gid=0/23, size=12288 Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: MCI@0x0: NULL Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: MCI@0x7fae2c814818: flags=26404c<CACHED,ESMTP,8BITMIME,INMIME,ENHSTAT,PIPELINED,TLSACT>, errno=32, herrno=0, exitstat=75, state=8, pid=0, maxsize=0, phase=client DATA 354, mailer=dovecot, status=4.4.2, rstatus=(null), host=localhost, lastuse=Wed Dec 9 12:00:10 2020\n Dec 9 12:00:10 phone sm-mta-rx[20763]: 0B89mOON016803: to=<s****************>, delay=1+01:11:31, xdelay=00:00:00, mailer=dovecot, pri=4787366, relay=localhost, dsn=4.4.2, reply=75, stat=Deferred ######################*****############## ### DOVECOT Mailer specification ### ##################*****################## Mdovecot, P=[IPC], F=zDFMPhnul59, S=EnvFromSMTP/HdrFromSMTP, R=EnvToSMTP/HdrFromSMTP, T=DNS/RFC822/X-Unix, A=FILE /var/run/dovecot/lmtp dovecot -n ————— # 2.3.11.3 (502c39af9): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.11 (d71e0372) doveconf: Warning: service auth { client_limit=100 } is lower than required under max. load (300) doveconf: Warning: service anvil { client_limit=100 } is lower than required under max. load (203) # OS: Darwin 15.6.0 x86_64 # Hostname: *************** doveconf: Error: t_readlink(/var/run/dovecot//dovecot.conf) failed: readlink() failed: Permission denied auth_mechanisms = cram-md5 auth_username_format = %Ln base_dir = /var/run/dovecot/ default_client_limit = 100 default_internal_group = _dovecot default_internal_user = _dovecot default_login_user = _dovenull hostname =***************** lda_mailbox_autocreate = yes mail_gid = 530 mail_home = /var/mail/%d/%n mail_location = sdbox:~/dbox mail_uid = 530 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 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 = scheme=SSHA256 username_format=%u /usr/local/etc/dovecot/users driver = passwd-file } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } postmaster_address = postmaster protocols = imap lmtp service auth { unix_listener auth-userdb { group = mailusers mode = 0777 user = _dovecot }

2 2

Disconnected: Inactivity (auth failed, 2 attempts in 180 secs)
by basti 11 Dec '20

11 Dec '20

Hello, I have a problem with "apple mail". Once it work as expected, then it does not answer. Dez 10 00:16:04 vsrv10563 dovecot[17121]: imap-login: Login: user=<info(a)example.com>, method=PLAIN, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, mpid=4490, TLS, session=<Oit4OxC2CTZNFv7P> Dez 10 00:17:38 vsrv10563 dovecot[17121]: imap-login: Login: user=<info(a)example.com>, method=PLAIN, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, mpid=5174, TLS, session=<IhlpQhC2XjZNFv7P> Dez 10 00:18:14 vsrv10563 dovecot[17121]: imap-login: Disconnected: Inactivity (auth failed, 2 attempts in 180 secs): user=<user(a)example.com>, method=CRAM-MD5, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, TLS, session=<tkVXOxC2DDZNFv7P> Dez 10 00:18:14 vsrv10563 dovecot[17121]: imap-login: Disconnected: Inactivity during authentication (auth failed, 2 attempts in 179 secs): user=<info(a)example.com>, method=CRAM-MD5, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, TLS, session=<pHVeOxC2HzZNFv7P> Dez 10 00:18:14 vsrv10563 dovecot[17121]: imap-login: Disconnected: Inactivity (auth failed, 2 attempts in 180 secs): user=<test(a)example.com>, method=CRAM-MD5, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, TLS, session=<J6ZXOxC2OTZNFv7P> Dez 10 00:18:14 vsrv10563 dovecot[17121]: imap-login: Disconnected: Inactivity (auth failed, 2 attempts in 180 secs): user=<user(a)example.com>, method=CRAM-MD5, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, TLS, session=<oUFXOxC2ATZNFv7P> Dez 10 04:00:22 vsrv10563 dovecot[17121]: imap-login: Login: user=<test(a)example.com>, method=PLAIN, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, mpid=24532, TLS, session=<QYSEXxO2DzZNFv7P> Dez 10 04:03:06 vsrv10563 dovecot[17121]: imap-login: Disconnected: Inactivity during authentication (auth failed, 2 attempts in 180 secs): user=<info(a)example.com>, method=CRAM-MD5, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, TLS, session=<fo2FXxO2BDZNFv7P> Dez 10 04:03:07 vsrv10563 dovecot[17121]: imap-login: Disconnected: Inactivity during authentication (auth failed, 2 attempts in 180 secs): user=<user(a)example.com>, method=CRAM-MD5, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, TLS, session=<ekWNXxO2VTZNFv7P> Dez 10 04:03:09 vsrv10563 dovecot[17121]: imap-login: Disconnected: Inactivity during authentication (auth failed, 2 attempts in 180 secs): user=<user(a)example.com>, method=CRAM-MD5, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, TLS, session=<YE6sXxO2HTZNFv7P> Then fail2ban block the IP. Has anybody similar problems? This there a way to fix this? Thunderbird does not have this problem. Best Regards,

1 0

Standalone Directors
by William Edwards 11 Dec '20

11 Dec '20

Situation: We will be switching to Dovecot proxy + Director with three email clusters - each cluster will host different email domains and users - with CephFS storage. Problem: A Director instance has one 'director_mail_servers' setting, meaning I could only use one set of email servers, while the set of email servers in the cluster depends on the client's domain. (The reason I use Dovecot proxy is so people can use the same IMAP/POP/SMTP hostnames; regardless of which email server / email cluster they're hosted on.) Question: Is it possible to set 'director_mail_servers' based on the client's email domain? Met vriendelijke groeten, William Edwards

2 2

problems after upgrade from 2.2.27 to 2.3.4.1
by Lampa 09 Dec '20

09 Dec '20

Hello, after debian version from 9 to, also dovecot was upgraded. There was problems with right imap and imap-login connection settings. I adjusted process_limit, service count increased /proc/sys/net/core/somaxconn from 128 to 1024 for imap It's a system with 1000+ imap and 200+ pop3 connections. When imap connections are over 1000 problems begins. Problem one: 2020-12-07T12:46:39.575586+01:00 vhermes dovecot: master: Error: service(pop3): Initial status notification not received in 30 seconds, killing the process 2020-12-07T12:46:39.576448+01:00 vhermes dovecot: pop3: Fatal: master: service(pop3): child 13975 killed with signal 9 2020-12-07T12:46:42.015726+01:00 vhermes dovecot: master: Error: service(lmtp): Initial status notification not received in 30 seconds, killing the process 2020-12-07T12:46:42.016680+01:00 vhermes dovecot: lmtp: Fatal: master: service(lmtp): child 13985 killed with signal 9 2020-12-07T12:46:42.061963+01:00 vhermes dovecot: master: Error: service(lmtp): Initial status notification not received in 30 seconds, killing the process 2020-12-07T12:46:42.062973+01:00 vhermes dovecot: lmtp: Fatal: master: service(lmtp): child 13987 killed with signal 9 problem two: 2020-12-07T13:55:43.106017+01:00 vhermes dovecot: pop3: Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Resource temporarily unavailable 2020-12-07T13:56:22.300893+01:00 vhermes dovecot: lmtp: Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Resource temporarily unavailable 2020-12-07T13:58:11.721892+01:00 vhermes dovecot: imap: Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Resource temporarily unavailable problem three - lot of 2020-12-07T10:16:24.773347+01:00 vhermes dovecot: imap-login: Error: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable problem four - crashing 020-12-09T07:53:26.914331+01:00 vhermes dovecot: imap(user@domain)<5426><cv8ehAK2npZX7MQb>: Panic: file message-parser.c: line 174 (message_part_finish): assertion failed: (ctx->nested_parts_count > 0) 2020-12-09T07:53:26.916771+01:00 vhermes dovecot: imap(user@domain)<5426><cv8ehAK2npZX7MQb>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xdb62b) [0x7f31bb0d462b] -> /usr/lib/dovecot/libdovecot.so.0(+0xdb6c1) [0x7f31bb0d46c1] -> /usr/lib/dovecot/libdovecot.so.0(+0x4a149) [0x7f31bb043149] -> /usr/lib/dovecot/libdovecot.so.0(+0x474ac) [0x7f31bb0404ac] -> /usr/lib/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x104) [0x7f31bb0bc844] -> /usr/lib/dovecot/libdovecot.so.0(message_search_msg+0xa8) [0x7f31bb0bedf8] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xcf89e) [0x7f31bb25789e] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_search_args_foreach+0x45) [0x7f31bb1d9445] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xd0774) [0x7f31bb258774] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xd1a68) [0x7f31bb259a68] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x61) [0x7f31bb25a0e1] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x28) [0x7f31bb1e2e58] -> dovecot/imap [user@domain 1.2.3.4 UID SORT](+0x2691f) [0x559347dc891f] -> dovecot/imap [user@domain 1.2.3.4 UID SORT](command_exec+0x70) [0x559347dc1d80] -> dovecot/imap [user@domain 1.2.3.4 UID SORT](+0x25ed2) [0x559347dc7ed2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0x111) [0x7f31bb0ea8f1] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd0) [0x7f31bb0ec070] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7f31bb0eab7c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7f31bb0eace0] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f31bb06b0d3] -> dovecot/imap [user@domain 1.2.3.4 UID SORT](main+0x325) [0x559347db2bf5] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f31bae5609b] -> dovecot/imap [user@domain 1.2.3.4 UID SORT](_start+0x2a) [0x559347db2d8a] 2020-12-09T07:53:26.917634+01:00 vhermes dovecot: imap(user@domain)<5426><cv8ehAK2npZX7MQb>: Fatal: master: service(imap): child 5426 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) Seems that last problem is solved (if same) https://github.com/dovecot/core/commit/a668d767a710ca18ab6e7177d8e8be22a6b0… Thank you for any help -- Lampa

2 2

Question about login_log_format_elements in a proxy environment
by Adi Pircalabu 08 Dec '20

08 Dec '20

Hi, I have a Dovecot proxy setup with several proxy machines (currently running 2.3.11.3) in front of the real Dovecot servers (2.3.10.1) storing the mailboxes. "doveconf -a | egrep lip" returns: login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> In the real server maillog I'm expecting to have "lip" replaced with the IP address of the proxy. It works as expected for imap-login processes, however for pop3-login processes I still see the real server IP instead of the proxy IP. Ideas? Regards, -- Adi Pircalabu

2 8

Fts solr add fields message-id, date, in-reply-to
by michael1970 07 Dec '20

07 Dec '20

Hi, how can I add fields message-id, date, in-reply-to to fts solr index like hdr,body,subject or to? Thanks, Michael -- Sent from: http://dovecot.2317879.n4.nabble.com/

3 6