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!

Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Več o tem

administrative prohibition

  • 2 odgovora
  • 1 ima to težavo
  • 2 ogleda
  • Zadnji odgovor od Ed

more options

Product Thunderbird While sending an email from my email address I get the following message. "An error occurred while sending mail. The mail server responded: Administrative prohibition. Please check the message recipient "email address" and try again. Do not know what is causing this.

Product Thunderbird While sending an email from my email address I get the following message. "An error occurred while sending mail. The mail server responded: Administrative prohibition. Please check the message recipient "email address" and try again. Do not know what is causing this.

Izbrana rešitev

Have you asked the operators of the server you are sending via what the error message you are getting actually means? All Thunderbird's doing is quoting verbatim the message it is given as to why your mail is not going.

From the context, I would guess the email address is not valid. It does not exist or is malformed with perhaps a . after the text.

Preberite ta odgovor v kontekstu 👍 0

Vsi odgovori (2)

more options

Izbrana rešitev

Have you asked the operators of the server you are sending via what the error message you are getting actually means? All Thunderbird's doing is quoting verbatim the message it is given as to why your mail is not going.

From the context, I would guess the email address is not valid. It does not exist or is malformed with perhaps a . after the text.

more options

Finally found the answer. In Thunderbird went into Account settings / my email / Server Settings and changed the Port from 105 to 143. Everything is now working fine.