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!

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

Email

  • 2 replies
  • 0 have this problem
  • 1 view
  • Last reply by 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.

Chosen solution

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.

Read this answer in context 👍 0

All Replies (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

Chosen Solution

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.