🚀 go-pugleaf

"John" <qwertzuiopmiller@web.de> wrote in message
news:42b9cdf2@newsgroups.borland.com...

> But TIdPOP3 has a "APOP" property.

In Indy 9, yes.  In Indy 10, it has been replaced with an AuthType property,
and also an AutoLogin property has been added.

> If it is "false" TIdPOP3 send the username and password in plain
> text, so everyone (hackers, ect.) can read it. If I set the property
> to "true" and the server does not support APOP, the operation fails
> and I get an exception error. I (or the user) have first to deactivate
> APOP manually.

It is your own responsibility to set the APOP property before calling
Connect().  It is your own responsibility to determine whether you want
TIdPOP3 to attempt APOP or not.

The only way to do that in Indy 9 is to set APOP to True, then connect and
catch the exception if APOP is not supported.  If not supported then
disconnect, change the APOP property to False, and reconnect.

In Indy 10, it is a little more streamlined.  You can set AutoLogin to
False, then connect, then parse the Greeting banner, then set the AuthType
accordingly, and then finally call Login().  You do not need to reconnect in
between.  The only downside is that you have to parse the Greeting banner
manually.  If you wait a day or so, the latest development snapshot of Indy
10 will have a new property added that Connect() updates to indicate whether
APOP is supported or not.

> I think, I did not understand you correctly. :-( How or when does
> TIdPOP3 handles APOP automatically?

It automatically determines whether the server actually supports APOP before
sending the APOP command.  But you are still responsible for telling TIdPOP3
whether to use APOP in the first place.


Gambit