July 2024 - dovecot - dovecot.org

[auth] epoll_ctl(add, 13) failed: Operation not permitted (fd doesn't support epoll)
by Alexander Vogt 05 Jul '24

05 Jul '24

Hi all, dovecot auth service is failing when using an inet_service. The configuration is essentially: service auth { inet_listener { address = * port = 12345 } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } When I connect to port 12345 (real IMAP client or telnet doesn't make a difference), the auth service crashes. Nov 19 22:21:54 imap.linexus.de dovecot[7195]: auth: Panic: epoll_ctl(add, 13) failed: Operation not permitted (fd doesn't support epoll) Nov 19 22:21:54 imap.linexus.de dovecot[7195]: auth: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x46) [0x7f9319f89486] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x22) [0x7f9319f895a2] -> /usr/lib64/dovecot/libdovecot.so.0(+0x10a41b) [0x7f9319f9841b] -> /usr/lib64/dovecot/libdovecot.so.0(+0x10a4b7) [0x7f9319f984b7] -> /usr/lib64/dovecot/libdovecot.so.0(+0x5d11a) [0x7f9319eeb11a] -> /usr/lib64/dovecot/libdovecot.so.0(+0x609b0) [0x7f9319eee9b0] -> /usr/lib64/dovecot/libdovecot.so.0(+0x1215ba) [0x7f9319faf5ba] -> /usr/lib64/dovecot/libdovecot.so.0(io_add_to+0x1d) [0x7f9319faf62d] -> /usr/lib64/dovecot/libdovecot.so.0(io_add+0x28) [0x7f9319faf668] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_io_listeners_add+0x8a ) [0x7f9319f1d16a] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_init_finish+0xff) [0x7f9319f24bdf] -> dovecot/auth(main+0x389) [0x55745603a4f9] -> /lib64/libc.so.6(+0x3feb0) [0x7f931963feb0] -> /lib64/libc.so.6(__libc_start_main+0x80) [0x7f931963ff60] -> dovecot/auth(_start+0x25) [0x55745603a715] System info (sysreport attached): # 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.16 (09c29328) # OS: Linux 5.14.0-383.el9.x86_64 x86_64 CentOS Stream release 9 This exact configuration is known to work on this system: # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) I tried for almost two hours to get a core dump for this, but finally gave up. I followed https://www.dovecot.org/bugreport-mail/#coredumps and other sources but the best I could get was Nov 19 22:21:54 imap.linexus.de dovecot[7195]: auth: Fatal: master: service(auth): child 7198 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - core wasn't writable?) for cat /proc/sys/kernel/core_pattern /tmp/core.%e.%p (which is 1777). Any help to get this resolved would be much appreciated! Thanks and best regards Alex

3 5

dsync will be removed in 2.4 - why?
by Oliver Krone 05 Jul '24

05 Jul '24

Hi there, I recently learned that dsync (mail replication) functionality will be removed in the upcoming releases of dovecot. What is the reason and will there be a replacement? How can I synchronize my e-mails in the future? Thanks a lot. Regards Oliver

3 2

Is it possible to access cert_username and original_username the same time?
by bisteycsaba＠gmail.com 05 Jul '24

05 Jul '24

Hello all, If i use auth_ssl_username_from_cert dovecot gets its username from certificate, but seems like it also becomes %orig_user , if i do not use auth_ssl_username_from_cert cert_username completly unaccessable. Is there a way to access the original user supplied username when auth_ssl_username_from_cert is set or am i missed something and there is a variable for cert_username? What i would like to do is use username from cert to determine which email accounts a user with that cert has access to but for that i would both need access to cert_username and the username given by the user, but when username supplied from cert seems like the username supplied by the user no longer accessable, or i cant figure out how to access it. Thanks: Csaba

1 0

dovecot replication problem
by Oliver Krone 05 Jul '24

05 Jul '24

