Package: imapproxy Version: 1.2.6-5 Severity: important Hola,
I upgraded Etch to Lenny today and ended with imapproxy service not being up. I researched a bit and the problem seems to be that imapproxy refuses to start when no imap server is reachable / available. This is dangerous and could derive in service lost (depending on imap server stability, possible network outages, etc). In my case, I suppose that imapproxy was restarted when cyrus was down. This is what I can see in mail.log: Feb 27 01:13:03 hsnew in.imapproxyd[5250]: No syslog priority mask specified. Feb 27 01:13:03 hsnew in.imapproxyd[5250]: main(): SELECT caching is disabled Feb 27 01:13:03 hsnew in.imapproxyd[5250]: main(): Internal admin commands are disabled Feb 27 01:13:03 hsnew in.imapproxyd[5250]: main(): Allocating 3072 IMAP connection structures. Feb 27 01:13:03 hsnew in.imapproxyd[5250]: ServerInit(): Using '/var/log/imapproxy_protocol.log' for global protocol logging file. Feb 27 01:13:03 hsnew in.imapproxyd[5250]: ServerInit(): proxying to IMAP server 'localhost'. Feb 27 01:13:03 hsnew in.imapproxyd[5250]: ServerInit(): Proxying to IMAP port 143 Feb 27 01:13:03 hsnew in.imapproxyd[5250]: ServerInit(): Connection refused -- exiting Look at the last line: imapproxy exited because it couldn't connect to imap server!!!!! This is unforgivable for a proxy service... The correct behaviour should be logging the error and then continue serving requests (waiting imap service to get up). Tested on Debian Lenny, up to date. -- Saludos, -Roman PGP Fingerprint: 09BB EFCD 21ED 4E79 25FB 29E1 E47F 8A7D EAD5 6742 [Key ID: 0xEAD56742. Available at KeyServ] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
