SSL certificates for secure mail not valid?

[matt connolly]

I just tried setting up my mail client (Mac OS X Mail) with me new account here at bluehost.

Mail reports that when I try to connect via SSL that the SSL certificate on "box198.bluehost.com" could not be verified or trusted.

Have I got something wrong here?

Also, what is the correct port to use for sending mail with authentication for SMPTS?

Matt

[Early Out]

Unless I've missed something, BH does not support SSL for POP email. You use port 110 for receiving, and either port 25 or port 26 for outgoing. It does support user authentication on the SMTP side, of course, but that has nothing to do with SSL.

[matt connolly]

Well, I can check the SSL option in my incoming mail preferences:

http://www.soundevolution.com.au/xyz/pop_settings.png

And then I see this error message:

http://www.soundevolution.com.au/xyz/mail_ssl_warning.png

Is this because the certificate is for "box198.bluehost.com" and I'm connecting to "mail.soundevolution.com.au" which is the same machine but via a different name?

If I click the "Continue" button, it works, and I download mail correctly. I'm just wondering what the error message is all about...

[Evil_Dictator]

The error message just means the cert is written for your box and not for your domain name. (i.e. written for box198.bluehost.com instead of your www.yourdomainname.com ) The certificate will still work 100% securely, you'll just get more warnings. To lessen those warnings, you can try setting your the mailservers you're using to box198.bluehost.com for incoming and outgoing.