Hi there, I'm experiencing the following when I replicate mails between two host, using different versions of dovecot: *Host A Host B result* dovecot-2.3-19 --> dovecort-2.3.16 ERROR: auth: Error: All password databases were skipped. doveadm(10.0.0.1,oliver.krone(a)snoog.ch): Error: auth-master: passdb lookup(oliver.krone(a)snoog.ch): Auth PASS lookup failed mail | 2024-07-04T14:21:35.635047+00:00 mail dovecot: doveadm(10.0.0.1,oliver.krone(a)snoog.ch): Error: /run/dovecot/auth-userdb: passdb lookup failed (to see if user is proxied, because doveadm_port is set) dovecot-2.3-21 --> dovecort-2.3.16 no errors, working Basically it does work with 2.3-21 --> 2.3-16 and it does not work with 2.3-19 ---> 2.3-16 without any changes in the configuration files. Any ideas? Thank you very much. Best regards Oliver

2 1

Doveadm on director
by g.carabella＠panservice.it 04 Jul '24

04 Jul '24

https://doc.dovecot.org/admin_manual/doveadm_mailbox_commands/ As indicated in the documentation above, in case of configuration with the director, the doveadm commands must be executed from the director itself. However, if I try to run the command "doveadm -D mailbox list -u user(a)example.com" the command fails because it tries to lookup user locally instead on one of the backend servers. Where am I wrong? My configuration consists of three directors and three backend servers. Thanks a lot.

1 0

Error: fts_solr: received invalid uid
by oliver.krone＠snoog.ch 04 Jul '24

04 Jul '24

I'm using dovecot 2.3.13, solr 8.x. and roundcube 1.5.1. However when I do a search I get the the Error: fts_solr: received invalid uid, search results are ok. Thanks

5 4

One-way synchronization with doveadm/TCP
by Дилян Палаузов 04 Jul '24

04 Jul '24

Hello, the replication procedure described at https://doc.dovecot.org/configuration_manual/replication/ suggests to open a server port 12345 on two systems, and then point each system to the other one. This creates bi-directional synchronization. I want to synchronize only from server A to server B, but not in the opposite direction. Is it sufficient on server A to set service doveadm { inet_listener { port = 12345 } } doveadm_password = secret and server B to set doveadm_port = 12345 doveadm_password = secret ? In other words, when a doveadm client (system B) connects to a server (system A) for replication purposes, does it only read data? Or does it instruct the server also to delete data? To start the replication I had to executed «doveadm replicator replicate '*'». Is in necessary to run this periodically? Thanks for your answer, Дилян

2 1

login_access_sockets
by John Fawcett 03 Jul '24

03 Jul '24

Hi I've used Dovecot for a long time but I never stop learning about the depth of features I've never used.... I just discovered the login_access_sockets setting when reading this page: https://doc.dovecot.org/admin_manual/login_processes/ The compilation using --with-libwrap configure setting was not immediate, since on Fedora which I am using there is no tcp_wrappers-devel package so tcpd.h wasn't installed in /usr/include and the library name libwrap.so that was expected by Dovecot needed a symlink to the library installed by tcp_wrappers package. So differently to what I previously understood, Dovecot does have a way of controlling access at connect time via tcp_wrappers hosts.allow and hosts.deny files. But now I also realize that this discovery will be short lived, since I understand this is going away in 3.0 and also 2.4 though I can't find a page on that: https://doc.dovecotpro.com/3.0/installation/upgrading/2.3.x-3.x.html I can understand the logic about slimming down the code to leave out less used features, but this part of the code looks well written and hasn't required much maintenance over the years. I know there's zero chance of reversing the removal of login_access_sockets, but I just wondered whether there could be the chance to introduce a LUA hook at connect time rather than waiting for authentication to be done. Also I have no idea what the overhead of LUA script is, does it spawn additional processes per connection? Thanks John

1 0

IMAP login-logout cycle performance with performance mode seems slow/limited and cause cannot be found
by m＠maltris.org 03 Jul '24

03 Jul '24

