Here's a little problem i have with fetchmail 6.2.3 on gentoo linux (gcc 3.2.2):
I use it to poll 4 servers for mail. Only one of them supports TLS.
The problem is: If the server supporting TLS is not the last one polled,
fetchmail tries TLS on the next server, too
(which doesn't support it). This is not a severe bug, but causes an annoying
message..
sample session output which exposes the bug:
[ .. querying 2 non-TLS servers successfully .. ]
fetchmail: 6.2.3 querying webmail.hansenet.de (protocol POP3) at Fri Oct 3
00:06:17 2003: poll started
fetchmail: POP3< +OK POP3 server ready (6.7.015)
<18EBB0DEFAF7AD8835661A601E7C7CB55E1EAC0F(_at_)webmail(_dot_)hansenet(_dot_)de>
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Capability list follows
fetchmail: POP3< TOP
fetchmail: POP3< RESP-CODES
fetchmail: POP3< STLS
fetchmail: POP3< USER
fetchmail: POP3< SASL CRAM-MD5 DIGEST-MD5 PLAIN
fetchmail: POP3< PIPELINING
fetchmail: POP3< UIDL
fetchmail: POP3< IMPLEMENTATION InScribe-6.7.015
fetchmail: POP3< AUTH-RESP-CODE
fetchmail: POP3< .
fetchmail: POP3> STLS
fetchmail: POP3< +OK begin TLS negotiation
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Capability list follows
fetchmail: POP3< TOP
fetchmail: POP3< RESP-CODES
fetchmail: POP3< USER
fetchmail: POP3< SASL CRAM-MD5 DIGEST-MD5 PLAIN
fetchmail: POP3< PIPELINING
fetchmail: POP3< UIDL
fetchmail: POP3< IMPLEMENTATION InScribe-6.7.015
fetchmail: POP3< AUTH-RESP-CODE
fetchmail: POP3< .
fetchmail: POP3> AUTH CRAM-MD5
fetchmail: POP3< +OK 0 messages
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: POP3> QUIT
fetchmail: POP3< +OK POP3 server closing connection
fetchmail: 6.2.3 querying webmail.hansenet.de (protocol POP3) at Fri Oct 3
00:06:21 2003: poll completed
fetchmail: 6.2.3 querying pop.kundenserver.de (protocol POP3) at Fri Oct 3
00:06:21 2003: poll started
fetchmail: POP3< +OK POP3 server ready
fetchmail: POP3> CAPA
fetchmail: POP3< +OK capability list follows
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< UIDL
fetchmail: POP3< PIPELINING
fetchmail: POP3< .
fetchmail: POP3> STLS
fetchmail: POP3< -ERR not supported
fetchmail: not supported
fetchmail: POP3> CAPA
fetchmail: POP3< +OK capability list follows
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< UIDL
fetchmail: POP3< PIPELINING
fetchmail: POP3< .
fetchmail: POP3> AUTH CRAM-MD5
fetchmail: POP3< -ERR not supported
fetchmail: could not decode BASE64 challenge
fetchmail: POP3> USER XXXXXXX
fetchmail: POP3< +OK
fetchmail: POP3> PASS
fetchmail: POP3< +OK
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: POP3> QUIT
fetchmail: POP3< +OK
fetchmail: 6.2.3 querying pop.kundenserver.de (protocol POP3) at Fri Oct 3
00:06:24 2003: poll completed
apparently, fetchmail "remembers", that it can use TLS. if i reverse the server
order, it doesn't try STLS /
AUTH CRAM-MD5 on that server.
cheers,
robert