as a followup to a post from a few days back, i still can't get
imapproxy installed and configured on this (fully-upgraded) lenny
system. every attempt to "aptitude safe-upgrade" produces:
... snip ...
The following partially installed packages will be configured:
imapproxy
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Setting up imapproxy (1.2.6-5) ...
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)
A package failed to install. Trying to recover:
Setting up imapproxy (1.2.6-5) ...
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
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
some googling produced this
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512369
which suggests that imapproxy won't install successfully if it can't
connect to a running IMAP server on port 143. but it certainly seems
that there's an imap server out there listening:
# netstat -a | grep imap
tcp 0 0 *:imaps *:* LISTEN
tcp 0 0 *:imap2 *:* LISTEN
tcp 0 0 192.168.169.10:imaps inet:3969
ESTABLISHED
tcp 0 0 192.168.169.10:imaps inet:3738
ESTABLISHED
tcp 0 0 192.168.169.10:imaps inet:2694
ESTABLISHED
tcp 0 0 192.168.169.10:imaps inet:3490
ESTABLISHED
tcp 0 0 192.168.169.10:imaps inet:1136
ESTABLISHED
#
does the above suggest that the proxy should be trying to connect
to the imaps port instead (still getting my head around imap stuff).
the line from /etc/imapproxy.conf reads:
server_port 143
should i change that to 993 (for imaps) and try again? i'm definitely
puzzled by this one. everything else on the system seems to be
running fine (fingers crossed).
rday
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
