Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기
이 쓰레드는 보존되었습니다. 만약 도움이 필요하시면 새로운 질문을 올려주세요.
Solved 보존

[TB] Configuring IMAP with comcast error 1014

Thunderbird 개인 정보 및 보안 설정
Matt replied
Michael Powell
Michael Powell

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?

모든 댓글 (2)

Michael Powell
Michael Powell 질문자

선택된 해결법

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.

Matt
Matt
  • 상위 25 공헌자

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.