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

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

Denna tråd har arkiverats. Ställ en ny fråga om du behöver hjälp.

Email

  • 2 svar
  • 0 har detta problem
  • 1 visning
  • Senaste svar av rbradburn

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

Vald lösning

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.

Läs svaret i sitt sammanhang 👍 0

Alla svar (2)

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

rbradburn
rbradburn Frågans ägare
more options

Vald lösning

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.