Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Email

  • 2 wótegronje
  • 0 ma toś ten problem
  • 1 naglěd
  • Slědne wótegrono wót rbradburn

more options

Sending of the message failed. An error occurred while sending mail. The mail server responded: <work@email address>: Sender address rejected: not owned by user personal@email address. Please verify that your email address is correct in your account settings and try again.

This message suddenly coming up after a Thunderbird update, and I cannot send messages from my work email because I don't "own" it. How do I fix this?

TIA.

Sending of the message failed. An error occurred while sending mail. The mail server responded: <work@email address>: Sender address rejected: not owned by user personal@email address. Please verify that your email address is correct in your account settings and try again. This message suddenly coming up after a Thunderbird update, and I cannot send messages from my work email because I don't "own" it. How do I fix this? TIA.

Wubrane rozwězanje

Thanks. Solved it anyway eventually. The outgoing server had been reset as a different smtp address for some reason in one of the Thunderbird updates, so kind of a variation on your answer.

Toś to wótegrono w konteksće cytaś 👍 0

Wšykne wótegrona (2)

more options

Some possibilities: - if you aren't using secure settings, your server may not be recognizing you. - if your sending email id doesn't match the SMTP server email id, that would also cause refusal.

more options

Wubrane rozwězanje

Thanks. Solved it anyway eventually. The outgoing server had been reset as a different smtp address for some reason in one of the Thunderbird updates, so kind of a variation on your answer.