Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Thunderbird gives this msg when trying to login to my Cox account...Sending pw did not succeed, the mail server says my cox account is inactive.

  • 2 replies
  • 3 have this problem
  • 73 views
  • Last reply by mrthrills

more options

I have my Cox email account associated with Thunderbird. Today when I opened Thunderbird I got a msg stating: Sending of password for user rbills1 did not succeed. Mail server pop.central.cox.net responded: account is currently inactive. I contacted Cox and they said my account is not inactive. They reset my Cox email password but when I changed to that password in Thunderbird I got the same msg. When I click on the OK button under the account is inactive msg it goes to a window that gives me the option of setting up a new pw which I tried twice. The same msg still pops up. I have 2 gmail accounts associated with Thunderbird that are working just fine. It is only the Cox account that I am having trouble with. Any help with this problem would be greatly appreciated. TY. Please reply using the mrthrills@gmail.com account.

I have my Cox email account associated with Thunderbird. Today when I opened Thunderbird I got a msg stating: Sending of password for user rbills1 did not succeed. Mail server pop.central.cox.net responded: account is currently inactive. I contacted Cox and they said my account is not inactive. They reset my Cox email password but when I changed to that password in Thunderbird I got the same msg. When I click on the OK button under the account is inactive msg it goes to a window that gives me the option of setting up a new pw which I tried twice. The same msg still pops up. I have 2 gmail accounts associated with Thunderbird that are working just fine. It is only the Cox account that I am having trouble with. Any help with this problem would be greatly appreciated. TY. Please reply using the mrthrills@gmail.com account.

Chosen solution

There is stupid, and then there is ISP technical support. Personally I find it is a very special kind of stupid.

POP.central.cox.net is not the recommended server name for cox email there page here indicates the server name should be simply pop.cox.net

I suggest you right click the account in Thunderbird, select settings from the menu and change the server settings to those provided by the cox web site. You should also select the outgoing server (SMTP) entry and correct the SMTP server setting as well.

I assume cox have changed their server names as I remember that silly eastern central stuff from years ago. My guess is now they are blocking connections from those that did not update their settings. Normally an ISP will notify by email of such changes about a year in advance of the final switch off, but as to timing I am guessing.

So back to my original statement. There is stupid, and then there is ISP support. They changed something and lack the skills to either identify the error they created or correct the issue when asked what is wrong. Very special really.

Read this answer in context 👍 6

All Replies (2)

more options

Chosen Solution

There is stupid, and then there is ISP technical support. Personally I find it is a very special kind of stupid.

POP.central.cox.net is not the recommended server name for cox email there page here indicates the server name should be simply pop.cox.net

I suggest you right click the account in Thunderbird, select settings from the menu and change the server settings to those provided by the cox web site. You should also select the outgoing server (SMTP) entry and correct the SMTP server setting as well.

I assume cox have changed their server names as I remember that silly eastern central stuff from years ago. My guess is now they are blocking connections from those that did not update their settings. Normally an ISP will notify by email of such changes about a year in advance of the final switch off, but as to timing I am guessing.

So back to my original statement. There is stupid, and then there is ISP support. They changed something and lack the skills to either identify the error they created or correct the issue when asked what is wrong. Very special really.

more options

TY Matt!! Your solution worked and yes you would think the Cox rep would have mentioned the server name had been changed. I have been using the pop.central.cox.net name for years and didn't think about asking about it. Simple solution and I want to TY again.