in reply to Pop3client.pm win vs. linux

Given the warning you show on the (working) Windows version and that you don't get the warning on the non-working Linux version I guess that you are using a very old version of IO::Socket::SSL on Windows which by default does not check any certificates while your Linux version is newer and does check certificates. The warning you see in Windows was removed about 4 years ago when the switch was made to checking certificates by default.

This leaves you with the following options to deal with the problem: The best way is to add the proper trust settings by specifying the issuer certificate with the SSL_ca_file option or use SSL_fingerprint option in newer versions of IO::Socket::SSL to just trust a specific certificate. The bad way is to ignore any security and simply disable certificate checking by setting SSL_verify_mode to 0 (SSL_VERIFY_NONE).

Replies are listed 'Best First'.
Re^2: Pop3client.pm win vs. linux
by Anonymous Monk on Apr 03, 2017 at 16:45 UTC
    thank you noxxi !! I hacked in the old win ActiveState IO::Socket::SSL.pm into the linux dist. This communication path happens inside a secure network, so I am not worried (yet) about the insecure nature. Thanks again.