Re: initial thoughts on 2.1/HEAD - trouble checking mail and otherproblems

[Pawel Salek <pawsa theochem kth se>]

On 04/29/2004 08:42:06 PM, Kacper Wysocki wrote:
> It most certainly did: I found that balsa is trying to talk to my
> server with APOP, even though I explicitly deselected "Use APOP
> authentication" in the account prefs. Here's the full dialog:
> 
> POP S: +OK <joe@blow>
> POP C: CAPA
> POP S: -ERR authorization first
> POP C: APop joe <HEX HASH>
> POP S: -ERR authorization failed
> 
> (values modified to protect the innocent)
> My primary mail account doesn't support APOP, and never has. Makes
> sense that the other account worked, though, as it _only_ works with
> APOP

My reading of RFC2449 is that servers that greet with <...> support  
APOP:
"Clients discover server support of APOP by the presence in the  
greeting banner of an initial challenge enclosed in angle brackets  
("<>").". Also, original POP RFC1939 said:
 "A POP3 server which implements the APOP command will
  include a timestamp in its banner greeting. The syntax of
  the timestamp corresponds to the `msg-id'"

Admittedly, it does not say that the server without APOP MUST not send  
such a greeting although it would seem a common sense....

Therefore, the GUI setting of APOP is currently ignored. It should be  
probably called "Disable APOP no-matter-what". Joys of  
interoperability...

Pawel