IMAP SSL Outgoing Issues - Mac Mail

[phlegma]

Hey everybody,
I've posted some pictures in hopes of resolving my outgoing IMAP SSL issues. I've tried using logins with both @, and +. Also tried outgoing server port 26. Ports 465, 26 and 993 are mapped on my Airport Router.

http://www.pirouettesdancewear.com/email/1.png

http://www.pirouettesdancewear.com/email/2.png

http://www.pirouettesdancewear.com/email/3.png

http://www.pirouettesdancewear.com/email/4.png

[breakingball]

Recreate the account.

The username for this account should be info@pirouettesdancewear.com. In Mail.app, Usernames should always be the full email address.

Your Incoming and Outgoing Mail Servers should both be mail.pirouettesdancewear.com

box383.bluehost.com should not appear in the Account information.

EDIT: Have you updated to 10.5.2? You should. I believe it addresses this issue.

See: http://docs.info.apple.com/article.html?artnum=307109

Mail

Addresses issues with some ISPs during automatic set-up in Mail.
Addresses an issue in which Mail might not send mail on some networks to some SMTP servers.

Also, I've found that using another server to send the first email after launching Mail.app kicks the outgoing server into action (I don't know why that is, but it works). Last, have you checked to see whether your SSL cert is set to Always Trust, both within Mail.app and in Keychain Access.app?

[phlegma]

Thanks for the help, but logging in to what you specified is not the SSL approach, it is just the standard method. Using box383 is what BH states for logging in through SSL

[breakingball]

Thanks for the help, but logging in to what you specified is not the SSL approach, it is just the standard method. Using box383 is what BH states for logging in through SSL

Maybe. I have 19 Bluehost email accounts configured this way in Mail.app, all of which use SSL ports (465, 993) with no issues, so....

[phlegma]

Then why would BH specify that for SSL, you need to use the box.etc?

[Early Out]

Then why would BH specify that for SSL, you need to use the box.etc?Instead of getting into a discussion about it, why not just try it, and see if it works? If it successfully connects, then SSL is, in fact, working.

(Actually, I think I know why BH says to do it that way - in Outlook on a PC, if you don't do that, it complains about the certificate name mismatch every time you launch the application. SSL still works, but the nagging from Outlook is a pain. But you're not using Outlook, so it's not an issue.)

[phlegma]

It works both ways. I just had to always allow trusting of the certificate instead of just hitting connect.

Thanks for the support guys.

[breakingball]

in Outlook on a PC, if you don't do that, it complains about the certificate name mismatch every time you launch the application.

Mac's Mail.app does the same. Fortunately, Macs like to run 24/7, with a reboot once or twice a month to flush the RAM.... ;)

[Early Out]

Fortunately, Macs like to run 24/7, with a reboot once or twice a month to flush the RAM.... ;)My PC doesn't have any applications with memory leaks, so I don't ever have to reboot it to flush the RAM. :p

I do, however, close Outlook often so that my little backup routine can make a copy of its database.