Randy,
The CN (common name) of the certificate would need to match your incoming and outgoing fully qualified domain names. If you server names are both secure1.ehowe.com (or can be made to be secure1.ehowe.com) then you should be able to use your existing certificate.
Jim Lohiser Imagine Net, Inc.
I'm running surgemail on OSX Lion Server. I have ssl certificate but
it's for secure1.ehowe.com
I guess I would have to get another certificate for just ehowe.com
for surgemail to use.
On 7/30/13 1:21 PM, Chris Ferebee
wrote:
What Paul said (RFC 6409).
It's convenient to set Apple Mail to "use standard ports" for SMTP, which will try ports 25, 465 and 587 as necessary, but if your server offers SSL with self-signed certificates, this will often cause SSL to be enabled automatically as well, which results in "untrusted certificate" errors later on.
It's really best to use SSL and get a proper certificate.
Chris
Am 30.07.2013 um 19:08 schrieb "Paul M. Beck" <pbeck@bexx.com>:
He should definitely be using 587 for SMTP as most ISP's block 25
Paul
On Jul 30, 2013, at 12:00 PM, Glenn Meadows <glenn@mayfieldmastering.com> wrote:
Hmm, based on that, what ports is he using for smtp, pop (if using pop, I know you commented in imap) and imap ports? 465/587 for smtp, 993 for iMap?
--
Glenn Meadows
Mayfield Mastering
2825 Erica Place
Nashville, TN 37204
615-383-3708
On 7/30/2013 11:58 AM, Randy Zumwalde wrote:
Hi Paul,
He can still browse the web when the connection is down. We are not using SSL on the mail server. He's tried it at his dads wireless network and also has the same issue unless he changes his smtp to uses his dads service provider (ie. mail.zoomtown.net).
On 7/30/13 12:40 PM, Paul M. Beck wrote:
I, and a number of my clients use 10.8 without issue.
I would expect he is experiencing some sort of network connectivity issue.
Apple mail in 10.8 has a connection doctor under the pull down item "Window" it's the 8th item down.
Additionally when your client is experiencing these issues can they browse the web, of use the surge mail web front end?
Are you using SSL, I've had issues if I didn't force Apple Mail to use the ssl ports.
I definitely agree he should try connecting hard wired as well as from a different location (wired and wireless) as he could be having an issue with his wireless card.
Paul
On Jul 30, 2013, at 11:20 AM, Chris Ferebee <cf@ferebee.net <mailto:cf@ferebee.net>> wrote:
Randy,
If at all possible I would try to convince him to work over an Ethernet connection for a while to rule out problems with his wireless connection.
You could also try to monitor his connection, even by simply running ping in a Terminal window in the background.
In my experience, Wi-Fi has been getting less and less reliable over the years, at least in the city. I think we're just seeing ever more networks (and perhaps also other transmissions on the same unlicensed 2,4 GHz frequency band).
The error messages certainly seem consistent with a networking issue.
If you have a VPN server, you could try setting him up to connect over VPN and see if that makes the problems go away, or alternatively if his VPN connection drops all the time due to the same network issues.
Best,
Chris
Am 30.07.2013 um 17:48 schrieb Randy Zumwalde <zumwalde.rl@ehowe.com <mailto:zumwalde.rl@ehowe.com>>:
I have a user that intermittently cannot connect to Surgemail and I'm wandering if there is anything I could do to resolve the issue.
He is using Apple Mail on OSX Mountain Lion. Sometimes he connects just fine then an hour later he cannot.
He gets an SMTP connection message like this:
"Could not connect to this SMTP server. Check your network connection and that you entered the correct information in the Account preferences."
At the same time he gets an IMAP message like this:
"Could not connect to this IMAP server. Check your network connection and that you entered the correct information in the Account preferences. Also verify that the server accepts connections on port 143. If it does not, change the port number in the Advanced tab of Account preferences."
I have no idea why he is having this issue and it is driving him and I nuts. Could it have something to do with his network connection. I believe he works via his wireless connection at home as does most of our remote employees but he seems to be the only one having issues and seems to believe it could be my problem since I run the mail server.
--
*Randy Zumwalde* • Tel: 513.651.1888 • Mobile/Direct 859.801.1419
IT Manager | The John K. Howe Company, Inc.
7188 Main Street | Cincinnati, OH 45244
Be sure to visit us online at http://www.ehowe.com <http://www.ehowe.com/>
Like us on Facebook at _https://www.facebook.com/howemarketing_
Looking for product ideas? visit _http://ehowe.mypromohq.com <http://ehowe.mypromohq.com/>_
<howe.jpg>
--
*Randy Zumwalde* • Tel: 513.651.1888 • Mobile/Direct 859.801.1419
IT Manager | The John K. Howe Company, Inc.
7188 Main Street | Cincinnati, OH 45244
Be sure to visit us online at http://www.ehowe.com
Like us on Facebook at _https://www.facebook.com/howemarketing_
Looking for product ideas? visit _http://ehowe.mypromohq.com_
|
