Patrique Wolfrum wrote:
I compiled fetchmail wih SSL-Support (openssl 0.9.6b-18 (installed via
Redhat RPM)), and when it fetches mails from my GMX-account (via SSL), it
works fine. But when it tries to fetch mails from my university account,
which can only be accessed via SSL, I get the following error message via
'fetchmail -v -v':
POP3< +OK Communicate Pro POP3 Server 3.4.7 ready
POP3< +OK capability list follows
POP3< SASL LOGIN PLAIN CRAM-MD5 DIGEST-MD5
POP3< IMPLEMENTATION Communicate Pro
POP3< -ERR already secured
SSL connection failed
It looks to me like fetchmail is connecting through SSL to start with
(via port 995), then seeing STLS listed in the capabilities and trying
to use it to (redundantly) encrypt the rest of the session.
It would help if you would show us your .fetchmailrc.
I don't think a server is supposed to advertise STLS as a capability
if the connection is already secure, but I also don't think fetchmail
should try to use STLS if the connection is already secure, so I'd say
they're both broken.
Surprisingly, with fetchmail 5.9.8 it works just fine.
==============================| "A microscope locked in on one point
Rob Funk <rfunk(_at_)funknet(_dot_)net> |Never sees what kind of room that
http://www.funknet.net/rfunk | -- Chris Mars, "Stuck in Rewind"