I've been using my spamcop e-mail account for many years now, I really like it a lot! To retrieve my e-mail I've been using the pop.spamcop.net server and about 6 months ago or so I set it to use SSL to connect to that server (using port 995). This has always been working great.

Since a few days, however, my e-mail client (Mozilla Thunderbird 2.0.0.17) is giving me warnings about issues with the SSL certificate for pop.spamcop.net. Is this a known issue, or should I change anything on my end?

Thanks,

Ronald

It looks like about 1 year ago (in September, however), there were also problems with an expired certificate. I am not a client of the email system so I don't know how you would go about sending in a trouble ticket - copied from another topic about other problems with pop servers "have you tried the "Problem" button within SpamCop's Webmail screen? That it the best way recently to get support for the Webmail system." OTOH, an expired certificate should not prevent the email system from working, I understand. If no one else chimes in, then maybe it would be worthwhile to check and make sure nothing has changed on your end.

Miss Betsy

Use "mail.spamcop.net" instead of "pop" and your problem should disappear. The security cert is for "mail" -- not for "pop" and doesn't expire until April 2009.

DT

I'm getting the same problem, with OS X Mail. Changing to "mail.spamcop.net" doesn't help; it still uses the certificate issued to "pop.spamcop.net".

The error isn't expiry. The error is that there is no root certificate. It says:

I checked the keychain, and the only Go Daddy certificate is a different one, for "Go Daddy Class 2 Certification Authority".

I just tested using Thunderbird (2.0.0.0), using both server names (I was examining the certs using HTTPS connections previously). When I used "mail.spamcop.net" and SSL, I got the mismatch error, and saw that it was a GoDaddy cert for "pop," so I switched to "pop.spamcop.net" with SSL and grabbed my messages without an error. My Pegasus client wasn't so picky...it did SSL popping using either hostname without complaining.

I'll try updating my Thunderbird and see if that makes any difference.

[on edit] I updated to 2.0.0.17, restarted Thunderbird and it's happy doing an SSL pop on port 995 of pop.spamcop.net, but if anyone's experience is different than that, they should use the "Problem" report funtion in webmail.

DT

BTW....I was experiencing some "deja vu," so I did a search and came up with this related topic:

Domain name mismatch?

DT

It is working again, for now. Weird.