This discussion is archived
2380 Views 7 Replies Latest reply: Jan 18, 2009 10:49 PM by Nick King
Currently Being ModeratedJan 18, 2009 12:38 AM (in response to PMAZ7)Have you seen [this page|http://office.microsoft.com/en-us/outlook/HA010962641033.aspx]?
It explains how to set it up, but it sounds like you can't connect directly to the smtp server so will have to find a different method of sending mail.
I had a similar issue with my work Exchange server and used [DynDNS's Mailhop|http://www.dyndns.com/services/mailhop/outbound.html] service to get around the problemMBP 15" iPhone 3G, Mac OS X (10.5.6)
Currently Being ModeratedJan 18, 2009 8:42 AM (in response to Nick King)I just checked out that page, and unfortunately it doesn't answer my questions concerning my 'pop' to 'spop' issue with mac mail. If it does, I'm not understanding it. Any additional help would be greatly appreciated.MacBook Pro, Mac OS X (10.5.6)
Currently Being ModeratedJan 18, 2009 9:23 AM (in response to PMAZ7)Sorry, I don't see any mention of spop on that page. Is that a secure POP server?
I think you'll need to get support from the mail service providers here.MBP 15" iPhone 3G, Mac OS X (10.5.6)
Currently Being ModeratedJan 18, 2009 10:20 AM (in response to Nick King)No problem, I appreciate the reply. It's cox.net. Whether that's a 'secure' server or not, I'm not sure. Please, can someone help before I punt this MBP across the street?!MacBook Pro, Mac OS X (10.5.6)
Currently Being ModeratedJan 18, 2009 10:33 AM (in response to PMAZ7)No I meant that if your putting spop and it's then trying to connect to a secure server that you haven't got either permissions/certificates/passwords for, then that could be the problem.
On that page the server is pop.west.cox.net not spop.west.cox.net.MBP 15" iPhone 3G, Mac OS X (10.5.6)
Currently Being ModeratedJan 18, 2009 9:24 PM (in response to PMAZ7)When setting up your account to use with Cox.net, the Mail defaults to use a secure pop type of connection first. For Cox.net change pop.west.cox.net to spop.west.cox.net. The warning is genereated when the SSL certificate host name is different than the host-name you are requesting. For example the certificate expects spop.west.cox.net, not pop.west.cox.net. In this example, a security warning is given to you for review and either cancel or accept.
Other workarounds are needed in regards to sending email through a non Cox.net email server. I can provide more information upon request.
You will not be able to send email through the Cox.net email servers from outside thier network, for example a hotel room. You will have to use their webmail interface.
Hope this helps