"Sasa Zeman" <public@szutils.net> wrote in message
news:xn0el8rfk3co16001@newsgroups.borland.com...
> I begin to using Indy 10 (indy10.0.52_source.zip) instead
> of Indy 9 (9.0.14) in order to use SSL/TLS and POP3 client.
10.0.52 is an old version. You should consider using the current 10.1.5
snapshot instead.
> Used components are TIdSSLIOHandlerSocketOpenSSL
> and TIdPOP31 only. It is used additionally provided
> OpenSSL libraries (ver. 0.96).
Older Indy versions required the use of custom OpenSSL DLLs. Did you
install those files?
Recent updates to Indy 10 allow it to now use the standard OpenSSL DLLs
instead. No more custom DLLs.
> Even without SSL IO Handler components, application with POP3
> component trigger firewall immediately after application runs - not
> after first attempt to connect. Assume this is normal behavior for Indy
> 10.
That likely has nothing to do with Indy.
> While using SSL/TLS, implicit approach only works. Other
> possibilities (explicit or reqired TLS) are not functioning
Just saying it doesn't work says nothing at all about the actual problem you
are having. What EXACTLY is happening?
> or there is need to use some other component.
Did you attach any SASL components to the TIdPOP3? What did you assign to
the AuthType property?
> Is there available main difference comparison page between
> Indy 9 and current version of Indy 10?
No.
Gambit
