Ongoing email problems
My email works fairly well over the weekend, but is absolutely horrible Monday through Friday. This is the message I get every few minutes: There may be a problem with the mail server or network. Verify the settings for account "Cox - IMAP" or try again. The server returned the error: The connection to the server "imap.cox.net" on port 993 timed out. The settings for my email are all correct. I'm using MacMail, and it has worked perfectly until about a month ago. Since then I have had nothing but trouble.13KViews0likes24Comments
"Enter network password" windows repeatedly popping up on Outlook email
I've had 3 minimum long chats with tech support and they've changed passwords, fiddled around, but in a nutshell I am still plagued constantly by these "enter network password" pop up windows. All PWs are entered correctly. Send/receive test works fine, all email addresses send/receive okay --- and then they don't! I have a Dell PC, Windows 8.1, MS Office 2013, I use Outlook 2013 for email. (Don't use webmail, just my PC.) Tech support has been hopeless in resolving this and I am tearing my hair out. Impossible to work with these darned pop-ups. Some days worse than others but no real rhyme or reason. One tech tried to tell me it might be because my McAfee security setting was high (it's set on medium level). I said, "and that would explain 6 pop up windows in 20 seconds?" No answer. I'm beyond disappointed in Cox. Twice, the tech support sessions left things worse rather than better. Has anyone had and resolved this problem? Thanks for any advice.11KViews0likes6Comments
Intermittent Email send/receive failures with POP3 - Again, for weeks
I posted this a couple weeks ago, have received no responses, and discovered it was deleted. So I'm posting it again. Don't delete it again...please solve it. For the past few weeks now, I've been experiencing the infamous & intermittent email send/receive failures, like many other customers in these forums have reported. My system specs: Windows 10 Pro x64 MS Windows Defender active, no other security packages MS Outlook Cox Internet Preferred package with the Cox provided DOCSYS 3.0 NetGear N450 modem/router My issues: For several weeks, my various Cox 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: ------------------------------------------------------------------- "Task 'myemailaddress' - Receiving' reported error (0x800CCC92 or some other error code) : '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)." ------------------------------------------------------------------- This issue happens consistently, several times a day with all my Cox email accounts...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 the past few weeks now. I don't bother calling Support about this because they usually blame Outlook and do nothing. It's not an Outlook problem. Everything works great, when it works...then this sudden issue pops once or twice a year, as so many other customers have been reporting. And as mentioned by other customers, Cox somewhat acknowledges that they know about this problem with email and it's been kicked upstairs for a harder look. In the past, 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. This happens regularly, so please Cox...don't ask the usual questions about using Webmail, trying another computer, etc. We know, and you know, this has been a persistent, recurring issue with Cox email accounts for many years and these suggestions don't work or fix anything. Usually, Cox Support hems & haws and says they're working on it...or they wrongly blame Outlook...and nothing gets resolved. After repeated complaints to report the issue, they'll usually reset or do something to solve the issue. So I'm adding my issue & complaint here to be resolved also. Please fix this email issues ASAP. Thank you.8.8KViews0likes17Comments
imap.cox.net password incorrect
Setting up my cox email account on my iPhone 5s, it gives me an error during the autoconfig that the password for imap.cox.net is incorrect. I can sign into my webmail account just fine on any computer. I've even changed my email password a couple times but no matter what I do I can not setup my cox webmail because I can't get past this error. I'm following the online directions: Settings > Mail, Contacts, Calendars > Add Account > Other > Add Mail Account > Name,Email,Password,Description...Next > ERROR "Cannot Get Mail - The user name or password for imap.cox.net is incorrect".7.9KViews0likes2Comments
Mail going to spam folder in cox.net
Mail going to spam folder incox.net I am trying to troubleshoot an issue with mail that I am sending through a third party (ESP) to myself, and for over a month now the messages have been delivered to the junk folder. I want to determine if this is an issue with content or perhaps with the sending domain or IP reputation. The messages aren't being bounced or blocked. The messages are consistently going to the junk folder now, and even when a contact forwards the same message to me (that they successfully received elsewhere) their forwarded messages go to the junk folder. I'd also like to know if this is a problem for my mailbox or if it may be impacting othercox.netusers who we send the same messages to. Below are the headers for two such messages, retrieved from the junk folder. Can someone from Cox examine the headers to determine what might be going on? I don't believe I have a rule in place for the sending domain set to be blocked or junked, nor do I have them set to be allowed. The two message headers: Message 1 - junk folder placement: Return-Path: <[REMOVED]> Received: from eastrmimpi210 ([68.230.241.251]) byeastrmfepi101.cox.net (InterMail vM.8.01.05.15 201-2260-151-145-20131218) with ESMTP id <20150826183304.RQGX24673.eastrmfepi101.cox.net@eastrmimpi210> for <[REMOVED]@cox.net>; Wed, 26 Aug 2015 14:33:04 -0400 Received: from [REMOVED] by eastrmimpi210 with cox id 9WZ11r00B0fxNjC01WZ2To; Wed, 26 Aug 2015 14:33:03 -0400 X-Spam-Optin: quarantine Message-ID: <9WZ11r00B0fxNjC01WZ2To> X-CT-Score: NA X-Authority-Analysis: v=2.0 cv=eZPjic4H c=1 sm=1 b=1 p=2kgPxcPQX4wA:10 a=OgR1bFBF52G5VLou61Qdlg==:17 a=jqJx3APsAAAA:8 a=LDByVImiAAAA:8 a=kviXuzpPAAAA:8 a=jPJDawAOAc8A:10 a=uRRa74qj2VoA:10 a=lyYuGu4CHa5PaZGX25icmyaRxzw=:19 a=Yx3IPQ1jo9L7taPXwAoA:9 a=QEXdDO2ut3YA:10 a=WhyLCfzSn8QA:10 a=Y9ZmdtH27PMA:10 a=ZSZAJmUR2EIA:10 a=UTW3GctDQawA:10 a=PR7BF1aH1wEA:10 a=8NxcaRFQ8m0A:10 a=qTpy2nhRcN4A:10 a=YnjVFmDOeLoA:10 a=JHyW0B_OV8oA:10 a=M4QScfzLx2AA:10 a=KYXIKXl0XnsA:10 a=w198VKY8_hbgblWb4fUA:9 a=2Ahxn7RlsFsA:10 a=OgR1bFBF52G5VLou61Qdlg==:117 X-CM-Score: 96.00 Received: from [REMOVED] id hro35u16jb4h for <[REMOVED]@cox.net>; Wed, 26 Aug 2015 14:33:01 -0400 (envelope-from <[REMOVED]>) X-Receiver: <[REMOVED]@cox.net> X-Sender: <[REMOVED]> Date: Wed, 26 Aug 2015 18:33:01 +0000 From: <[REMOVED]> Reply-To: <[REMOVED]@cox.net> Subject: =?UTF-8?B?KiogSW5mb3JteiBUZXN0LTIgKiogUkkgTWVkaWNhbCBKb3VybmFs4oCTQXVn?==?UTF-8?B?dXN0IElzc3Vl?= To: <[REMOVED]@cox.net> Message-ID: <[REMOVED]> List-Unsubscribe: <http://[REMOVED].net/[REMOVED]/default.asp?action=u&email=[REMOVED]@cox.net&mi=4606687> X-IADB-IP: [REMOVED] X-IADB-IP-REVERSE: [REMOVED] X-IADB-URL: [REMOVED] MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="Mjk4OTM0MTA1NDA3MTM5MzU4NDc3OTgxNDg4OTk4" Message two, a forward of the message above sent to me from another provider, also placed in the junk folder: Return-Path: <[REMOVED]> Received: from eastrmimpi110 ([68.230.240.50]) byeastrmfepi207.cox.net (InterMail vM.8.01.05.15 201-2260-151-145-20131218) with ESMTP id <20150825151858.UGZD15495.eastrmfepi207.cox.net@eastrmimpi110> for <[REMOVED]>; Tue, 25 Aug 2015 11:18:58 -0400 Received: frommail-ob0-f170.google.com([209.85.214.170]) by eastrmimpi110 with cox id 93Fv1r02b3h9KGZ013JuwG; Tue, 25 Aug 2015 11:18:54 -0400 X-Spam-Optin: quarantine Message-ID: <93Fv1r02b3h9KGZ013JuwG> X-CT-Score: NA X-Authority-Analysis: v=2.0 cv=cuRFZSEi c=1 sm=1 p=2kgPxcPQX4wA:10 a=jqJx3APsAAAA:8 a=pGLkceISAAAA:8 a=jPJDawAOAc8A:10 a=uRRa74qj2VoA:10 a=LDByVImiAAAA:8 a=Yba-5btluGXBt1vgvQEA:9 a=QEXdDO2ut3YA:10 a=WhyLCfzSn8QA:10 a=Y9ZmdtH27PMA:10 a=ziwGhm86LekA:10 a=M4QScfzLx2AA:10 a=2Ahxn7RlsFsA:10 a=HfggiU_nJIziXa3iytcA:9 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=_W_S_7VecoQA:10 a=frz4AuCg-hUA:10 a=d5Tk2X25c3oA:10 a=NWVoK91CQyQA:10 a=99SZI+B64J60o7343nyXDw==:117 X-CM-Score: 96.00 Received: bymail-ob0-f170.google.comwith SMTP id wr7so144800267obb.2 for <[REMOVED]@cox.net>; Tue, 25 Aug 2015 08:18:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:content-type; bh=eyXaQobaSK4Bu8l0Uen6l5s0W5f5vy4e/tYYnb3NCuQ=; b=ii+fpub53ffTMiDM/+l3uTXCpfA6Cn1PZdFnZaWLKxR7g7SAHaxdUKl8ap1mERnm2i 4KlvJUro1TGyRuK/XPi4ByE4n93545mbWUxSzLe5V0pm5Q4Cp3seNhXEuJNdwzczQcvj v0yIQaKLRmv5LvOxevlE8saIJzm/RzWdu/nluCB5+uf/3yJAbz57R/VC3nmCVE5lVoW3 eucVnQSiWiYg7Wd2EfJNRsDmPO8fza9QAm0un3aUPpZjehEeRuv4zO2WB4IT8CVMC4ga 1Vd1/LpQIgeK4qcph/6SLpZC1Cz9pmnngV4e+P23NPXCH43nG8nSlrJFcRUNEh95wf6j QEFg== X-Gm-Message-State: ALoCoQmGgkdJZmyNy8vPTOrUbAyjizNHV26Oz3x7t/T81w1NkqYYRF4gSrdgdw1OX/Az9ZomWbH3 X-Received: by 10.60.33.74 with SMTP id p10mr28256410oei.62.1440515934836; Tue, 25 Aug 2015 08:18:54 -0700 (PDT) From: <[REMOVED]> References: <[REMOVED]> In-Reply-To: <[REMOVED]> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQGaIpo9KhG6sBGOw2oGNuCV+ZfGFp6KTN3g Date: Tue, 25 Aug 2015 11:16:45 -0400 Message-ID: <b85f27beac4c6856b680 @mail.gmail.com> Subject: =?UTF-8?Q?RE=3A_=2A=2A=2D1_=2A=2A_Journal=E2=80=93August?= =?UTF-8?Q?_Issue?= To: <[REMOVED]@cox.net> Content-Type: multipart/alternative; boundary="089e0115eef896fdc0051e244039" One thing I noticed in both messages was the "X-CT-Score: NA" and "X-CM-Score: 96.00", where messages that are NOT placed in the junk folder have "X-CT-Score: 0.00" and "X-CM-Score: 0.00", like so: X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020202.55DF6A14.0288:SCFSTAT18704550,ss=1,re=-4.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.0 cv=bsyS8jmi c=1 sm=1 a=jqJx3APsAAAA:8 a=pGLkceISAAAA:8 a=uRRa74qj2VoA:10 a=3rIOuboa6WO4aOeUn_AA:9 a=QEXdDO2ut3YA:10 a=dCqkORpdOv8A:10 a=dF6-1Dv-l8Iueur8euIA:9 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=_W_S_7VecoQA:10 a=frz4AuCg-hUA:10 a=8KaXlSnK7icamR8iFF8A:9 a=IKIoO-ieCDEA:10 a=W0k1p8L2Fg/Q12D2FaSoVw==:117 X-CM-Score: 0.00 What do the X-CT and X-CM scores mean? This seems to be a consistent difference between delivered and junked messages. I don't need to know the secret sauce behind the scoring, but I am hoping to know what is the basic cause for scores to go one way or another, or to be "NA" as seen in the junked message above. I am configured to use classic webmail, though I am interacting with my mail not through thecox.netweb UI, instead using Apple mail on my Mac. I have reported messages from the sender as false positives in the past, and have gone to thecox.netwebmail only when I need to retrieve messages that wind up in the junk folder there. If I could get some assistance figuring out why these messages are always going to the junk folder I would appreciate it. I don't want to just add an allow rule to push the messages through, as that simply masks the issue. It may not even be effective, as I believe those rules work AFTER thecox.net's spam filter has made its own judgement and the messages may remain in the junk folder. I also want to figure out if this is an issue specific to my mailbox or if it is impacting othercox.netrecipients of the same mail as we send to many members of the organization who usecox.netaddresses for their email. If there is any additional information I can provide, please let me know. If the conversation must be taken offline to avoid exposing too much information, that would also be okay. I can involve someone from the ESP in the conversation as needed.7.6KViews0likes3Comments
Can't receive all emails
I am not receiving all emails. It seems I can't receive any from gmail account users. I have never had any problem until recently. My neighbor and I no longer are able to send or receive each other's emails. He uses gmail. But we can correspond if I use yahoo. Another email friend has gmail. She said she receives my emails but I don't receive hers. Here lately I have really been disappointed in my Cox services of internet and TV. I've even emailed Cox 3 times thru the website and they don't respond. What could be the reason for not being able to get all emails? Thank you7.4KViews0likes7CommentsCan’t Access E-Mail using Outlook or MacMail (Error Code 3170)
Can’t Access E-Mail using Outlook or Mac Mail (Error Code 3170) Starting on 10/2/19, I’ve started getting the following error message: “Outlook cannot find the server. Verify the server information is entered correctly in the Account Settings, and that your DNS settings in the Network pane of System Preferences are correct.” I made no changes to my Outlook e-mail client; this just started happening out of the blue. Then as a test, I attempted to download my e-mail via Mac Mail. This also failed to connect, just got a spinning wheel that forced me to use a “force-quit” to get out of the Mail app. I updated my Cox password and also tried resetting the modem. It should be noted that I’m able to access my Web Mail via Cox’s main website; no problems there. Because I cannot access my e-mail using two separate e-mail clients, I strongly believe that the problem is with Cox. My system details: Outlook for Mac 2011 (14.7.2) Mac Mini running Sierra 10.12.6 Although I’d made no changes to either e-mail client, I reviewed the Port settings for both servers (993 and 465) to make sure they were correct. The “Use SSL to connect (recommended)” check boxes are checked for both Incoming and Outgoing. For Authentication I have “Use Incoming Server Info” applied (I also tried “User Name and Password” to no effect). I’ve had issues with my Cox e-mail several times in the past, so I’m quite familiar with how to set up my e-mail clients with the correct information. I would greatly appreciate any and all assistance, advice, help! Thanking in advance...Solved6.8KViews0likes18CommentsCan't send e-mail using Outlook, Mail (OS10.11.6) or Mail (iOS)
Okay, please bear with me cause this post will be somewhat long. Problem in a nutshell: I haven't been able to send e-mails since June 1st, 2017. I've chatted online with two tech reps, and today I discussed the issue on the phone with a fellow named Ron. Here's some info from the second online chat: Dear Cox, I chatted with one of your tech reps yesterday regarding my inability to send e-mails. After a lot of back & forth re: making sure that I had the correct POP e-mail account settings, she eventually found out and then told me that Cox was in the process of updating their “e-mail platform,” and that I should try again in a few hours. Could you please update me re: the status of this; it’s a day later and I’m still unable to send e-mails. Here’s the background info re: my issue: I am currently not able to send outgoing mail, although I was able to send mail on May 30th. I’m using Outlook 2011 as my e-mail client. My OS is El Capitan 10.11.6. I’m able to receive messages. I believe I have the correct POP settings as specified on your website page “Cox Email Server Settings.” When attempting to send an e-mail I get the following error: fed1rmimpo209.cox.net cox connection refused from 68.6.118.7 It’s very strange that I was able to send e-mails up to May 30th, but not able to June 1st. Please advise and update; any assistance and new info would be greatly appreciated! After waiting a day with no feedback or resolution, I started another chat, opening dialog as follows: Hello, there’s been an ongoing problem with me not being able to send e-mails using Outlook 2011 on my Mac-Mini (El Capitan, 10.11.6). I’ve chatted with several people to date, and have confirmed that I have the correct POP settings for my Cox account. The last person I spoke with submitted a support ticket, and said I’d have a reply within 48 hours; the support ticket was issued on June 2nd and I have yet to hear from anyone, so I’m starting to get somewhat frustrated. I’d greatly appreciate if you could get me an update. The problem started on June 1st. I was able to send e-mails before that date without any problems. Please help! I was eventually told that the problem was with Cox's servers and that the issue would be resolved within 24 hours. 48 hours later, I'm still not able to send e-mails. So today, I called Cox and had a long discussion with the aforementioned Ron. We did a lot of tests, tried different port settings, etc. and he came to the conclusion that the problem was with my Outlook application (which I was doubtful of, but heck, I'm no techie). I decided to test Ron's theory and did a test run using my Mac's Mail Application, which to date I hadn't used. Not surprisingly, I was unable to send e-mails using Mac Mail either! Again, I tried various outgoing server settings, all with the same negative results. Just to take it one step further, I attempted to set up the Mail program on my iPad, which to date I'd never used. This also failed, giving me the following message: "The SMTP server "smtp.cox.net" is not responding; etc, etc. While doing all these tests I also performed extra steps like taking Outlook and Mail offline after making account changes, deleting outbox messages and creating new ones for testing, etc. Which leads me to the conclusion that there is indeed something wrong on Cox's end, as I was originally told during my second online chat. I'm hoping someone on this forum can provide some insight, as I'm going a bit crazy not being able to send e-mails, and Cox support has been useless to date. I may have to start using Cox's Web Mail application to send e-mails (which works) but I'd really prefer to use my desktop's Outlook application! Any help and insights will be greatly appreciated!! Thanks, David6.4KViews0likes10CommentsIntermittent Email send/receive failures with POP3 - Usual issue every few months - PLEASE FIX
For the past couple weeks now, I've been experiencing the infamous & intermittent email send/receive failures, like many other customers in these forums have been reporting. My system specs: Windows 10 Pro x64, version 1809, all updates installed MS Windows Defender active, no other security packages MS Office Outlook 2007 Cox Internet Preferred package My issues: For the past couple weeks, my various Cox 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 infamous 'Enter Network Password'. This issue happens consistently, all day longwith all my Cox email accounts...then emails will suddenly work again temporarily...then the issue reappears, rinse & repeat...it's an ongoing cycle of working/not working throughout the day for the past couple weeks now. I don't bother calling Support about this because they usually blame Outlook and do nothing about it. It's not an Outlook problem...or a Windows Defender problem, or a security setting problem. Everything works great, when it works...then this sudden issue pops once or twice a year, as so many other customers have been reporting. And as mentioned by other customers, Cox somewhat acknowledges that they know about this problem with email and it's been kicked upstairs for a harder look. In the past, 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. This happens regularly, so please Cox...don't ask the usual questions about using Webmail, trying another computer, etc. We know, and you know, this has been a persistent, recurring issue with Cox email accounts for many years and these suggestions don't work or fix anything. Usually, Cox Support hems & haws and says they're working on it...or they wrongly blame Outlook...and nothing gets resolved. Eventually, somewhere in the deep basement of Cox, some tech support genius who lives down there, does something that magically fixes the issue. I pay a lot of money every month and expect working email. Please fix this email issues ASAP. Thank you.6.2KViews2likes14Comments
Rejected messages
It appears the new spam filtering service Cox is using (cloudfilter.net) is blocking a lot of valid mail. I would like to know where our individual portals and addressbooks are that we can configure our own whitelists and to be able to see what messages are being rejected. It is one thing to be identify a message as spam, and another thing entirely to reject them without notification. I have mail senders from a good number of places and since my mail volume has dropped by over 75%, it is quite safe to assume the spam aggressiveness thresholds are set quite high as well as are the bulk sender identifiers and anti-spoofing features. While you claim to not whitelist senders, you do need to provide your users the ability to do so. No doing so means you are censoring email Also, it is poor form to put a like to review changes and then have it error out. http://postmaster.cox.net/confluence/display/postmaster/Error+Codes If you are going to implement such a service you should become a lot more responsive with corrective actions. I am now on my second day waiting for an answer on my ticket with Tier 2, and third day with the actual issue at large.5.7KViews0likes7Comments
Rejected messages
It appears the new spam filtering service Cox is using (cloudfilter.net) is blocking a lot of valid mail. I would like to know where our individual portals and addressbooks are that we can configure our own whitelists and to be able to see what messages are being rejected. It is one thing to be identify a message as spam, and another thing entirely to reject them without notification. I have mail senders from a good number of places and since my mail volume has dropped by over 75%, it is quite safe to assume the spam aggressiveness thresholds are set quite high as well as are the bulk sender identifiers and anti-spoofing features. While you claim to not whitelist senders, you do need to provide your users the ability to do so. No doing so means you are censoring email Also, it is poor form to put a like to review changes and then have it error out. http://postmaster.cox.net/confluence/display/postmaster/Error+Codes If you are going to implement such a service you should become a lot more responsive with corrective actions. I am now on my second day waiting for an answer on my ticket with Tier 2, and third day with the actual issue at large.