All Products Support Forum

First, I am supporting a family member, who has TB configured on two separate machines. Configuring for Comcast IMAP+SMTP, in the usual manner; nothing esoteric about that, all very routine.

Machine A seems to be working okay, no errors. TB up to date on this machine, connected over an ethernet wire, if that makes any difference.

Machine B, getting spam prompted over IMAP 1014 errors. No other information is provided than 1014.

I have tried dropping the account configuration hundred percent, restarting TB, re-adding the account configuration, to no avail. Still spam 1014 errors.

I did happen to notice TB needed an update, so I did that as well. Still 1014 errors.

I have also tried dropping that email saved password from the saved passwords, and responding to the subsequent re-enter password prompt. Also to no avail.

What if anything might have changed, and how can we contend with this? What is so corrupt, do we need to be mucking around in any AppData files, roaming files, etc?

We are not the only ones, apparently, to have bumped into this issue. Not sure if this is also Comcast specific, since a recent TB and/or IMAP specification change, i.e. maybe we try with a gmail account, for instance.

Wondering also, is it IMAP and/or Comcast somehow tieing Machine A to the IMAP and not releasing that association? Knowing a little bit about IMAP in this regard. And/or somehow now prohibiting Machine B+ from establishing a connection?

One of my two gmail accouns has suddenly become impossible to access (cannot receive, cannot send). T'Bird produces an Authentication has Failed notification, after a Google Window headed "Sign in to Mozilla Thunderbird Email" which refuses to go away. Clicking on the 'help' or 'privacy' options in that google window produces no more than a blank window but then "Sign in to Mozilla Thunderbird Email" reappears a few minutes later. My other gmail account doesn't have this problem, so I assume it's not gmail but it's T'Bird.

What's going on?

(BTW signing into this Support resulted in an email "New sign-in to Mozilla Support" warning "New sign-in to Mozilla Support to Firefox on Windows 10". Trouble is, I'm on Windows 11. Trivial maybe, but telling maybe.)