On Qui, 27 Ago 2009, "Robert P. J. Day" wrote:
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:
[snip
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).
Last time I checked, imapproxy didn't do SSL, so if you need imapproxy
your server will have to listen on the standard non-SLL port 143. This
is not really a problem, since imapproxy is on the same machine as the
server. You can restrict the server so that it listens on port 143
only in the local interface, so your server will not be accessible to
outsiders without SSL.
--
Eduardo M KALINOWSKI
edua...@kalinowski.com.br
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
