At 8:16 PM -0700 9/18/00, Corin Royal Drummond wrote:
> Comrades,
>
> I'm bugged by qpopper. I've compiled it, and installed the recent 3.1 beta
> RPM (from rpmfind.net) for RedHat 6.2. The server responds nicely using
> user/pass authentication, but won't do APOP.
>
> Examining the debugging logs ("-t" cmd line flag) reveals that when Outlook
> 2000 says "AUTH" qpopper responds "+OK Following are Support SASL
> mechanisms". Problem is, it doesn't provide such a list. Outlook gets so
> frustrated by qpoppers obvious duplicity in this matter that the next thing
> it says is "QUIT". In Outlook, I have the "Use secure password
> authentication" box checked. If I uncheck that, and blow away
> /etc/pop.auth, I get all my mail.
>
> Any suggestions would be warmly and greatfully received.
>
> Corin Royal Drummond
> Savage Beast Technologies
> System Administrator
Qpopper does not currently support any standards-track SASL
mechanisms. The list of supported mechanisms (only an early version
of an experimental one: SCRAM) is given in the CAPA response.
However, I recommend not compiling with SCRAM.
I think Outlook may not do APOP. Try a client that supports APOP,
such as Eudora <http://www.eudora.com>.
