- dovecot - dovecot.org

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