I am running Windows 7 and using Outlook 2007 for my email. For most of the past week and still continuing, Outlook has been able to receive emails but unable to send emails and continually - like over and over again - pops up the Enter Network Password window. I have entered the correct user name and password, clicked Cancel and just closed the window to no effect. It just keep popping up over all other windows and interrupts typing. The only way to stop it is to close Outlook. I have made all of the required port changes to conform to the new requirements. I have chatted with Cox support people already. I have gotten no satisfactory responses. I believe this is a Cox problem not mine. I'm sure others a running into this. Anybody know if Cox has seen and acknowledged this problem and if they have an ETA for a fix?

I have been having the same problem since wednesday. Even have tried changing email software and outbound will not work. They claim the problem is my system.

me too ,, I have windows live email and cant send a darn thing... unable to communicate have the new settings too.. we should all get credited for all of our problems

With Windows Live Mail you need to use the default outbound port of 25 SMTP Cox gives the wrong port on it's instructions. Even their help line gets the port wrong and tries to make you use 465

They told me to contact Microsoft. Good luck with that. With Windows Live Mail you need to use the default outbound port of 25 SMTP Cox gives the wrong port on it's instructions. Even their help line gets the port wrong and tries to make you use 465

Outgoing Email Problems | Cox Community

76 Replies

Replies have been turned off for this discussion

Falmouth
New Contributor
6 years ago
I have been having the same problem since wednesday. Even have tried changing email software and outbound will not work. They claim the problem is my system.
bonbowl
New Contributor
6 years ago
me too ,, I have windows live email and cant send a darn thing... unable to communicate have the new settings too.. we should all get credited for all of our problems
Kenn
New Contributor
6 years ago
With Windows Live Mail you need to use the default outbound port of 25 SMTP

Cox gives the wrong port on it's instructions. Even their help line gets the port wrong and tries to make you use 465
Kenn
New Contributor
6 years ago
They told me to contact Microsoft. Good luck with that.

With Windows Live Mail you need to use the default outbound port of 25 SMTP

Cox gives the wrong port on it's instructions. Even their help line gets the port wrong and tries to make you use 465
LJW
New Contributor
6 years ago
Same here.
Dee47
New Contributor
6 years ago
I'm using Outlook in Windows 10 and having the same problem. However, I have 2 Cox accounts set up in Outlook and both have the same settings. One of them send/receives just fine, but the other one continually prompts for the password when sending and will not send emails. So frustrating!

UPDATE: I did the repair option through Outlook account settings and it updated my SMTP server to 25 with TLS enabled. I'm able to send emails now.
TrishMc
New Contributor
6 years ago
The issue of the Outgoing Server is a Cox problem. Last Thursday, Jan 25, they told me that it was a Microsoft problem so I called Microsoft and was told by them that it was DEFINATELY not a Microsoft problem. So I called Cox back and paid the $10 for CoxCare. The technician confirmed that it was a COX problem since the Outgoing server settings were correct at: SMTP 465 and encrypted connection of SSL. The biggest indicator that it is a COX problem is because the Incoming e-mail works perfectly. I was told that COX upgraded to a new "safer" server for the Outgoing mail and they knew about the issue. Based on this response, I can only conclude the following: 1) They did not perform QA or any form of testing on the new server whatsoever (i.e. They took the Microsoft approach of letting the users test the new product). 2) They don't seem to understand that outgoing mail is just as important and incoming mail. 3) They know they have a captive audience and really don't care if there are problems. And if there are problems, there is no urgency to fix them. Basically, the customers are just jerks like you and me. 4) It's January 28 and I've been on hold with them - it's been 40 minutes. 5) I expect the same answer as before "We know about it and we're working on it". I think that this is code for they took the weekend off and will look into some time next week.
StephanieA
Former Moderator
6 years ago
Hi Everyone,

We have updated our security on our servers. Port 25 will need to be changed to 465 with SSL enabled. Please update the settings, empty your outbox, and try sending a test email to yourself. If you are still not able to send after trying these steps, please post your current settings here to review.
bryaninphx
Valued Contributor
6 years ago
Kenn said:

With Windows Live Mail you need to use the default outbound port of 25 SMTP

Cox gives the wrong port on it's instructions. Even their help line gets the port wrong and tries to make you use 465

I am using Windows Live Mail 2009 (Version 14.0.8117.0416) and it works fine. You can Google "Windows Essentials 2009 offline installer download" if you need to upgrade to a newer version. I just happen to prefer Live Mail 2009 over 2012.

Configure as shown below, Go to the Servers Tab and check the box circled in Orange Below

=====================================================
MartzMimic
New Contributor
6 years ago
OK, this is going to sound crazy...

I was also experiencing an issue sending emails from Outlook 2016 on my PC and on my iPhone 8 Plus since the security update. I had followed the instructions in the Cox email to a "T," but could not send emails. I could receive them.

I resolved my issues on both by changing my password. I ran into this issue once a couple years ago, and resolved it by trying a different password. In this most recent situation, my password ended with a number. I changed my password, and everything began working immediately.

Like I said, it sounds crazy, but it worked for me.