We have been increasing our user count and have only run across these errors so far (dovecot-1.0.rc27):
Mar 18 02:50:14 myhost.mydomain dovecot: pop3-login: Can't connect to auth server at default: Connection refused Mar 18 04:07:13 myhost.mydomain dovecot: imap-login: Can't connect to auth server at default: Connection refused Mar 18 05:43:14 myhost.mydomain dovecot: pop3-login: Can't connect to auth server at default: Connection refused Mar 18 07:39:38 myhost.mydomain dovecot: imap-login: Can't connect to auth server at default: Connection refused Mar 18 07:58:44 myhost.mydomain dovecot: imap-login: Can't connect to auth server at default: Connection refused Mar 18 09:55:20 myhost.mydomain dovecot: imap-login: Can't connect to auth server at default: Connection refused
I presume that the changes Timo made in response to my previous inquiry about refused connections at reboot will fix these. My question is: what do clients see when this situation arises? Is it transparent, or does the client/user end up having to re-connect?
--
Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs@umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593