dovecot - Mar 2011 - logging issues w/ login_max_processes_count on 1.x

Today I found our dovecot 2.x gracefully logged:
dovecot: master: Warning: service(imap-login): process_limit reached, client
connections are being dropped

I am confident that we had the very same problem on our previous dovecot 1.x
box. Of course with dovecot 1.x, the same relative setting is
login_max_processes_count. I believe that I turned up all dovecot logging &
debugging to the max (also checked with the 1.x wiki), but nothing was ever
logged relating to this.

Does anyone know whether there is a way to get dovecot 1.x to log this type of
error?

Thanks,
-
Doug Mortensen
Network Consultant
Impala Networks Inc
CCNA, MCSA, Security+, A+
Linux+, Network+, Server+
.
www.impalanetworks.com
P: (505) 327-7300
F: (505) 327-7545

On 4.3.2011, at 1.12, Douglas Mortensen wrote:
> Today I found our dovecot 2.x gracefully logged:
> dovecot: master: Warning: service(imap-login): process_limit reached,
client connections are being dropped
> 
> Does anyone know whether there is a way to get dovecot 1.x to log this type
of error?
As long as all of the connection slots aren't used for SSL connections, it
should log:

Disconnected: Connection queue full

as some (not yet logged in) client's disconnection reason. It kills the
oldest client away. This is actually what v2.0 also does in that situation, it
just logs that extra warning. If all of the login processes are busy serving SSL
sessions, v1.x logs:

All login processes are in use. You may need to increase
login_max_processes_count