Hi,
lately I had some problems with fetchmail and the new STLS feature. Because
with a qpopper server at hand, it just didn't work. When I did some "-vv",
I was surprised that fetchmail never sent a CAPA to qpopper. So I went and
read some lines in pop3.c where the STLS/CAPA stuff is detailed:
[...]
:: if (ctl->server.authenticate == A_ANY
:: && strchr(greeting, '<')
:: && gen_transact(sock, "CAPA") == 0)
:: {
[...]
Mmmh. Why does it expect a '<'? AFAIK "POP3 Extension Mechanism" (RFC 2449,
where CAPA is defined) and "APOP" (a server advertises its APOP functionality
by having a "<"-some-number-">" in its banner) are not tied that closely to-
gether, are they? Some server - e.g. the qpopper at hand - may do CAPA but
not APOP and vice versa. At least I did not find anything stating "APOP is
required for CAPA to work" in RFC 2449.
Or am I completely stumbling over my feet here? I did not see something about
this at the bugs page or in list archives, so I hope this is a not-so-stupid
question.
What I used:
fetchmail-5.9.11 on a RH-7.1 box /w kernel 2.4.2. (self compiled with
gcc version 2.96 20000731) On the other side of the table qpopper-4.0.3
with STLS:
:: $ telnet 10.10.10.10 110
:: Trying 10.10.10.10...
:: Connected to 10.10.10.10.
:: Escape character is '^]'.
:: +OK Qpopper (version 4.0.3) at 10.10.10.10
:: CAPA
:: +OK Capability list follows
:: TOP
:: USER
:: LOGIN-DELAY 0
:: EXPIRE 0
:: UIDL
:: RESP-CODES
:: AUTH-RESP-CODE
:: X-MANGLE
:: X-MACRO
:: X-LOCALTIME Thu, 2 May 2002 17:34:51 +0200
:: STLS
:: IMPLEMENTATION Qpopper-version-4.0.3
Regards,
Birger