Your message dated Tue, 18 Nov 2008 23:27:22 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#505828: "apt-get install imapproxy" cannot install
imapproxy
has caused the Debian Bug report #505828,
regarding "apt-get install imapproxy" cannot install imapproxy
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.)
--
505828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505828
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: imapproxy
Version: 1.2.6-4
Severity: important
*** Please type your report below this line ***
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)
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.27.1 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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.22 Debian configuration management sy
ii libc6 2.7-15 GNU C Library: Shared libraries
ii libncurses5 5.6+20080830-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 ---
lee wrote:
> On Sat, Nov 15, 2008 at 11:35:52PM +0100, José Luis Tallón wrote:
>
>> [snip]
>>
>>> -- debconf information:
>>> imapproxy/imap-server: localhost
>>>
>> I strongly suspect that you don't had an IMAP server running on
>> localhost at the time when you installed imapproxy.
>>
>
> No, I don't have an IMAP server running on localhost.
That is why it fails.
You told it to connect to localhost (see debconf answer above)
> I wanted to try out imapproxy with mutt
[snip Mutt's broken IMAP handling]
> As far as I understand the description and documentation of imapproxy,
> its purpose is to keep connections to a *remote* IMAP server open,
>
from imapproxy's description:
"UP-ImapProxy proxies IMAP transactions between an IMAP client and an IMAP
server."
"ImapProxy was written to compensate for webmail clients [...]"
Again, where does it say "remote" ?
How is mutt a webmail client ?
> Imapproxy is supposed to be able to create secure
> connections with remote IMAP servers and unencrypted connections to
> the local webmail clients,
It does, indeed. That's how I use it, along many other users.
> which also indicates that you don't need an IMAP server on localhost to use
> it.
>
Of course, but you configured it (via debconf) to look for the IMAP
server at localhost.
Please do "dpkg-reconfigure" -plow imapproxy and/or purge and reinstall.
> Anyway, it seems that the package was installed, but not
> configured.
The daemon failed to start, and so configuration failed (as it is
supposed to)
> I'm guessing that there is some mistake in the package
> that leads to abort the installation in the configuration phase.
The packaging seems to be fine right now, AFAICS
> That
> is unusual, considering that packages requiring (manual) configuration
> usually are installed and configured without causing the package
> manager to abort with an error.
>
The postinstallation script performs the minimal configuration needed to
allow imapproxyd to start (provided the user gave proper input). The
it's up to the user to fine-tune it (e.g. configure the certificate
location so that TLS can be negotiated)
Hope this solves your question.
Regards.
J.L.
imapproxy maintainer
--- End Message ---
