in reply to Net::SMTP::SSL on Windows 8

Greetings, DanEllison. If I had to guess. I'd say it didn't pass the Sniff Test.

Judging from the informative debugger output. It seems fairly obvious; the certificate is bad -- has perhaps expired, isn't signed in a way IO::Socket::IP, or Net::SMTP::SSL considered acceptable (wildcard, self signed,...). Have you tried it with your Browser, or mail reader? What/How does the certificate read there? Any indications, as to the failure there (assuming they don't also reject the cert)?

Just my initial thoughts, given the information you've provided.

Best wishes.

--Chris

#!/usr/bin/perl -Tw
use Perl::Always or die;
my $perl_version = (5.12.5);
print $perl_version;

Replies are listed 'Best First'.
Re^2: Net::SMTP::SSL on Windows 8
by DanEllison (Scribe) on Jan 25, 2014 at 17:10 UTC

    Yes, sure, the problem is obvious. The solution is what seems non-existent.

    I started with notes I found for sending e-mail out through gmail. godaddy works similarly. I didn't have to install any certificate before.

    The more I read, it may not be a difference in windows versions, but possibly a change in IO::Socket::SSL that may be requiring me to install a certificate that I hadn't before. But where? Which certificate? If I need to supply an option to IO::Socket::SSL to identify the certificate, how do I do that via Net::SMTP::SSL, since I don't work with IO::Socket::SSL directly?

      I have now confirmed it. I had IO::Socket::SSL version 1.953 installed. I re-installed version 1.76, and everything started working as before. So, what does the new version need?
        So, what does the new version need?

        Searching the Changes file for "certificate" might turn up something helpful.
        For example, I see that there are two "MAJOR BEHAVIOR CHANGE" announcements (for 1.950) in relation to certs.

        Cheers,
        Rob
        With 1.950 IO::Socket::SSL switched the default from "no certificate verification" to "require verification", after 3 years of complaining (since 1.79) if you used the insecure default of no verification. It also uses the default location for the certificates provided by the openssl installation.

        On windows there are probably no certificates installed in a form usable by openssl, so you have to do it by your own. You might use Mozilla::CA and then set the SSL_ca_file like documented there.