Hello, I am running a test setup in a docker stack with Dovecot (2.3.21). Basically as a test to see whats possible. The whole thing works okay, but I noticed that with imaptest (latest version) somewhere between 230 and 270 requests per second on a login+logout cycle it cannot go further. However, this is a 384G memory, 48 core, dual-cpu setup that is pretty much idling (utilization somewhere around 6-12%). The ssds are not loaded at all. The memory usage is low. For testing purpose I set nopassword=y and allowed all logins, the users just require a small mysql db lookup which is done once before the cache is filled. If I copy that exact same stack to my local machine, I yield around 450 cycles per second. And the only difference I somehow see is that my local machine has a faster cpu-memory connection and only one cpu with less cores. Is it possible memory speed is a limiting factor because of the cpu-memory-mapping on the server and the slower memory? What performance should I expect? Asking because I am planning to run a stateless client at a later point and the limited login-performance really seems to make that difficult at scale. doveconf -n: # 2.3.21 (47349e2482): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.21 (f6cd4b8e) # OS: Linux 6.8.0-36-generic x86_64 Debian 11.7 ext4 # Hostname: 4e83f0e9d630 auth_cache_negative_ttl = 0 auth_cache_size = 50 M auth_cache_ttl = 5 hours auth_cache_verify_password_with_worker = yes auth_debug = yes auth_debug_passwords = yes auth_failure_delay = 0 auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = yes auth_worker_max_count = 500 default_vsz_limit = 2 G disable_plaintext_auth = no doveadm_api_key = # hidden, use -P to show it doveadm_password = # hidden, use -P to show it doveadm_port = 2425 log_debug = event=* log_path = /var/log/dovecot-debug.log login_trusted_networks = 10.0.0.0/8 127.0.0.0/8 mail_debug = yes mail_fsync = never mail_gid = 1000 mail_location = maildir:/data/vmail/%d/%1n/%n mail_uid = 1000 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 = nopassword=y driver = static } protocols = " imap lmtp sieve pop3 submission" service anvil { chroot = empty client_limit = 75100 idle_kill = 4294967295 secs process_limit = 1 unix_listener anvil-auth-penalty { mode = 00 } } service auth-worker { client_limit = 1 process_limit = 6000 user = $default_internal_user } service auth { client_limit = 91000 } service doveadm { inet_listener { port = 2425 } inet_listener http { port = 8080 } } service imap-login { process_limit = 15000 process_min_avail = 48 service_count = 0 vsz_limit = 2 G } service imap { client_limit = 1 process_limit = 15000 } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol doveadm { passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql name = override_fields = port=2425 ssl=no starttls=no } } protocol imap { mail_max_userip_connections = 250 } Best regards

2 5

AW: AW: AW: IMAPSieve plugin will not run rspamd script
by postfix_dovecot＠gmx.de 02 Jul '24

02 Jul '24

