We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

protonmail mailbridge

  • 1 antwurd
  • 0 hawwe dit probleem
  • 1 werjefte
  • Lêste antwurd fan Matt

primary1
primary1
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.

Alle antwurden (1)

Matt
Matt
  • Moderator
  • Top 10 Contributor
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.