Improved IMAP Server BETA.

Advanced feature discussion, beta programs and unsupported "Labs" features.
33 posts Page 4 of 4
by augie » Fri Jun 22, 2012 2:40 pm
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.
by toast0 » Sat Jun 23, 2012 10:05 pm
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.
by kgc » Mon Jun 25, 2012 2:41 pm
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
Kelsey Cummings
System Architect, Sonic.net, Inc.
33 posts Page 4 of 4

Who is online

In total there are 141 users online :: 0 registered, 0 hidden and 141 guests (based on users active over the past 5 minutes)
Most users ever online was 999 on Mon May 10, 2021 1:02 am

Users browsing this forum: No registered users and 141 guests