Chad1

Just a follow-up, for anyone who cares: so far as I can tell, this problem is now fixed. TCH's level-two support contacted me yesterday afternoon to say that they believed they'd gotten it, and this morning the certificate was still the same as yesterday's, so they're probably right. I'll keep an eye on it over the next few days, but it looks like it's all good.

I'm afraid that the problem continues. Every morning, starting on the fifth of January, the SMTP certificate claims that it was issued that same day. I switched e-mail programs yesterday (I'm now using Thunderbird), but this morning when I tried to send a message, it said: "Alert: You have received an invalid certificate. Please contact the server administrator or email correspondent and give them the following information: Your certificate contains the same serial number as another certificate issued by the certificate authority. Please get a new certificate containing a unique serial number." This is probably the same thing that The Bat was complaining about. I'll open a ticket for this.

Curious... I'd rather not dump The Bat! just yet, I haven't found anything that's as good or better. Looking at the log, it seems that the valid-from date on the certificate has changed each day, which does strongly suggest that the certificate has changed too. If the problem continues, I'll report back.

I've been using secure POP and SMTP with my TCH account for a couple months now, and I've been quite happy with it, knowing that my account password and e-mail contents are safe from prying eyes between me and the server. But over the past three days, the SMTP certificate (on server320) has been changed three times. My e-mail program, The Bat!, sees the changes and refuses to send mail because of what it calls a "key material mismatch". Is there something wrong with the certificates, that they have to keep being replaced? Does anyone know if this is going to continue for a while?