search for: imap_login

I'm running Dovecot on a very small mail server (never more than six users accessing IMAP, often fewer). I'm seeing the number of imap_login processes grow over time, and right now there are 23. All the "login_process_*" settings in dovecot.conf are commented (ie, at their defaults). Is this a known or expected issue? The version of Dovecot is 0.99.10.8, which I accept is perhaps a little old. Thanks, Keith

Hello, I am using dovecot 2.3.2 on my private email server in conjunction with: centos 7.5 apache 2.4.6 mariadb 10.2.16 roundcube mail 1.3.6 php 5.6.36 postfix 2.10.1 I have one mailbox with nearly 30k messages in it dispersed across several folders. it's often very slow in refreshing the message list, especially in the one largest 25k+ message folder. is this simply to be expected

Just thought I'd check, but is the combination of SSL and "login_process_per_connection = no" expected? I'm wondering, because imap_login is doing the SSL-proxying, and in our live Dovecot instance we have "login_process_per_connection = no" (we had problems with authentication and running out of file descriptors early on, now fixed by using userdb = passwd-file rather than NIS). This combination seems to work OK in 1.0-be...

...to migrate from NFS old netapp to NFS new server (this one is not a netapp !). There 3 kind way (according to my own experience) - rsync old spool to new spool being patient stop services and then doing last rsync and mount /var/mailboxes mount point from old netapp to new nfs server). - doing imap_login (and other stuff like this) doing an rsync per box AFTER doing the first rsync with all boxes... - using dsync to fetch the maildir stuff from old server to new one, doing a simple flag, and doing "au fil de l'eau" migration. The last one seems to me a good idea, but I cannot figur...

Hi, [Steffen Kaiser] - [2016-07-26 09:05] >>>> I am running a dovecot server and have set up an external >>>> monitoring, where every five minutes a login with SSL on port >>>> 993 is done. I usually get once a day an error "connection >>>> reset by peer - SSL connect", which goes away until the next >>>> monitor is executed.