I am getting an error after upgrading similar to others. Mine is as follows:
-
--- Version ---
OS: Windows 7 (x64)
POP Peeper: 4.4.1.0
Webmail: 4.4.4.0
SSL: 1.0.2.11
IMAP: 4.4.0.0
SendMail: 4.4.0.0
Spell Checker: 4.4.0.0
--- Error ---
removed@fop.net [0: POP3] ['email.fop.net' (995) SSL: 1] [Smtp: 'email.fop.net' (587) SSL: 1] [Consec: 1]
- SSL connection failed (certificate failed: unable to get local issuer certificate (20))
-
This, obviously, is the FOP and this account was working great before the upgrade.
Also getting the "SSL connection failed" error
Re: Also getting the "SSL connection failed" error
This issue has to do with the extra SSL certificate verification security that was added to POP Peeper v4.4 likely caused by a missing FOP account SSL certificate.
As a result of this you will probably have to do what is described below in the next paragraph but you could try following the POINT #3 steps in the topic POP Peeper v4.4: Common issues (and solutions) to see if this helps Note: because this would have been done when updating to PPv4.4.1 it is likely that you will need to add certificate exceptions for now, referenced below.
Because the above approach will most likely not help (specifically in the case of FOP.net accounts), it may for now be necessary to add a certificate exception for this FOP account by going to "Tools" > "PPtweaker" > "Certificates" where you will need to add the incoming and outgoing Server names (probably "pop.fop.net" or "mail.fop.net") that FOP.net uses and then retest your account(s) or if FOP.net accounts are the ONLY accounts you use in POP Peeper you could alternately disable (uncheck) "Enable local SSL certificate verification" temporarily in this same interface. Note: this solution bypasses the additional security that was added in v4.4. If this is what was needed to get your FOP.net account(s) to work in POP Peeper then Jeff will be looking into this as far as addressing SSL certification verification issues regarding FOP accounts at which time perhaps you can then enable certificate verification again by undoing what you did.
If after doing the above you continue to have problems, what is the data path where you are installing POP Peeper?
As a result of this you will probably have to do what is described below in the next paragraph but you could try following the POINT #3 steps in the topic POP Peeper v4.4: Common issues (and solutions) to see if this helps Note: because this would have been done when updating to PPv4.4.1 it is likely that you will need to add certificate exceptions for now, referenced below.
Because the above approach will most likely not help (specifically in the case of FOP.net accounts), it may for now be necessary to add a certificate exception for this FOP account by going to "Tools" > "PPtweaker" > "Certificates" where you will need to add the incoming and outgoing Server names (probably "pop.fop.net" or "mail.fop.net") that FOP.net uses and then retest your account(s) or if FOP.net accounts are the ONLY accounts you use in POP Peeper you could alternately disable (uncheck) "Enable local SSL certificate verification" temporarily in this same interface. Note: this solution bypasses the additional security that was added in v4.4. If this is what was needed to get your FOP.net account(s) to work in POP Peeper then Jeff will be looking into this as far as addressing SSL certification verification issues regarding FOP accounts at which time perhaps you can then enable certificate verification again by undoing what you did.
If after doing the above you continue to have problems, what is the data path where you are installing POP Peeper?
Good judgment comes from experience and a lot of that comes from bad judgment. - Will Rogers
Re: Also getting the "SSL connection failed" error
I read that topic before I posted my question and tried adding the file provided and it did not work.lakrsrool wrote:As a result of this you will probably have to do what is described below in the next paragraph but you could try following the POINT #3 steps in the topic POP Peeper v4.4: Common issues (and solutions) to see if this helps Note: because this would have been done when updating to PPv4.4.1 it is likely that you will need to add certificate exceptions for now, referenced below.
I was not aware of this option. This did the trick. Thank you very much. I realize this is just a workaround but it works fine. Thank you.Because the above approach will most likely not help (specifically in the case of FOP.net accounts), it may for now be necessary to add a certificate exception for this FOP account by going to "Tools" > "PPtweaker" > "Certificates" where you will need to add the incoming and outgoing Server names (probably "pop.fop.net" or "mail.fop.net") that FOP.net uses and then retest your account(s) or if FOP.net accounts are the ONLY accounts you use in POP Peeper you could alternately disable (uncheck) "Enable local SSL certificate verification" temporarily in this same interface. Note: this solution bypasses the additional security that was added in v4.4. If this is what was needed to get your FOP.net account(s) to work in POP Peeper then Jeff will be looking into this as far as addressing SSL certification verification issues regarding FOP accounts at which time perhaps you can then enable certificate verification again by undoing what you did.
By data path do you mean where is it installed on my machine? If so then that is:If after doing the above you continue to have problems, what is the data path where you are installing POP Peeper?
C:\Program Files (x86)\POP Peeper\POPPeeper.exe
Re: Also getting the "SSL connection failed" error
Sentinel -- I've looked into your server and I've just updated the certificate file to include Go Daddy's SSL certificate, and this should allow it to work without having to use an exception.
Please re-download and install the cacert.pem file from:
viewtopic.php?f=2&t=6846&p=34501#p34501
and be sure to disable the exception (you can put an 'X' or something in front of it to neutralize the exception to check that it works first; e.g. Xemail.fop.net; if, after testing, it does work, then you can go ahead and delete the exception entirely)
Let us know if that works or not.
Please re-download and install the cacert.pem file from:
viewtopic.php?f=2&t=6846&p=34501#p34501
and be sure to disable the exception (you can put an 'X' or something in front of it to neutralize the exception to check that it works first; e.g. Xemail.fop.net; if, after testing, it does work, then you can go ahead and delete the exception entirely)
Let us know if that works or not.
Re: Also getting the "SSL connection failed" error
Worked perfectly.
Thank you. Very much appreciated.
Thank you. Very much appreciated.