Hi John, the prefix is just a sign of my desperation - I tried all sorts of variations yesterday and now forgot to undo it. There’s a very detailed tutorial available (German language) with Debian 10. Just the sieve scripts are little different. I spend the time to raise a Debian 10 with this tutorial – and with exact the same result as with my up to date configuration. So it would be interesting for me to know if there is anyone here who has managed to get this to work on Debian? Jens Von: John Fawcett <john(a)voipsupport.it> Gesendet: Montag, 1. Juli 2024 18:26 An: postfix_dovecot(a)gmx.de Betreff: Re: AW: AW: IMAPSieve plugin will not run rspamd script On 01/07/2024 18:08, postfix_dovecot(a)gmx.de <mailto:postfix_dovecot@gmx.de> wrote: Hi John, is there any other log than system? Jens Hi Jens I meant the same type of logging you already posted (i.e. as below) for exactly the same test case, but where the rules use the mailbox name that includes the prefix you set for the namespace (i.e.INBOX/Spam). There is probably a good reason why you have configured a prefix for your namespace, but my suspicion is that the example imapsieve config you copied assumes no prefix set (it was not part of the example so we cannot see it). I personally tried the settings from the example and they work fine and I have no prefix. I also did the opposite test and I get the behaviour you reported when I have prefix set. In order to solve it (without changing the prefix) I had to state the full mailbox name including the prefix in the imapsieve rules. In that case it worked. What I'd like to check in your logging is if there is a clue why it didn't work for you when yu used INBOX/Spam in the rules. John imap(mail(a)test.example <mailto:mail@test.example> )<1797><a/FKmgIcqKvAqB4a>: Debug: Module loaded: /usr/lib/dovecot/modules/lib95_imap_sieve_plugin.so imap(mail(a)test.example <mailto:mail@test.example> )<1797><a/FKmgIcqKvAqB4a>: Debug: imapsieve: mailbox INBOX/Spam: APPEND event imap(mail(a)test.example <mailto:mail@test.example> )<1797><a/FKmgIcqKvAqB4a>: Debug: sieve: Pigeonhole version 0.5.19 (4eae2f79) initializing imap(mail(a)test.example <mailto:mail@test.example> )<1797><a/FKmgIcqKvAqB4a>: Debug: sieve: include: sieve_global is not set; it is currently not possible to include `:global' scripts. imap(mail(a)test.example <mailto:mail@test.example> )<1797><a/FKmgIcqKvAqB4a>: Debug: sieve: Sieve imapsieve plugin for Pigeonhole version 0.5.19 (4eae2f79) loaded imap(mail(a)test.example <mailto:mail@test.example> )<1797><a/FKmgIcqKvAqB4a>: Debug: sieve: Sieve Extprograms plugin for Pigeonhole version 0.5.19 (4eae2f79) loaded imap(mail(a)test.example <mailto:mail@test.example> )<1797><a/FKmgIcqKvAqB4a>: Debug: imapsieve: Static mailbox rule [1]: mailbox=`Spam' from=`*' causes=(COPY APPEND) => before=`file:/usr/lib/dovecot/sieve/report-spam.sieve' after=(none) imap(mail(a)test.example <mailto:mail@test.example> )<1797><a/FKmgIcqKvAqB4a>: Debug: imapsieve: Static mailbox rule [2]: mailbox=`*' from=`Spam' causes=(COPY APPEND) => before=`file:/usr/lib/dovecot/sieve/report-ham.sieve' after=(none) imap(mail(a)test.example <mailto:mail@test.example> )<1795><iC6JmQIcnqvAqB4a>: Debug: imapsieve: mailbox INBOX: FLAG event (changed flags: \Deleted) imap(mail(a)test.example <mailto:mail@test.example> )<1795><iC6JmQIcnqvAqB4a>: Debug: sieve: Pigeonhole version 0.5.19 (4eae2f79) initializing imap(mail(a)test.example <mailto:mail@test.example> )<1795><iC6JmQIcnqvAqB4a>: Debug: sieve: include: sieve_global is not set; it is currently not possible to include `:global' scripts. imap(mail(a)test.example <mailto:mail@test.example> )<1795><iC6JmQIcnqvAqB4a>: Debug: sieve: Sieve imapsieve plugin for Pigeonhole version 0.5.19 (4eae2f79) loaded imap(mail(a)test.example <mailto:mail@test.example> )<1795><iC6JmQIcnqvAqB4a>: Debug: sieve: Sieve Extprograms plugin for Pigeonhole version 0.5.19 (4eae2f79) loaded imap(mail(a)test.example <mailto:mail@test.example> )<1795><iC6JmQIcnqvAqB4a>: Debug: imapsieve: Static mailbox rule [1]: mailbox=`Spam' from=`*' causes=(COPY APPEND) => before=`file:/usr/lib/dovecot/sieve/report-spam.sieve' after=(none) imap(mail(a)test.example <mailto:mail@test.example> )<1795><iC6JmQIcnqvAqB4a>: Debug: imapsieve: Static mailbox rule [2]: mailbox=`*' from=`Spam' causes=(COPY APPEND) => before=`file:/usr/lib/dovecot/sieve/report-ham.sieve' after=(none) imap(mail(a)test.example <mailto:mail@test.example> )<1795><iC6JmQIcnqvAqB4a>: Debug: imapsieve: mailbox INBOX: FLAG event (changed flags: \Seen)

2 10