Page 1 of 1
SSL issues after 4.4 installation; certificate signature failure
Posted: Sat May 13, 2017 7:16 am
by dtemple
I'm sure others have had the same issues, but since updating to 4.4, I can't access *any* of my email accounts. I downloaded and installed the SSL driver pack, but the problem persists. Here are the errors - would appreciate any help you can provide.
--- Version ---
OS: Windows 10 (x64)
POP Peeper: 4.4.0.0
Webmail: 4.4.0.0
SSL: 0.9.8.10
IMAP: 4.4.0.0
SendMail: 4.4.0.0
Profile Picture: 4.2.0.0
AntiJunk: 4.2.0.0 (disabled)
Spell Checker: 4.2.0.0 (disabled)
Web of Trust: 4.2.0.0 (disabled)
--- Web Test ---
Result: 200
Error:
Time: 07:03:24 - 07:03:24 (0 s) (-0400)
Data: Sat, 13 May 2017 04:03:18 -0700
--- Error ---
Gmail [0: POP3] ['pop3.gmail.com' (995) SSL: 1] [ClientSend: '' (0) SSL: 0] [Consec: 2]
- Unknown Host
Hotmail [0: POP3] ['pop-mail.outlook.com' (995) SSL: 1] [Smtp: 'smtp-mail.outlook.com' (587) SSL: 2] [Consec: 1]
- SSL connection failed (certificate failed: certificate signature failure (7))
ACCOUNT1 @verizon.net [0: POP3] ['pop.verizon.net' (995) SSL: 1] [Smtp: 'smtp.verizon.net' (465) SSL: 1] [Consec: 1]
- SSL connection failed (certificate failed: certificate signature failure (7))
ACCOUNT2 @verizon.net [0: POP3] ['pop.verizon.net' (995) SSL: 1] [Smtp: 'smtp.verizon.net' (465) SSL: 1] [Consec: 1]
- SSL connection failed (certificate failed: certificate signature failure (7))
Re: SSL issues after 4.4 installation; certificate signature failure
Posted: Sat May 13, 2017 8:05 am
by spc3rd
Welcome to the Esumsoft Forums,
dtemple!
Sorry to hear of the issues you're experiencing and
thank you for providing the detailed information in your post! Rest-assured
The Esumsoft Team is looking into your problems, and we will help you get them resolved!
* I edited the portion of your email addresses shown before the "
@" symbol. This is for your security/privacy and to prevent harvesting by spambots.
(See Forum Rule # 7).
I also revised your topic title slightly to better specify the particular issue you're having.
[SIDENOTE # 1]: You indicated having downloaded the
SSL plugin
(driver pack). However, the SSL version shown in your topic is not the current version (which is
1.0.2.11). You can download the current version from
HERE, at your convenience. (Though, I do not believe this is the actual, sole cause of the issues you are having).
[SIDENOTE # 2]: In the error message shown for your
Gmail POP3 account, the "
Incoming Server"
(highlighted in red font) does not appear to be correct. Please see the information about the correct settings at the following
FAQ link:
http://www.esumsoft.com/products/pop-pe ... =GMailPop3
In the interim, while awaiting further feedback from other team members,
please take a few moments to review the following Sticky topic:
Information for new users and forum members.
It provides important information & resources about the Forums and the POP Peeper program which we recommend all new forum members read.
Thank you & best regards,
Re: SSL issues after 4.4 installation; certificate signature failure
Posted: Sat May 13, 2017 11:09 am
by dtemple
Pete, thank you for your reply. I did download the SSL plugin, but the error messages were generated before rather than after installing the plugins. I also enabled POP in GMail; now I get the same error message for GMail that I do for all other accounts (Gmail SSL connection failed (certificate failed: certificate signature failure (7)).
I did review FAQs and Help section before posting here; I do hope the problem can be solved, as I appreciate the features of PP and hope to keep using it.
Thanks again,
Dena
Re: SSL issues after 4.4 installation; certificate signature failure
Posted: Sat May 13, 2017 11:13 am
by mjs
dtemple wrote:
Gmail [0: POP3] ['pop3.gmail.com' (995) SSL: 1] [ClientSend: '' (0) SSL: 0] [Consec: 2]
- Unknown Host
Hotmail [0: POP3] ['pop-mail.outlook.com' (995) SSL: 1] [Smtp: 'smtp-mail.outlook.com' (587) SSL: 2] [Consec: 1]
- SSL connection failed (certificate failed: certificate signature failure (7))
ACCOUNT1 @verizon.net [0: POP3] ['pop.verizon.net' (995) SSL: 1] [Smtp: 'smtp.verizon.net' (465) SSL: 1] [Consec: 1]
- SSL connection failed (certificate failed: certificate signature failure (7))
ACCOUNT2 @verizon.net [0: POP3] ['pop.verizon.net' (995) SSL: 1] [Smtp: 'smtp.verizon.net' (465) SSL: 1] [Consec: 1]
- SSL connection failed (certificate failed: certificate signature failure (7))
The top error is because the Server name ("Incoming server" setting) should be "pop.gmail.com" (not "pop3.gmail.com" which will produce the "- Unknown Host" error).
Changing the "Incoming server" to "pop.gmail.com" should clear up the "Unknown Host" error.
Also I notice that this "Unknown Host" error (which will remain persistent until the Server name is changed to the proper "pop.gmail.com" had occurred twice as of the time you captured the error information (based on "Consec: 2") however on the other hand the "SSL connection failed" errors did not apparently occur on the prior Mail Check.
So I am wondering if those "SSL connection failed" errors have remained persistent or have they cleared up?
Please report back if these errors have continued to occur on a regular basis.
If the "SSL" errors have remained persistent for help on how PPv4.4 handles SSL Certificate verification from the main PP menu go to "Tools" > "PPtweaker...", select the "Certificates" tab and press the "Help (F1)" button, click on the URL link (blue underlined link) which will take you to the FAQ on this topic.
Note: if you decide to disable (uncheck) "local SSL certificate verification",
this should only be TEMPORARY until Jeff can look into this further as your email is not secure when you do this.
Re: SSL issues after 4.4 installation; certificate signature failure
Posted: Sat May 13, 2017 11:33 am
by mjs
dtemple wrote:Pete, thank you for your reply. I did download the SSL plugin, but the error messages were generated before rather than after installing the plugins. I also enabled POP in GMail; now I get the same error message for GMail that I do for all other accounts (Gmail SSL connection failed (certificate failed: certificate signature failure (7))....
Based on your reply the "SSL certificate" errors are apparently persistent.
I cannot test for your verizon accounts so
Jeff will need to look into the "SSL Certificate" issues for these accounts.
As to the Gmail and Hotmail accounts they should work with the following POP3 settings (tested in both cases) with no errors...
Gmail:
Hotmail:
Re: SSL issues after 4.4 installation; certificate signature failure
Posted: Sat May 13, 2017 11:40 am
by dtemple
Yes, the error persists. All email accounts show a consec error of 7 now. I am reluctant to disable the SSL security, so I will wait for an alternate solution and use webmail in the meantime. I may also try deleting the accounts and starting over, to see if that fixes the problem. You never know.
Thanks, Dena
Re: SSL issues after 4.4 installation; certificate signature failure
Posted: Sat May 13, 2017 12:03 pm
by dtemple
Well, I did hear from Jeff who was very helpful, but unfortunately his solution didn't work, either. So I tried the next logical step: I deleted all my email accounts in Pop Peeper, and tried adding them as new. The first account seems to be working properly, so happy ending! While I can't say why it wasn't working, this seems to have worked for me.
Thanks for all your help,
Dena
Re: SSL issues after 4.4 installation; certificate signature failure
Posted: Sat May 13, 2017 12:26 pm
by Jeff
Dena, glad to hear things are working again.
Here's some general information, since this may be a common issue:
The error "SSL connection failed (certificate failed: certificate signature failure (7))" is the error you'll see with an out-dated SSL plugin because the 0.9 versions didn't support the feature that POP Peeper v4.4 uses (however, an out-dated SSL may not be the *only* reason for that error). I believe the functionality was added somewhere in SSL v1.0.0.x (I'm not sure of the exact version; I tested it with v1.0.0.4/d and it appears to work).
I regret not foreseeing this potential problem and the installer should have defaulted to updating the SSL plugin. This will be addressed.