Yahoo error - SSL connection failed (certificate failed: certificate has expired (10))

[Bronson]

Good morning Gents...new error started yesterday. I'm able to login to the website, but keep getting this:

--- Version ---
OS: Windows 10 (x64)
POP Peeper: 4.4.0.0
Webmail: 4.4.1.0
SSL: 1.0.2.8
IMAP: 4.4.0.0
SendMail: 4.4.0.0
Profile Picture: 4.3.0.0
AntiJunk: 4.4.0.0 (disabled)
Spell Checker: 4.4.0.0 (disabled)
Web of Trust: 4.4.0.0 (disabled)

--- Web Test ---
Result: 200
Error:
Time: 08:40:30 - 08:40:30 (0 s) (-0400)
Data: Mon, 26 Jun 2017 05:40:29 -0700

--- Error ---
Yahoo [1000: IMAP] ['imap.mail.yahoo.com' (993) SSL: 1] [Smtp: 'smtp.mail.yahoo.com' (465) SSL: 1] [Consec: 1]
- SSL connection failed (certificate failed: certificate has expired (10))

[mjs]

Good morning Bronson, thanks for posting your error information.

You could first try updating your SSL plugin to the current v1.0.2.11.

If no help there, please take a look at THIS post by Jeff (click on link in the last post in topic) regarding a patch that you will notice specifically "addresses the issue where some users experience a 'certificate has expired' error on certain IMAP/POP servers (notably: Yahoo)".

Please post back in this topic to let us know your results as far as which of these two options fixes the problem (most likely the 2nd option will do the trick ).

Please refer to Jeff's post below, the changes in the Beta release (referenced and struck-out above) has been incorporated into the current POP Peeper 4.4.2 production release.

[Jeff]

Download POP Peeper v4.4.2 and this will fix the problem:
https://www.esumsoft.com/download/

btw, the "beta" that lakrsrool referred to has just been removed since it has been superseded by v4.4.2 -- if you've already downloaded it, you should be ok.

[Bronson]

Ok Thanks guys I download the second option that lakrsrool provided earlier and that worked. I didn't have a chance to reply But thank you very much. So I guess I'm ok for now...
Thanx !!!

[mjs]

You're okay for now (at least until the next PM release --- (I wasn't sure, but Jeff has pointed out, what was in the beta release regarding this issue was incorporated into the 4.4.2 release)

Thanks for the reply.