Mozilla 도움말 검색

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

자세히 살펴보기

Thunderbird 78.10.1 broke IMAP send connection with TLS issue

  • 1 답장
  • 1 이 문제를 만남
  • 5 보기
  • 최종 답변자: christ1

more options

I am occasionally using an e-mail server with out of date TLS settings. Unfortunately, there is no work around for one particular job that I have to do.

When I first was updated to version 78, I got the error described in the string, "can not send mail after update ver78...." I updated my TLS settings as follows: security.tls.version.min = 1 security.tls.version.enable-deprecated = true

And everything seemed to work. However, today, I can no longer send e-mails with that server. It appears that another update broke things again.

I am currently running 78.10.1 on Windows 10. I can receive e-mail, no problem. With the bad server, a test message appears to be sent and gets put in the sent messages folder but doesn't show up in my inbox on another account. I'm not sure of the date but it appears that a message I sent on April 28 worked.

I'm filing a bug report

I am occasionally using an e-mail server with out of date TLS settings. Unfortunately, there is no work around for one particular job that I have to do. When I first was updated to version 78, I got the error described in the string, "can not send mail after update ver78...." I updated my TLS settings as follows: security.tls.version.min = 1 security.tls.version.enable-deprecated = true And everything seemed to work. However, today, I can no longer send e-mails with that server. It appears that another update broke things again. I am currently running 78.10.1 on Windows 10. I can receive e-mail, no problem. With the bad server, a test message appears to be sent and gets put in the sent messages folder but doesn't show up in my inbox on another account. I'm not sure of the date but it appears that a message I sent on April 28 worked. I'm filing a bug report

모든 댓글 (1)

more options

If you did raise a bug you may want to post the bug ID here.