re :If I do an auto populate attempt,

Does this mean you removed the Imap account and are now attempting to recreate the account ? If yes, then after entering Name, Email address and Password clickon 'Continue' It attempts to locate configuration Then click on 'Configure Manually' button And check everything is correctly set up as server settings stated below.

Please recheck everything - look for typos - make sure Username is full email address. Here are the settings:

IMAP server settings:

• Server name : mail.twc.com
• Port : 993
• Connection Security : SSL/TLS
• Authentication Method: Normal Password
• Username = full email address
• Password = same password you use to access webmail

SMTP server settings:

• Server name : mail.twc.com
• Port : 587
• Connection Security : STARTTLS
• Authentication Method: Normal Password
• Username = full email address
• Password = same password you use to access webmail

After you have carefully rechecked everything including what you see in : Settings > Privacy & Security 'Saved Passwords' imap://account.... and smtp://account... Both need to show correct Username as full email address and Password - identical for incoming and outgoing and must be same as used to access webmail.

Then Exit Thunderbird so it can be forced to update files.

Whilst Thunderbird is closed.... check Firewall This might be the default that came with computer or one controlled by an Anti-Virus you installed. Thunderbird must be set up as an allowed program. You do not want the Firewall blocking anything. Confirm Thunderbird is set up as an allowed app.

Then start Thunderbird and report on results.

Solved it late at night... It turns out it was a Spectrum server issue. The stock reply I kept getting was it was "a known Mozilla Thunderbird error." After doing what you described above, and five days of arguing with tech support for escalation to a supervisor/competent tech, I got to a person who listened to me and understood my testing results. Spectrum changed to a "one password to rule them all" policy scheme. The tech pulled in a server engineer and even got them to check the server logs. It was determined that the issue was two fold.... took fifteen minutes total to fix....

First, their password scheme assumed the TWC server password would accept the same special characters as the website password. However, the TWC server only accepts !@#$%-_ special characters, fewer than the website.

Second, they scheme is supposed to update the server password when you update your website password. It turns out it does not update the TWC server password at all.

So let it be known at this time the TWC servers' passwords have to be updated/reset by hand and it is a specific group separate from the regular path of support that does it. It is now written in my account notes that this group needs to address a password reset on the TWC server. The tech wrote up a report but can not guarantee that the changes needed will be made to the scheme.

AA