Your message dated Tue, 22 Nov 2016 05:16:52 -0600 with message-id <[email protected]> and subject line Re: fails to configure when an IMAP server is not available has caused the Debian Bug report #512369, regarding fails to configure when an IMAP server is not available to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 512369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512369 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: imapproxy Version: 1.2.6-4 Severity: serious This package fails to configure with the default settings when an IMAP server can't be reached on localhost:143. Setting up imapproxy (1.2.6-4) ... Starting IMAP proxy: invoke-rc.d: initscript imapproxy, action "start" failed. dpkg: error processing imapproxy (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: imapproxy Jan 20 09:10:38 testhost imapproxyd: main(): Using configuration file '/etc/imapproxy.conf' Jan 20 09:10:38 testhost imapproxyd: Using syslog facility 'LOG_MAIL' for logging. Jan 20 09:10:38 testhost in.imapproxyd[18812]: No syslog priority mask specified. Jan 20 09:10:38 testhost in.imapproxyd[18812]: main(): SELECT caching is disabled Jan 20 09:10:38 testhost in.imapproxyd[18812]: main(): Internal admin commands are disabled Jan 20 09:10:38 testhost in.imapproxyd[18812]: main(): Allocating 3072 IMAP connection structures. Jan 20 09:10:38 testhost in.imapproxyd[18812]: ServerInit(): Using '/var/log/imapproxy_protocol.log' for global protocol logging file. Jan 20 09:10:38 testhost in.imapproxyd[18812]: ServerInit(): proxying to IMAP server 'localhost'. Jan 20 09:10:38 testhost in.imapproxyd[18812]: ServerInit(): Proxying to IMAP port 143 Jan 20 09:10:38 testhost in.imapproxyd[18812]: ServerInit(): Connection refused -- exiting I'd expect retrying in the background or even leaving it disabled, but postinst failure seems too intrusive. See also #512272, which makes the postinst hang if configured with an invalid hostname. Release team, please downgrade if this is considered acceptable for the release. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-xen-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages imapproxy depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii libc6 2.7-16 GNU C Library: Shared libraries ii libncurses5 5.7+20081213-1 shared libraries for terminal hand ii libssl0.9.8 0.9.8g-14 SSL shared libraries ii libwrap0 7.6.q-16 Wietse Venema's TCP wrappers libra ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip imapproxy recommends no packages. imapproxy suggests no packages. -- debconf information: imapproxy/imap-server: localhost
--- End Message ---
--- Begin Message ---This was fixed in 1.2.7-1.2: * Disable start of service during postinst, as the upstream imapd may not be available (or even on localhost). (Closes: #829310) -- Richard
--- End Message ---
