Vyhľadajte odpoveď

Vyhnite sa podvodom s podporou. Nikdy vás nebudeme žiadať, aby ste zavolali alebo poslali SMS na telefónne číslo alebo zdieľali osobné informácie. Nahláste prosím podozrivú aktivitu použitím voľby “Nahlásiť zneužitie”.

Learn More

[TB] Configuring IMAP with comcast error 1014

  • 2 odpovede
  • 0 má tento problém
  • 1 zobrazenie
  • Posledná odpoveď od Matt

more options

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?

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?

Vybrané riešenie

Sheesh, turns out it was a case of "mistaken identity", incorrect password notations somewhere in our notes. Got it sorted as that. Not helpful, however, that the 1014 error did not include a more verbose explanation; somewhere between the xfinity imap/smtp servers, and TB treatment of the same messages.

Čítať túto odpoveď v kontexte 👍 0

Všetky odpovede (2)

more options

Vybrané riešenie

Sheesh, turns out it was a case of "mistaken identity", incorrect password notations somewhere in our notes. Got it sorted as that. Not helpful, however, that the 1014 error did not include a more verbose explanation; somewhere between the xfinity imap/smtp servers, and TB treatment of the same messages.

Pomohla vám táto odpoveď?

more options

In these situations, Thunderbird simply passes on the error message it is given by the server. It has no way of knowing what that error actually means, so it just passes it along verbatim. Despite common assumptions (often encouraged by support folk I admit), those numbers are largely relevant only to the software package installed on the server issuing the error.

You might also look at this topic which reported the same error. https://support.mozilla.org/en-US/questions/1348887

The very last post is enlightening really if it is still so.

Pomohla vám táto odpoveď?

Položiť otázku

Ak chcete odpovedať na príspevky, musíte sa prihlásiť do svojho účtu. Ak ešte nemáte účet, položte novú otázku.