Rick wrote:
> You could try the old import trick - do https://mail.elisand.com:993 and
> accept the cert in IE. Outlook should then just accept it.
Thanks Rick - that's a neat trick I didn't even know/think about. However,
after trying it (IE7 doesn't seem to let you save invalid certs btw, in m
Nikolay Shopik wrote:
> Usually it works like this. You are configure your mail client to
> address like this mail.example.com, when mail client establish
> connection to server and receive certificate it compare CN with current
> configuration in it. So if you configure connect to mx.example.com b
Hugo Monteiro wrote:
> Ah ... wildcard certs .. from what i recall, certs issued like
> *.example.com were not very well accepted by M$ clients. You should
> test against non wildcard certs and see how it behaves.
Already have and no luck :( My domain is elisand.com and I have tried
*.elisand.com
> Yeah, I throttle initial connections per IP to something like 15 or 20.
> I started doing this after I got hit with a little more than 600
> connections/second for a few minutes.
Just a note to those who might not know - but Outlook (Express) and possibly
other MUAs like to connect once per "acc
