- dovecot - dovecot.org

Connection closed (user disabled)
by Roberto J. Bolivar Plenge 28 Aug '24

28 Aug '24

Hello everyone Thank you in advance for your help. Why do I get the following error: Aug 23 10:37:51 cp-cl02 dovecot[2337577]: pop3-login: Disconnected: Connection closed (user disabled): user=<loliva(a)romaseguro.pe>, method=PLAIN, rip=x.x.x.x, lip=x.x.x.x, TLS: Connection closed, session=<8na4jlsg3HK1Q1LE>. I never observed this before: Connection closed (user disabled): I wish to know what is causing it and how can I fix it. Thank you.

2 4

Dovecot with LDAP and Solr: Force Solr user key
by Michele Giacomoli 27 Aug '24

27 Aug '24

Good morning everyone. I am configuring dovecot with ldap and solr as fts plugins. The LDAP configuration works correctly and users can log in both via the userPrincipalName attribute and via mail. In this configuration the LDAP realm and the email domain differ, and on the server the LDAP realm domain is privileged. This means that the mail dir is located in ./ldap_realm/username and in the same way postfix delivers the emails to dovecot using username@ldap_realm as envelope recipient. Consequently the emails are indexed on solr using "username@ldap_realm" as user key. However if I log in in imap using the email address as username and try to do some searches dovecot sends a select to solr using the email address as key and not the ldap user, and consequently I do not get any results from the search. So my question is: is it possible to configure dovecot to force queries to solr so that "username@ldap_realm" is always used as the key even when logging in via email? Dovecot version is: 2.3.7.2 Solr version: 7.2.1 Ldap configuration: [...] user_filter = (&(|(userPrincipalName=%u)(mail=%u))(objectClass=person)(!(userAccountControl=514))(memberOf=cn=Mail,ou=Groups,dc=example,dc=org)) pass_filter = (&(|(userPrincipalName=%u)(mail=%u))(objectClass=person)(!(userAccountControl=514))(memberOf=cn=Mail,ou=Groups,dc=example,dc=org)) pass_attrs = userPassword=password user_attrs = =home=/data/mail/%Ld/%Ln/Maildir/,=mail=maildir:/data/mail/%Ld/%Ln/Maildir/ Solr configuration: plugin { fts = solr fts_solr = url=http://solr_host:8983/solr/dovecot/ fts_autoindex=yes } Best regards -- Logo Mynet *Michele Giacomoli* Reparto IT 32.000 km di fibra ottica nel nord Italia al servizio delle aziende *www.mynet.it* <https://www.mynet.it/> - *www.vogliadifibra.it* <https://www.vogliadifibra.it/>

1 1

2.3.21(.1) build error on aarch64 (using slackware ARM -current)
by shawn.kubik＠shaw.ca 22 Aug '24

22 Aug '24

I've spent the last week trying to rebuild Dovecot on my Raspberry Pi 3 (aarch64; running Slackware ARM -current) and am running into the following build error. I suspected it may be my recent update to Slackware but I've been able to build the same source tarball on an x86 system running slackware64-current without any problems, so it *seems* specific to aarch64. I've tried both building from the 2.3.21 (and 2.3.21.1) tarball(s) as well as pulling the latest code from github and they all fail similarly, though in different spots it appears. I am building from source instead of using the available Slackware packages bc those packages don't have support for postgresql built in, but has mysql/mariadb support, which I am not using and is not installed on my systems. While it does run, when I try to connect to it, it fails citing a missing mariadb.so file. gcc -v output: Reading specs from /usr/lib64/gcc/aarch64-slackware-linux-gnu/14.2.0/specs COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/aarch64-slackware-linux-gnu/14.2.0/lto-wrapper Target: aarch64-slackware-linux-gnu Configured with: ../configure --with-arch=armv8-a --verbose --prefix=/usr --mandir=/usr/man --infodir=/usr/info --libdir=/usr/lib64 --enable-bootstrap --enable-checking=release --enable-libstdcxx-dual-abi --enable-shared --enable-languages=ada,c,c++,d,fortran,go,lto,m2,objc,obj-c++,rust --enable-objc-gc --enable-threads=posix --enable-__cxa_atexit --enable-gnu-unique-object --enable-clocale=gnu --enable-plugin --enable-lto --with-arch-directory= --with-system-zlib --with-gnu-ld --with-isl --with-default-libstdcxx-abi=new --disable-libunwind-exceptions --disable-libstdcxx-pch --disable-libssp --disable-werror --disable-gtktest --disable-install-libiberty --host=aarch64-slackware-linux-gnu --build=aarch64-slackware-linux-gnu --target=aarch64-slackware-linux-gnu Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 14.2.0 (GCC) ldd --version output: ldd (GNU libc) 2.40 Copyright (C) 2024 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Written by Roland McGrath and Ulrich Drepper. Configure is: ./configure \ --with-pgsql \ --localstatedir=/var \ --with-lucene \ --with-libcap \ --with-inotify=inotify \ --disable-static \ --build=$ARCH-slackware-linux || exit 1 And the output at the point of failure is: libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../.. -I../../../../src/lib -I../../../../src/lib-test -I../../../../src/lib-settings -I../../../../src/lib-mail -I../../../../src/lib-imap -I../../../../src/lib-imap-client -I../../../../src/lib-index -I../../../../src/lib-storage -I../../../../src/lib-storage/list -I../../../../src/lib-storage/index -I../../../../src/lib-ssl-iostream -std=gnu99 -g -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -MT imapc-sync.lo -MD -MP -MF .deps/imapc-sync.Tpo -c imapc-sync.c -fPIC -DPIC -o .libs/imapc-sync.o free(): double free detected in tcache 2 during GIMPLE pass: slp imapc-sync.c: In function ‘imapc_initial_sync_check’: imapc-sync.c:294:1: internal compiler error: Aborted 294 | imapc_initial_sync_check(struct imapc_sync_context *ctx, bool nooped) | ^~~~~~~~~~~~~~~~~~~~~~~~ 0x1b4a3df internal_error(char const*, ...) ???:0 0x7f80a139fc pthread_kill@@GLIBC_2.34 ???:0 0x7f809c419b gsignal ???:0 0x7f809abfa7 abort ???:0 0x7f80a06943 __libc_message_impl ???:0 0x7f80a1e2c7 malloc_printerr ???:0 0x7f80a2053b _int_free ???:0 0x7f80a22b7f __free ???:0 0xfa35d7 _slp_tree::~_slp_tree() ???:0 0xfa3aa7 vect_free_slp_instance(_slp_instance*) ???:0 0xfb9a7f vect_slp_analyze_operations(vec_info*) ???:0 0xfc06a7 vect_slp_function(function*) ???:0 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. make[5]: *** [Makefile:597: imapc-sync.lo] Error 1 make[5]: Leaving directory '/data/local/src/Dovecot/dovecot-2.3.21/src/lib-storage/index/imapc' make[4]: *** [Makefile:733: all-recursive] Error 1 make[4]: Leaving directory '/data/local/src/Dovecot/dovecot-2.3.21/src/lib-storage/index' make[3]: *** [Makefile:1107: all-recursive] Error 1 make[3]: Leaving directory '/data/local/src/Dovecot/dovecot-2.3.21/src/lib-storage' make[2]: *** [Makefile:573: all-recursive] Error 1 make[2]: Leaving directory '/data/local/src/Dovecot/dovecot-2.3.21/src' make[1]: *** [Makefile:704: all-recursive] Error 1 make[1]: Leaving directory '/data/local/src/Dovecot/dovecot-2.3.21' make: *** [Makefile:548: all] Error 2 Can someone please help me figure this out? If more output is required let me know and I can provide it. Thank You!

2 2

limits to auth of submission
by horizon＠secubox.org 21 Aug '24

21 Aug '24

Hello I am using a plaintext db as the auth db. The db content is like this line: user@mail.com:{CRYPT}$****::::::userdb_quota_rule=*:bytes=1G How can I limit some people can auth with postfix submission (port 587), and some others can't? Thank you.

1 0

Seeking Suggestions for Optimizing Dovecot Performance
by leoniemeeyr＠gmail.com 21 Aug '24

21 Aug '24

Hi everyone, I hope you’re all doing well! I’ve been working with Dovecot for a while now and I’m looking to optimize its performance on my server. I’d love to hear any tips or suggestions you might have to help me get the best performance out of it. Specifically, I’m interested in: 1. Configuration Tweaks: Any key settings that you’ve found to be particularly beneficial for performance? 2. Best Practices: Are there any common practices or tools that help in monitoring and improving performance? 3. Resource Management: How do you handle resource allocation to ensure smooth operation under heavy loads? Any advice or experiences you can share would be greatly appreciated! Thanks in advance for your help. Best Regards https://www.igmguru.com/blog/msbi-vs-power-bi

1 0

dovecot-indexer writting as root
by Joan Moreau 20 Aug '24

20 Aug '24

Hi I have that issue times to times Full case described properly here : https://github.com/grosjo/fts-xapian/issues/168 Can you help understand the root cause of that ? THank you

3 6

SQL Multiple passwords
by Aubry 19 Aug '24

19 Aug '24

Hi, From what I understood from the archive and from my tests, we cannot have multiple passwords for a given account. (I get the error: Password query returned multiple matches) But it looks like it can be done via a PAM module. Does anyone succeeded setup multiple password with PAM or any other method with a SQL backend ? Regards, Aubry

6 7

Re: Frequency Control for IMAP connection
by Joseph Tam 16 Aug '24

16 Aug '24

From: Corey H <coreyh(a)alwaysdata.net> > $ sudo tail -10000 /var/log/mail.log|grep **(a)**mail.com|wc -l > 3544 > > logs like this: > > Aug 15 19:54:10 mx dovecot: imap-login: Login: user=<**(a)**mail.com>, > method=PLAIN, rip=**, lip=**, mpid=4151830, TLS, > session=<UPotgLcfTOjYUzTN> > > How can I implement a Frequency Control on client connections to slow > down his requests? Is this a MacOSX client? I think they have a habit of doing this when doing global mailbox searches. Instead of doing a sane serial march through mailboxes, it opens up as many mailboxes as it can, then closes them when the IMAP server denies then when they hit the max. If Aki doesn't can't offer a solution, neither can I, but maybe you can play around with mail_max_userip_connections to stop them from swamping all your connections. You might have to resort to firewall or other general network controls to actually rate limit connections. Joseph Tam <jtam.home(a)gmail.com>

2 1

dovecot-2.3.2.1 and dovecot-pigeonhole-0.5.2 bug?
by Jan Nowak 16 Aug '24

16 Aug '24

Hello, we have a problem after updating the software with the operation of sieve scripts sending a copy of the e-mails, e-mails are not transferred. Configuration: dovecot-2.3.2.1 + dovecot-pigeonhole-0.5.2 + FreeBSD 11.2 log: Sep 06 13:28:17 lda(XXX@XXX)<38615><XXX+XXX>: Info: sieve: msgid=<XXX-XXX-XXX-7788-XXX@XXXXnet>: stored mail into mailbox 'INBOX' Sep 06 13:28:17 lda(XXX@XXX)<38615><XXX+XXX>: Info: sieve: Execution of script /usr/home/XXX/mail/XXX(a)XXX/.dovecot.sieve failed, but implicit keep was successful (user logfile /usr/home/XXX/mail/XXX(a)XXX/.dovecot.sieve.log may reveal additional details) .dovecot.sieve.log: error: msgid=<XXX-XXX-XXX-7788-XXX@XXXXnet>: failed to redirect message to <XXXXX(a)XXXXXX.com>: smtp(127.0.0.1:25): DATA failed: 552 Message header not CRLF terminated (permanent failure). On old configuration: dovecot 2.2 + dovecot-pigeonhole- 0.4 + FreeBSD 11.2 we don't have problem. Has anyone had a similar problem, knows the solution?

5 12

The future of SIS
by Sebastian Marsching 16 Aug '24

16 Aug '24

Hi, I am currently in the process of planning a new deployment of Dovecot. I was planning to use mdbox or sdbox with “mail_attachment_fs = sis posix”, but I stumbled across the following notice in the documentation for Dovecot 3.0 (https://doc.dovecot.org/3.0/settings/core/#core_setting-mail_attachment_fs) > Changed in version 2.4.0 (CE): SIS is deprecated and writing of SIS files is disabled. Reading is supported for now, any missing SIS attachments are replaced with files filled with spaces. > > Changed in version 3.0.0 (Pro): SIS is deprecated and writing of SIS files is disabled. Reading is supported for now, any missing SIS attachments are replaced with files filled with spaces. And https://doc.dovecot.org/3.0/installation_guide/upgrading/from-2.3-to-3.0/ says: > Saving new mails’ attachments via fs-sis is disabled, but reading SIS attachments is still supported. Missing SIS attachments are replaced with files filled with spaces. What is not entirely clear from this comment is whether this only applied to “sis posix” or also to “sis-queue posix”. Does anybody whether sis-queue is also affected by this? I saw that the notice was added to the dovecot/documentation Git repository in April 2023, but I couldn’t find any further information there or the main branch of the dovecot/core repository. Maybe, the code for 2.4 / 3.0 has not made it into that branch or repository yet. SIS sounds like a neat concept and I would like to use it, but obviously I do not want to use a soon-to-be-deprecated feature in a completely new deployment. So, does anybody know an alternative solution for attachment deduplication (except file-system level deduplication)? Thanks, Sebastian

19 43