Mozilla 도움말 검색

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

자세히 살펴보기

After update to 102.6.0 cannot connect to IMAP

  • 4 답장
  • 1 이 문제를 만남
  • 2 보기
  • 최종 답변자: chazz_TSC

more options

I have about ten IMAP mailboxes spread across some five different mail servers, two of which I control. Thunderbird downloaded my mail this morning, and asked for an update. I let it update to 102.6.0, and on restart the two mailboxes attacked to Sendmail / Dovecot servers could no longer retrieve mail. One is reporting "The mail server does not support any of the available authentication methods" (paraphrased, more on that below); the other simply sits and spins forever at "Checking mail server capabilities".

Because older versions of TBird do not seem to be available, I downloaded and installed the current beta 109.0b1. This version does not have the "authentication methods" issue, seemingly, but does still sit and spin forever on the other problem mailbox. Because profile format changed between 102 and 109, I cannot backstep to the older version to confirm the error message wording on the first mailbox.

Sometimes when I have a "sit and spin" mailbox, it will turn out that there is a certificate problem; hitting "Get Messages" will then bring up the certificate override window, and allowing the override will then make things work. In this case, it does not; if that's the error (which it shouldn't be, that certificate is current) it's not leting me fix it.

What are my next steps?

I have about ten IMAP mailboxes spread across some five different mail servers, two of which I control. Thunderbird downloaded my mail this morning, and asked for an update. I let it update to 102.6.0, and on restart the two mailboxes attacked to Sendmail / Dovecot servers could no longer retrieve mail. One is reporting "The mail server does not support any of the available authentication methods" (paraphrased, more on that below); the other simply sits and spins forever at "Checking mail server capabilities". Because older versions of TBird do not seem to be available, I downloaded and installed the current beta 109.0b1. This version does not have the "authentication methods" issue, seemingly, but does still sit and spin forever on the other problem mailbox. Because profile format changed between 102 and 109, I cannot backstep to the older version to confirm the error message wording on the first mailbox. Sometimes when I have a "sit and spin" mailbox, it will turn out that there is a certificate problem; hitting "Get Messages" will then bring up the certificate override window, and allowing the override will then make things work. In this case, it does not; if that's the error (which it shouldn't be, that certificate is current) it's not leting me fix it. What are my next steps?

선택된 해결법

Please post a screenshot of the certificate exception prompt. https://support.mozilla.org/kb/how-do-i-create-screenshot-my-problem

What is your anti-virus software?

문맥에 따라 이 답변을 읽어주세요 👍 0

모든 댓글 (4)

more options

선택된 해결법

Please post a screenshot of the certificate exception prompt. https://support.mozilla.org/kb/how-do-i-create-screenshot-my-problem

What is your anti-virus software?

글쓴이 christ1 수정일시

more options

Antivirus software is Windows Defender (lame, I know, but there are reasons). As mentioned, in this case I'm not getting and can't force a certificate exception prompt. I am getting one on a different client and will be checking that, but Thunderbird cannot be coerced into showing me that exception.

EDIT: Yeah, that solved it. Turns out that my mail server had been up for a long time and a certificate had aged out and been replaced, but because Dovecot (the IMAP server) had not restarted, it had not picked up the new certificate. Restarting Dovecot made it pick up the new certificate and made things work. Thank you for the suggestion.

글쓴이 chazz_TSC 수정일시

more options
Antivirus software is Windows Defender (lame, I know, but there are reasons).

There is nothing wrong with Windows Defender and no reason to switch to anything else.

You can try to create an exception in Defender for the Thunderbird profile folder. https://support.mozilla.org/en-US/kb/profiles-where-thunderbird-stores-user-data#w_how-to-find-your-profile

Does the problem go away?

more options

Seems I've tagged the wrong thing as the answer, but it was your certificate suggestion that cured the issue. Thanks for your time.