On Tue, 3 Feb 2004, ml wrote: > I suspect, the problem is that upon seeing the "+OK <blah blah blah>" > greetings from the pop3 server, c-client will issue a "CAPA" command. In > response to that, the server would say: > +OK capability list follows > PIPELINING > TOP > UIDL > APOP > .
This server is saying that it does not support plaintext password USER/PASS authentication, but it does support APOP authentication. The c-client library does not support APOP, as APOP has been deprecated in favor of SASL based authentication. The SASL equivalent to APOP would be "AUTH CRAM-MD5". Are you certain that the server will accept a USER/PASS authentication? The CAPA response says that it will not. Your patch will work to force c-client to send USER/PASS even if the server says that it does not support it. This would be a bad thing if it turned out that the server didn't really support USER/PASS. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum.
