Your message dated Sun, 26 Oct 2008 13:45:48 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: imapproxy: Fails to install with error subprocess
post-installation exit status 1
has caused the Debian Bug report #502109,
regarding imapproxy: Fails to install with error "subprocess post-installation
exit status 1"
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.)
--
502109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502109
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: imapproxy
Version: 1.2.6-4
Severity: important
After running "apt-get install imapproxy" the following error occurs:
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
E: Sub-process /usr/bin/dpkg returned an error code (1)
In the log, a CA is missing:
Oct 13 18:15:55 server in.imapproxyd[30472]: main(): Enabling STARTTLS.
Oct 13 18:15:55 server in.imapproxyd[30472]: Initialising 39 pthread_mutexes
Oct 13 18:15:55 server imapd[30474]: Logout user=??? host=localhost [127.0.0.1]
Oct 13 18:15:55 server in.imapproxyd[30472]: main(): Failed to load CA data.
Exiting.
But in the config TLS is set to no force:
force_tls no
I run uw-imap only on localhost for a webmail interface.
Any help would be kind.
Joris
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/bash
Versions of packages imapproxy depends on:
ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy
ii libc6 2.7-13 GNU C Library: Shared libraries
ii libncurses5 5.6+20080830-1 shared libraries for terminal hand
ii libssl0.9.8 0.9.8g-13 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 ---
clone 502109 -1
reassign -1 uw-imapd
retitle -1 uw-imapd advertises TLS even over localhost
severity -1 wishlist
thanks
----------
After (privately) exchanging several e-mails with the reporter, the
cause of the problem was found.
uw-imapd was (incorrectly) advertising the STARTTLS capability *over
localhost*.
imapproxy, upon seeing this capability, engaged in the TLS negotiation.
However, given that the certificate was auto-generated, and no CA certs
/ CA cert path had been given to imapproxy, the negotiation could never
succeed.
The solution in this case was to provide imapproxy with the appropriate
CA certificates, so that it could resolve the certificate trust chain
and complete the negotiation.
Another, much better solution would have been to fix UW-IMAPd to *not*
advertise the STARTTLS capability -- by definition, connections over
localhost can not be eavesdropped in transit. Therefore, TLS over
localhost only imposes an unnecesary overhead.
The next version of imapproxy will, however, include a reference to this
situation in its README.Debian file, so as to prevent future headaches
to our users.
Regards,
J.L.
maintainer of imapproxy
--- End Message ---
