I have Outlook for Mac2011 on a MacBook Pro. This morning my Outlook stopped working. When I went into the Cox website they said they were doing maintenance. Since then, my Outlook won't work although my iPad is fine. I was in the Cox chatroom for over an hour and they can't fix the problem. Anyone else have this issue?

Update: i was on the phone with Technical Support this morning and they are aware of the problem; HOWEVER they do not why it is occurring and recommended contacting Microsoft. I was told by the Cox technical engineer that It appears the issue is just with Outlook for Mac 2011 and not the later versions. One solution for 2011 is to delete the account and open a new one although they were not confident how long that would last. I ended up purchasing Office for Mac 2016 which includes Outlook, Word, Excel and Powerpoint for $79. Once prompted for my account particulars, Outlook automatically connected into Cox and my emails downloaded. The 2016 version for the server has IMAP/POP and automatically did its thing including picking the port values. So one approach is to upgrade. Take care though. I could not upgrade to 2019 SW since my MacBook has the El Capitan OS as the latest and last for my dated MacBook Pro and that can't support the latest Microsoft 2019 products. Good luck with whatever approach you choose.

See my separate post on the solution to the problem that worked for me: https://forums.cox.com/forum_home/internet_forum/f/internet-forum/24512/i-fixed-my-outlook-email-problem-after-cox-maintenance

I am having the same problem - Mac2011 Outlook won't work. I can access email through webmail - but nothing since 11:20pm last night on my Outlook.

Hi, Please use this link and check the settings www.cox.com/.../updating-email-client-settings-to-protect-your-information.html. Jonathan J Cox Moderator

Outlook for Mac Email problem after Cox maintenance

43 Replies

Reinhard
New Contributor II
Update: i was on the phone with Technical Support this morning and they are aware of the problem; HOWEVER they do not why it is occurring and recommended contacting Microsoft. I was told by the Cox technical engineer that It appears the issue is just with Outlook for Mac 2011 and not the later versions. One solution for 2011 is to delete the account and open a new one although they were not confident how long that would last. I ended up purchasing Office for Mac 2016 which includes Outlook, Word, Excel and Powerpoint for $79. Once prompted for my account particulars, Outlook automatically connected into Cox and my emails downloaded. The 2016 version for the server has IMAP/POP and automatically did its thing including picking the port values. So one approach is to upgrade. Take care though. I could not upgrade to 2019 SW since my MacBook has the El Capitan OS as the latest and last for my dated MacBook Pro and that can't support the latest Microsoft 2019 products. Good luck with whatever approach you choose.
- KC5
  New Contributor III
  Thanks for the update. I did the same and upgraded and now everything is back working.
blackeneth
New Contributor III
See my separate post on the solution to the problem that worked for me:

https://forums.cox.com/forum_home/internet_forum/f/internet-forum/24512/i-fixed-my-outlook-email-problem-after-cox-maintenance
- lobu
  New Contributor
  Unfortunately, this fix is for Windows computers and there doesn't seem to be a readily available similar fix for Macs. Also "blackeneth" indicates he's using IMAP for email. Most if not all the problems discussed in this topic refer to POP receiving problems mostly on Macs. Sad that COX has done nothing to explain or address this issue and like so many issues, this one will probably die here as well, forcing affected users to either switch to IMAP or change their email clients.
  - KevinM2
    Former Moderator
    Hi Lobu, we generally do not provide support for email client servers, aside from instructions on setting up the email client, as well as information on server settings. At this time, we recommend contacting Outlook or Microsoft directly, for additional support. For POP settings, we recommend 995, with a TLS or SSL/TLS encryption. The security encryption version your email client uses is dependent upon your device operating system and email client versions. Please make sure your device's opearting system is up-top-date.
    
    www.cox.com/.../pop-or-pop3-server-settings.html
    
    -Kevin M. Cox Support Forum Moderator
KC5
New Contributor III
I am having the same problem - Mac2011 Outlook won't work. I can access email through webmail - but nothing since 11:20pm last night on my Outlook.
KC5
New Contributor III
I am having the same problem - Mac2011 Outlook won't work. I can access email through webmail - but nothing since 11:20pm last night on my Outlook.
- JonathanJ
  Former Moderator
  Hi,
  
  Please use this link and check the settings www.cox.com/.../updating-email-client-settings-to-protect-your-information.html.
  
  Jonathan J
  Cox Moderator
  - Reinhard
    New Contributor II
    my settings are precisely what is described in the link Jonathan J sent. When i open Outlook, I receive a message that " a unknown error occurred in Outlook" The details state that Outlook could not receive mail. Error code 150
JTA
New Contributor
I'm also having issues with receiving emails on my Mac. This must be something Cox is doing because others are having a problem too. I can send, but can not receive. This also just happened.
- Reinhard
  New Contributor II
  Very interesting. Based on your post, I discovered I can send email as well. That tells me it is a POP connection issue.
  - KC5
    New Contributor III
    I just tested mine too - I can SEND email as well.
LPalmer
New Contributor
Yes!! Can't receive or send on Outlook. MacBookPro and Outlook for Mac2011 as well. I have set the settings for receiving and sending as indicated by Cox. Can receive fine through cox webmail and on iPhone with Mail app. Come on Cox!!!
KC5
New Contributor III
I still can't receive emails as of this morning, Friday 12/6. Can anyone else?
JTA
New Contributor
I can't believe that the only solution to not receiving emails is to upgrade my outlook. Cox has done something to make our outlook unable to receive emails. You'd think that the techs would know what that was and fix it. Please cox, fix the issue or let us know what to do. Everybody with Outlook 2011 that's having issues is because something on Cox's end has changed. Thank you for your help.
- KevinM2
  Former Moderator
  JTA, on myemail.cox.net, are you able to send and receive emails? Using one email address, can you please send yourself a test email on myemail.cox.net, to see if you can send and receive emails? If you are able to send and receive emails on myemail.cox.net without any issues, please change your password on the Cox website, http://bit.ly/2KOrZnd. Once the password is changed, please ensure the password matches both the incoming and outgoing settings.
  
  Cox made changes to our email server back in April, to ensure the safety and security of customer privacy information. Cox no longer supports sending email through email clients using SSL security encryption version 3.0 or older. SSL / TLS encrypts information from potential thieves as it is sent from one location to another, such as when sending email messages. Choosing to encrypt with SSL / TLS provides added security to email. -Kevin M. Cox Support Forum Moderator
  - JKT
    New Contributor
    I've tried the changing of the password. That did not work. Problem is definitely with incoming mail. Please advise next steps.
lobu
New Contributor
I too am having problems with Outlook not receiving email since 12/5/2019. I spent a long time in the chatroom. The agent kept trying to upsell me to a support protection plan-Cox Complete Care. He couldn't help me.
amco
New Contributor
I have the same problem with my Mac11 Outlook that occurred at the same time. Cox tech support won't help and says it is a Microsoft issue.
- Kim_P
  New Contributor
  Not a Microsoft issue - nothing changed on the Microsoft side of the problem. Clearly a cox issue. They either stopped supporting something (which means we''re stuck with the upgrade problem), or they broke something on Dec 5 (the more likely answer)