New Contributor III
•
37 Messages
Intermittent Email send/receive failures with POP3 - Again, for the third time
I posted about this issue back in January & May 2015 and this issue has come up again. Cox still has this problem and has to do something about it. Back in May or so, during a tech support phone call about something else, on a lark I mentioned this issue to the tech who said it was a known issue and he'd kick it upstairs...and the problem lessened a few days later...till the past few weeks. Now the issue is back again with a vengeance.
This current intermittent email send/receive error is much worse, occurring all throughout the day, on all my @cox.net email accounts, no matter what I do. This is a well known issue to Cox and they've admitted it's on their end...so no, it's not Outlook, it's not my computer, Cox modem, or some other excuse. There are Cox customers all over these boards with the same issue for the past year at least.
Please resolve this issue...I'd really appreciate it.
Since the recurrence of this issue is almost identical to my previous occurrences, I'll just repost my original posting, with modifications:
---------------------------
For the past few weeks now, I've been experiencing the intermittent email send/receive failures, like many other customers in these forums have reported. This needs to get fixed by Cox ASAP, instead of sometimes telling us it's being worked on.
My system specs:
Windows 8.1 Pro x64
MS Windows Defender active, no other security packages
MS Outlook 2007
Cox Internet Preferred package with the Cox provided DOCSYS 3.0 NetGear N450 modem/router
My issues:
For weeks, all of my @cox.net email accounts have intermittent problems sending or receiving emails through Outlook 2007. When receiving emails, I'll get the Outlook pop-up error window stating (the message details may vary depending):
-------------------------------------------------------------------
"Task 'myemailaddress@cox.net - Receiving' reported error (0x8004210A) : 'The operation timed out waiting for a response from the receiving (POP) server. If you continue to receive this message, contact your server administrator or Internet service provider (ISP)."
OR I'll get this message:
"Task 'myemailaddress@cox.net - Receiving' reported error (0x800CCC92) : 'Your e-mail server refjected your login. Verify your user name and password in your account properties. Under Tools, click E-mail accounts. The server responded: -ERR mail storage services unavailable, wait a few minutes and try again.'
-------------------------------------------------------------------
This issue happens consistently, several times a day...then emails will suddenly work again...then the issue reappears, rinse & repeat...it's an ongoing cycle of working/not working throughout the day for weeks now.
I have several other non-Cox email addresses that have no issues at all sending/receiving within Outlook. Only my Cox email addresses have this issue.
It's almost useless calling Support about this. Some support reps blame Outlook, like usual, while others have acknowledged it's a Cox issue and they'll forward it on for resolution. It's not an Outlook problem. Everything worked great for years...then this issue popped up over a year ago, as so many other customers have been reporting. And as mentioned by other customers, Cox acknowledges that they know about this problem with email and it's been kicked upstairs for a harder look. But this has been going on for far too long and we never see a solution.
On my end, in past occurrences, I've reset my Outlook settings for the Cox emails, tried different settings and ports according to the Cox email support docs, and even deleted my Cox email account profiles within Outlook and recreated them (in case they were corrupted). Nothing has worked.
From a troubleshooting standpoint, everything points to Cox being the culprit, which they have acknowledged. Instead of just nodding at us, tell us what's really going on and kick someone to hard fix this.
If there's any other information I can provide or help you with, let me know.
Thank you.
Neuro2015
New Contributor III
•
37 Messages
10 years ago
0
0
yak
Contributor III
•
521 Messages
10 years ago
I wondered if i was alone. I just posted a similar question today. Yesterday i could not receive. Today i could not send. Same thing that started November, 2014. The problem usually lasts 1 hour or less. Sometimes it happens more than once in a day. All of my settings have been verified to be correct. Cox did make some efforts to help. They switched some accounts to a different server and that made things much better. But only for a month. Then the send/receive problems came back. I am generally happy with my Cox email. Fast and reliable. But this problem can occur at the worst times. Today, customers were waiting for my emails and i did not have a phone number to tell them that i could not send emails. Luckily, they called me.
0
0
EdwardH
Valued Contributor
•
755 Messages
10 years ago
In the email issue, with the Pop servers the issues from late last year have been resolved as Tiffany mentioned though it may be a localized issue. Just to get al the information on escalating can you confirm the Pop setting in Outlook for the port and if SSL or TLS are being used when seeing the issue?
---
0
0
Neuro2015
New Contributor III
•
37 Messages
10 years ago
0
0
timannnn6
New Contributor
•
2 Messages
10 years ago
I am having the same issue on my Macbook Pro with Outlook 2016 for MAC using SSL ports 995 to receive and port 465 on send. If I change to non SSL I can receive and send email just fine. I don't want to use the non SSL ports. All passwords are confirmed current/working as I can login to webmail just fine. Funny thing is I have an ATT email account as well with exact same ports setup and it's working perfectly. Definitely a COX issue.
This is the error I get "An operation on the server timed out. The server may be down, overloaded, or there may be too much net traffic. Could not retrieve mail. Error code -1001"
If I change the ports to 110 and 25 email works fine.
0
0
yak
Contributor III
•
521 Messages
10 years ago
@tim6, are you saying that you recommend changing to ports 110 and 25? Or are you just saying that you can use them to temporarily fix the send/receive problem? When i had the problems ( the "send" problem and the "receive" problem do not happen at the same time) i called Cox Support and spoke to a Level 2 (Tier 2?) technician who said that the problem has not been completely fixed. He verified that my settings are correct.
0
0
timannnn6
New Contributor
•
2 Messages
10 years ago
What I meant was if I leave the SSL ports 995 and 465 then I get errors. If I change to 110 and 25 (non SSL ports) the email works fine. I do not want to use the non secure ports when traveling.
0
0
Tecknowhelp
Valued Contributor II
•
2.8K Messages
10 years ago
I think the issue is since moving to IMAP, that sync more often with email servers, the authentication servers have become backed up. That is why port 25 works when 465 does not. Anyone notice any difference between using SSL on 465 and TLS on 587? I have a feeling it won't make a difference, but it's worth a shot.
Also, is there anyway to force what SMTP server you authenticate through? Maybe look at the mail headers of a email sent before and after the "change server" fix where they redirect your mail through another SMTP server? Or is that only possible on the back end?
0
0