This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

protonmail mailbridge

  • 1 reply
  • 0 have this problem
  • 8 views
  • Last reply by Matt

more options

since around 18 December 2022 I have not been able to send mail with thunderbird using the proton mail bridge. The error message I am getting tells me to "blame it on the weather" ? I am using Starlink as an ISP and as of now they do not offer e-mail. I have been using starlink and a paid protonmail account for several months.

since around 18 December 2022 I have not been able to send mail with thunderbird using the proton mail bridge. The error message I am getting tells me to "blame it on the weather" ? I am using Starlink as an ISP and as of now they do not offer e-mail. I have been using starlink and a paid protonmail account for several months.

All Replies (1)

more options

primary1 said

The error message I am getting tells me to "blame it on the weather" ?

I started this by writing the following.

How about the "real" error message. It might be gibberish to you, but it might actually mean something to others.

Then I popped over to github and searched the source code for the bridge, and that ludicrous error message popped up, with added information. https://github.com/ProtonMail/proton-bridge/search?q=Weather

SMTP response is "SMTP error: 554 5.0.0 Error: transaction failed, blame it on the weather: failed to create new parser: unexpected EOF"

and

SMTP response is "SMTP error: 554 5.0.0 Error: transaction failed, blame it on the weather: backend: invalid email address: not owned by user"

So which of these applies to you. I will guess it is the latter and the email address you are using does not match the one registered with proton. This may be as simple as the spelling of case used to express the address or even the existence of a space character in the from address.