VanguardLH wrote:

svejkat wrote:

I have ver 6 of OE and I just started getting this error message:The
connection to the server has failed. Account: 'POP.WEST.COX.NET', Server:
'SMTP.WEST.COX.NET', Protocol: SMTP, Port: 4500, Secure(SSL): No, Socket
Error: 10060, Error Number: 0x800CCC0E

Hw do I fix it? thanks

Um, what's with the port 4500? POP normally uses port 110.

telnet POP.WEST.COX.NET 110
(responds immediately)

telnet POP.WEST.COX.NET 4500
(no response)

So when did you decide to use port 4500?

Oops, the POP part was in what you named the account (which you let
default to the POP server's name). The server you have problems with is
their SMTP mail host. The de facto port for SMTP is 25 (although an RFC
in 1998 changed it to 537 for end-user clients). So try 25 or 537. Of
what I saw in their web help pages, they don't specify the port so they
are defaulting to whatever default the e-mail client uses, and
traditionally that has been port 25 for SMTP.

telnet SMTP.WEST.COX.NET 4500
(no response)

telnet SMTP.WEST.COX.NET 25
(no response)

telnet SMTP.WEST.COX.NET 537
(no response)

Hmm, have you called Cox tech support to ask if this particular mail
host is operational?

I later found http://support.cox.com/sdccommon/asp...ntredirect.asp
which says to enable SSL on the outbound connection (to SMTP) and to use
port 465. I can't do SSL using telnet or go through the handshaking
process, so try enabling SSL on the SMTP connection and specify port
465.

Port 4500 was such a weird port number that it stuck out as probably the
cause of your problem. I've never heard of an SMTP mail host using that
port. You sure that you didn't install some anti-spam or anti-malware
program that acts like a proxy and modifies the account settings in OE?
That is, the anti-whatever program is running a local proxy that listens
on port 4500 and changes OE to use that port to go through their proxy
(and the proxy then goes to the real mail host).