currently the client_limt is at zero, and I believe this is unlimited
service config {
chroot =
client_limit = 0
drop_priv_before_exec = no
executable = config
extra_groups =
group =
idle_kill = 1 mins
privileged_group =
process_limit = 0
process_min_avail = 16
protocol =
The only thing I had initially configured was vsz_limit, but as the
number of clients grew, the number of dovecot/config processes grew, and
with that I added idle_kill and service_count to try to minimize the use
of ram memory
In dovecot 2.2.33.2 , another server, has the same amount of account
Hello,
I tested the suggestion to decrease the service_count and the accounts
stopped logging in, then I gradually increased it to 500, and now it's
working. But the dovecot/config processes are still being created, there
has been no change for the better.
Now I have an error constantly appear
I'm having strange behavior in dovecot 2.3.16.
It's opening dozens of dovecot/config process and consuming all server
memory. Normally each process consumes between 700Mb and 1Gb of ram.
Would anyone have an idea about this?
service config {
vsz_limit = 2048M
idle_kill = 60s
service_coun
soon after starting dovecot these errors start to appear. I will send
the first errors after doing a service dovecot start
Jul 15 10:08:16 box5 dovecot: pop3: Error: conn
unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for
handshake response
Jul 15 10:08:16 box5 dov
Hi, I'm using ubuntu 22.04 and installed dovecot 2.3.16.
I did some initial testing with 100 email accounts and everything seemed
to work perfectly the same as dovecot version 2.3.16 on another server.
So I performed the migration of approximately 30 thousand email
accounts, but the following e
Hello, my name is Filipe
I'm migrating an email server to another new server. Accounts have their
storage configured as mdbox and their index being saved in another
storage device. I want to migrate all messages to the new server with a
new storage mode, sdbox.
The new server will have stora
