* Matt Kraai
| > It seems my pop3 server does not like the `CAPA' query (in fact, it
| > closes the connection on anything it does not like). Who is to blame?
| > Micro$oft again (I think this is a microsoft pop3 server at the other
| > end)? I can't find any reference to CAPA in rfc 1725, so I'm not
| > sure.
|
| If you add `auth password' to your .fetchmailrc, it won't send
| `CAPA'.
Yes, I found that in the meantime. _After_ I have logged in with
user/pass, the server responds to CAPA fine:
% telnet mail.t-intra.de pop3
Trying 62.156.147.75...
Connected to mail.t-intra.de.
Escape character is '^]'.
+OK POP3Proxy server ready version 1.2.903.29791
user x
+OK user
pass x
+OK User successfully logged on.
capa
+OK Capability list follows
TOP
USER
PIPELINING
EXPIRE NEVER
UIDL
SASL NTLM
.
quit
+OK POP3Proxy signing off
I'm curious what is the proper protocol proceedings here, since we
have access problems using other clients (netscape, eudora) too. The
ISP (german telekom) is currently busy answering zillions of service
requests after they introduced the new pop server :-/
R'