Sonic.net

Graham, a quick fix would be to change your hosts file in Windows to point imapd at imap so the certificate will not have a name mis-match, an entry like this should do it:

69.12.218.40 imap.sonic.net

Not sure which version of Windows you are on, but this post should help:

http://www.windowsreference.com/windows ... ows-vista/

Long term, maybe we'll just bite the bullet and purchase a valid certificate for imapd.sonic.net.

augie wrote:Long term, maybe we'll just bite the bullet and purchase a valid certificate for imapd.sonic.net.

How about a wildcard cert? If you have enough different certs, it'll probably save a couple bucks too.

It would save us a little but but I'm not particularly enthusiastic about the added security risks of having a wildcard cert on *.sonic.net. If we had a security incident on the forums or wiki servers, for example, I wouldn't want the attacker to be able to take the cert and put get a transparent proxy up on pop.sonic.net or imap.sonic.net