Re: Clarification Question about migrating_mailboxes and broken doc link
On 2025-02-01 (Sa.) 07:28, Aki Tuomi via dovecot wrote: On 01/02/2025 01:56 EET Aleks via dovecot wrote: Hi. [snipp] The question is for me now: I think that this command `doveadm backup -Ru username tcp:host:port` should be executed on the mail2. Is this assumption right? Yes. [snipp] What's the right link for the manpages https://doc.dovecot.org/latest/ Best regards Aleks Aki Thanks Alex ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Different Replicator Crash??
After adding patch you mentioned I no longer have replicatior out of memory. Are you sure you patched both sides? 31.01.2025 22:27, Kent Borg via dovecot пишет: I added the suggested "count--" and recompiled, and it now appears to work, the replication goes both ways, eyeballing the e-mail on the two servers they look the same. Good. But part of the time I am still getting what looks very much like the same crash, is there another "count--" I need to add to that file? Jan 28 10:53:08 la dovecot[96175]: replicator: Panic: data stack: Out of memory when allocating 268435496 bytes Jan 28 10:53:08 la dovecot[96175]: replicator: Error: Raw backtrace: #0 t_askpass[0x7fb404b0c0] -> #1 backtrace_append[0x7fb404b374] -> #2 backtr\ ace_get[0x7fb404b510] -> #3 execvp_const[0x7fb4057ba4] -> #4 i_syslog_fatal_handler[0x7fb4058510] -> #5 i_panic[0x7fb3fa6808] -> #6 t_pop_pass_st\ r[0x7fb4050eb4] -> #7 connection_deinit[0x7fb4056430] -> #8 pool_datastack_create[0x7fb407e7b0] -> #9 array_bsearch_insert_pos_i[0x7fb40446d0] ->\ #10 t_base64_scheme_decode[0x7fb404cb24] -> #11 buffer_append[0x7fb404d3d0] -> #12 replicator_queue_push[0x558c4b4f40] -> #13 replicator_brain_i\ nit[0x558c4b53e4] -> #14 _start[0x558c4b3d70] -> #15 _start[0x558c4b3f04] -> #16 io_loop_call_io[0x7fb4072f20] -> #17 io_loop_handler_run_interna\ l[0x7fb4075450] -> #18 io_loop_handler_run[0x7fb4075680] -> #19 io_loop_run[0x7fb4075944] -> #20 master_service_run[0x7fb3fd84b0] -> #21 main[0x5\ 58c4b3930] -> #22 __libc_init_first[0x7fb3dd76d0] -> #23 __libc_start_main[0x7fb3dd7780] -> #24 _start[0x558c4b3b80] Jan 28 10:53:08 la dovecot[96175]: replicator: Fatal: master: service(replicator): child 96714 killed with signal 6 (core dumps disabled - https:\ //dovecot.org/bugreport.html#coredumps) Thanks, -kb ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
IMAP dovecot\postgres low authentication performance
Hi. We have a performance problem with imap authentication through
postgresql.
Our servers(modoboa based) have a big amount of permanent imap
connections(5000-5).
Current performance is about 3000 successful authentications per hour. No
visible reasons for such low speed. Accordingly, after a network failure or
server restart, all clients try to reconnect, but restoring the connection
pool takes hours and even tens of hours. Judging by the logs after the
restart, a huge number of auth requests closed by timeout after 70-90
seconds. The postgresql database is not overloaded at the restore
connections process and the postgresql connection pool (100) does not
overflow. Manually started sql auth queries work fast, tables have indexes.
So I guess there is a bottleneck somewhere in dovecot auth service or
postgresql driver.
I couldn't find any settings in the documentation that are directly
responsible for regulating the number of connections to PostgreSQL from the
auth service or performance of the driver. Is there any way to manage this?
Does it make sense to use pgbouncer in front of the base? What else can be
a bottleneck in our configuration and how to regulate the number of
possible simultaneous authentications via PostgreSQL? I would be happy for
any advice on how to increase the performance to at least 100
authentications per second.
Thanks in advance for your help.
Anatoliy Zhestov.
configs of server with 48 core, 184 gb mem ---
dovecot 2.3.16
# 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.16 (09c29328)
# OS: Linux 5.15.0-126-generic x86_64 Ubuntu 22.04.5 LTS
# Hostname: imap.ourcompany.net
auth_cache_negative_ttl = 0
auth_cache_size = 20 M
auth_cache_ttl = 3 hours
auth_master_user_separator = *
auth_mechanisms = plain login
default_client_limit = 131072
default_process_limit = 131072
dict {
quota = pgsql:/etc/dovecot/dovecot-dict-sql.conf.ext
}
mail_location = maildir:~/Maildir
mail_plugins = quota
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 mai
lbox date index ihave duplicate mime foreverypart extracttext editheader
imapflags notify vnd.dovecot.pipe vnd.dovecot.execute
namespace inbox {
inbox = yes
location =
mailbox Drafts {
auto = subscribe
special_use = \Drafts
}
mailbox Junk {
auto = subscribe
special_use = \Junk
}
mailbox Sent {
auto = subscribe
special_use = \Sent
}
mailbox Trash {
auto = subscribe
special_use = \Trash
}
prefix =
}
passdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
passdb {
args = /etc/dovecot/dovecot-sql-master.conf.ext
driver = sql
master = yes
pass = yes
}
plugin {
quota = dict:User quota::proxy::quota
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
sieve_execute_bin_dir = /usr/lib/dovecot/sieve-execute
sieve_execute_socket_dir = .
sieve_extensions = +notify +imapflags +editheader +body
+vnd.dovecot.execute +vnd.dovecot.pipe
sieve_pipe_bin_dir = /usr/lib/dovecot/sieve-execute
sieve_pipe_socket_dir = .
sieve_plugins = sieve_extprograms
}
protocols = " imap lmtp sieve"
service anvil {
client_limit = 393219
}
service auth {
client_limit = 524288
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0666
user = postfix
}
unix_listener auth-radicale {
group = radicale
mode = 0666
user = radicale
}
unix_listener auth-userdb {
user = vmail
}
}
service config {
vsz_limit = 1 G
}
service dict {
unix_listener dict {
mode = 0600
user = vmail
}
}
service imap {
executable = imap postlogin
process_limit = 131072
vsz_limit = 1 G
}
service lmtp {
unix_listener /var/spool/postfix/private/dovecot-lmtp {
group = postfix
mode = 0600
user = postfix
}
vsz_limit = 512 M
}
service pop3 {
executable = pop3 postlogin
}
service postlogin {
executable = script-login /usr/local/bin/postlogin.sh
service_count = 1000
process_min_avail = 5
user = modoboa
}
service send-to-click-frontapp1 {
executable = script
/usr/lib/dovecot/sieve-execute/clickhouse_log_frontapp1.sh
unix_listener send-to-click-frontapp1 {
group = vmail
mode = 0666
user = vmail
}
user = dovenull
vsz_limit = 2 G
}
service send-to-click {
executable = script /usr/lib/dovecot/sieve-execute/clickhouse_log.sh
unix_listener send-to-click {
group = vmail
mode = 0666
user = vmail
}
user = dovenull
vsz_limit = 2 G
}
service stats {
unix_listener stats-reader {
group = vmail
mode = 0660
user = vmail
}
unix_listener stats-writer {
group = vmail
mode = 0660
user = vmail
}
vsz_limit = 2 G
}
ssl_cert =
/dev/null
exec "$@"
/usr/lib/dovecot/sieve-execute/clickhouse_log_frontapp1.sh
#!/bin/bash
cd /tmp
logger -i -t SIEVE_
Re: [Dovecot-news] Dovecot v2.4.0 released - FTS plugin also released
Hi all, I just wanted to say thanks for all your efforts and bringing this looking to be promising release together. I spent the last two days tinkering with old and new configurations. Sadly I had to revert back to 2.3.21😭. Everything worked just fine including compression and sieve and secure connections except Exim with Dovecot LMTP and authenticator. There seem to be a bug, only occurs when I attempt to send remote email, I connect to smtp via Exim which uses dovecot auth-client socket to authenticate user, dovecot accepts the connection from Exim, makes sql driver query from mysql to check passdb, and stalls there forever and noticed it keeps opening more and more and more connections with unique fd until it reaches anvil limit and disallow logins and if I disable anvil service like it was recommended in documentation, it reaches max user connected using same ip address limit and disallow logins again. I tinkered so much with permissions and both exim and dovecot logs trying to find any lead to fix yet to no avail I found way, as everything works fine when I return to 2.3.21. using old yet identical configuration. One thing I remember happened before and its similar in terms of exim authentication stalling experience, its when I set ssl = yes inside lmtp service in 2.3.21 and when I remove it works fine. Along this, I noticed the only different configuration its the address member in the lmtp service referenced here https://doc.dovecot.org/2.4.0/core/config/delivery/lmtp.html#lmtp-server When I set it, dovecot 2.4 fails to start service and returns " address " unrecognised option. Its quite strange and not sure why its still in documentation page which was updated few days ago, on the 27th. I had to remove it while in 2.3.21 I can set it to the smtp server address which exim makes lmtp call to byname and works fine. Dovecot 2.4 works fine with receiving remote emails since no authentication is required from mta agent, exim since it just transports the email to lmtp transport and forward it to dovecot. I hope the team to review this bug when they have the chance and address it in the incoming release. I am really excited to give dovecot 2.4 another try hopefully with much better release. In case I missed anything which with I can fix this problem, I would also appreciate if anyone let me know. With thanks. Zakaria. ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Exim / Dovecot v2.4.0 authentication patch
Hi, Dovecot v2.4.0 changed authentication protocol slightly to allow new functionality (SCRAM TLS channel binding). It attempted to preserve backwards compatibility by checking client-provided VERSION first before sending data that the client wouldn't handle correctly. However, Exim's Dovecot authenticator doesn't send VERSION until Dovecot has sent the whole authentication handshake. This causes Exim to get stuck when trying to authenticate. I guess we'll provide some kind of a workaround for v2.4.1, but this should get fixed on Exim side as well. Attached a patch that I tested works (against 4.97-4ubuntu4). exim4-dovecot24-auth.patch Description: Binary data ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
