Tired of searching for email configs.

[robio376]

Host 2 sites and still have trouble for setting up email in Outlook 2007.

Trying to configure our email clients (Outlook 2007) and one incoming imap 143 works as also
our outgoing SMTP 465 with SSL for one domain. But when I try to set it up with another domain that I have purchased (from Bluehost), it doesn't work. Really wish the configure email client was up to date. You Outlook 2000 configure email client is a little outdated.

[Early Out]

Does it work without SSL on port 25 or port 26?

[DanEG]

I'm having some issues trying to configure Outlook 2007 also. not sure it's worth a new thread though.

first of all, I wanted the SSL pop3 connection (box432.bluehost.com), but I kept getting invalid certificate messages that I had to manually override every time I ran a send/receive action. well that's ridiculous. I can't be doing that each time.

so I went back to regular old pop3 server (mail.aeentertainments.com). This really isn't what I want, but at least it's serviceable. But even there, every once in a while, I'll send a message on the same server (mail.aeentertainments.com) and get the standard "invalid certificate" notice that I need to click through. :confused:

I've played with the outgoing ports (26 vs. 465), servers, and my username/loginID (username+domain vs. username@domain). They don't seem to have any impact on the problem except that the secure server ALWAYS triggers the invalid certificate message and the standard server does it rarely and during send (smtp) actions.

Honestly, I'd be happy just to accept the SSL certificate permanently (for SSL connectivity), but I see no way of doing so. I'm new to Office 2007 (sucks, btw), but configuring a pop3 account is not exactly rocket science. Am I missing something really obvious? Any help is greatly appreciated.

edit: aeentertainments.com is actually a parked domain on ancientearthentertainment.com, but the same issues occur with the latter domain concerning SSL connection. So I seriously doubt that's behind my problem. :confused:

[Early Out]

The problem with SSL is that it's a shared certificate, so the holder of the certificate (boxXXX.bluehost.com) doesn't match the mail server (mail.yourdomain.com). This upsets Outlook, and there's no way to tell it that it should ignore the mismatch. You have to tell it every time you launch Outlook. Thunderbird, on the other hand, can be told not to sweat the details.

If you're also getting the warning on outgoing mail, you need to stick to port 26, with no SSL. I find it hard to believe that the warning is appearing on a non-SSL connection.

[DanEG]

hmm...I was about to post pics of each tab in my setting until I noticed that even though SSL was unchecked, the outgoing secure protocol was set to "auto." Would that still cause the outgoing issue? Guess I'll know soon enough if that does the trick.

http://aeentertainments.com/images/aee-ports.jpg

For the greater good, I think I'll just access my business email through thunderbird. it's prolly easier than separate data boxes in outlook anyway. there are random occaisions when outlook just cannot read/find the custom data folders for these accounts (nothing wrong with hdd).

[DanEG]

The problem with SSL is that it's a shared certificate, so the holder of the certificate (boxXXX.bluehost.com) doesn't match the mail server (mail.yourdomain.com). This upsets Outlook, and there's no way to tell it that it should ignore the mismatch. You have to tell it every time you launch Outlook. Thunderbird, on the other hand, can be told not to sweat the details.

If you're also getting the warning on outgoing mail, you need to stick to port 26, with no SSL. I find it hard to believe that the warning is appearing on a non-SSL connection.
would the above issue have any relevance to the following error code in the Mail server host name in greeting:

WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.

aeentertainments.com claims to be host box432.bluehost.com [but that host is at 69.89.31.232 (may be cached), not 67.222.45.245]. <br />
It looks like the warning is telling me that I'm being blocked by one of my vendor's anti-spam apps, but that doesn't exactly gel with the fact that I get these failure notices from BH a week or so after trying to send the message:

Hi. This is the qmail-send program at outbound-mail-138.bluehost.com.

I'm afraid I wasn't able to deliver your message to the following addresses.

This is a permanent error; I've given up. Sorry it didn't work out.

any help is greatly appreciated. :)

[Early Out]

Welcome to the wonderful world of shared hosting. Your domain may be aeentertainments.com, but each domain doesn't get its own actual mail server. You wouldn't really expect that, would you? Your outgoing messages are routed first through the server you share with 1000 other domains, and then through a collection of SMTP servers that actually make contact with the outside world.

Having said that, there's no indication that anyone's outgoing email is being blocked because of a host name mismatch.

What does happen, however, is discussed in this thread (http://www.bluehostforums.com/showthread.php?t=15528). Please search the forums before posting.