搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Protonmail stopped functioning with Thunderbird

  • 3 回覆
  • 0 有這個問題
  • 1 次檢視
  • 最近回覆由 gp

more options

On 22DEC2022, I installed Protonmail (a paid account with the Proton Bridge) on my HP laptop (Windows 10). I was able to configure Thunderbird to send and receive messages. I previously used Thunderbird with a Gmail account for a long time with no issues other than slow speed (rural area, wireless Internet only, Android pad used as hotspot when working online). On 24DEC2022 I organized my Protonmail account from inside the web version by adding a number of folders. I have since been unable to send, receive, or update my Protonmail account in Thunderbird. I have received an error message "no such API" a few times. I have checked my passwords, certificate exception, Bridge settings. Both Gmail and Protonmail are located in the same Thunderbird window. Gmail loads immediately, Protonmail only loads messages up to 24DEC. I have deleted and reinstalled the Protonmail account with no change. My Windows 10 mail application also loads messages up to 24DEC, making me think it's a Proton issue. I have contacted Protonmail support and tried some of their suggestions with no luck. The web version, Android version, and iPhone versions all work fine. I am very limited with technical knowledge on this level. I would appreciate any suggestions but in as simple terms as possible, please! Thank you! P.S. By the way, I am in New York State, USA, if it makes any difference.

On 22DEC2022, I installed Protonmail (a paid account with the Proton Bridge) on my HP laptop (Windows 10). I was able to configure Thunderbird to send and receive messages. I previously used Thunderbird with a Gmail account for a long time with no issues other than slow speed (rural area, wireless Internet only, Android pad used as hotspot when working online). On 24DEC2022 I organized my Protonmail account from inside the web version by adding a number of folders. I have since been unable to send, receive, or update my Protonmail account in Thunderbird. I have received an error message "no such API" a few times. I have checked my passwords, certificate exception, Bridge settings. Both Gmail and Protonmail are located in the same Thunderbird window. Gmail loads immediately, Protonmail only loads messages up to 24DEC. I have deleted and reinstalled the Protonmail account with no change. My Windows 10 mail application also loads messages up to 24DEC, making me think it's a Proton issue. I have contacted Protonmail support and tried some of their suggestions with no luck. The web version, Android version, and iPhone versions all work fine. I am very limited with technical knowledge on this level. I would appreciate any suggestions but in as simple terms as possible, please! Thank you! P.S. By the way, I am in New York State, USA, if it makes any difference.

所有回覆 (3)

more options

I would say you have issues with the bridge software. Proton support should be your port of call for help with it. While they call it a bridge, it is really an IMAP mail server locally installed and that is how Thunderbird sees it. There is nothing simplistic about the code used in the bridge.

The proton folk publish the source of the bridge here. https://github.com/ProtonMail/proton-bridge/issues

I have linked to their open issues page, just in case that offers you some insight into your issue.

more options

Thank you for your response. The problem has been solved, at least, for now. After several conversations with the Proton team, Thunderbird started interfacing properly with Protonmail. The issue is, I'm not exactly sure why. As stated before, I have very limited technical knowledge of these problems. One thing I did was to modify my Windows firewall settings, allowing private networks as well as public. I'll be happy as long as it works, whatever the reason.

more options

earl2910riley said

One thing I did was to modify my Windows firewall settings, allowing private networks as well as public.

That looks very much like the thing that fixed it, because the fake Imap server installed by the provider's software is probably on a private local network.