Remy Lebeau (TeamB) wrote:
> Older Indy versions required the use of custom OpenSSL DLLs. Did you
> install those files?
As mentioned, only used are:
1. TIdPOP31
2. TIdSSLIOHandlerSocketOpenSSL
3. OpenSSL libraries 0.96 (two DLLs), downloaded from Fulgan and copied
to app. directory.
Implicit SSL works correctly, set trough POP3 component. Other SSL's
types return no error - simply freeze the application.
> Recent updates to Indy 10 allow it to now use the standard OpenSSL
> DLLs instead. No more custom DLLs.
After updating to 10.1.5, application return that cannot load in
directory present OpenSSL libraries. Perhaps is required to copy it to
system32 folder, but that is not prefered currently.
> That likely has nothing to do with Indy.
1. Application with Indy 9 - trigger firewall on first Connect request
2. The same application with Indy 10 - trigger firewall when
application starts
This imply that Indy 10 try to access internet during POP3 component
initialization. Just interested of the cause of it.
> Just saying it doesn't work says nothing at all about the actual
> problem you are having. What EXACTLY is happening?
It frezee the application (upper POP3 example) instead to return an
error. Is there available a simple example of using SASL components
instead of downloading complete 20MB file with 56Kbps DialUp
connection? Onlie documentation page seems to be currently unavailable.
Sasa
--
www.szutils.net
