Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

SMTP error on Thunderbird.91.0.3

  • 1 Antwort
  • 1 hat dieses Problem
  • 17 Aufrufe
  • Letzte Antwort von Matt

more options

I installed Thunderbird.91.0.3 under Leap 15.3, and everything worked fine. But I was able to send mail messages only, but no postings to newgroups.

When I tried to post to a newsgroup, Thunderbird.91.0.3 refused to send it, displaying this error message:

          A News (NNTP) error occurred: posting failed

and after pressing "ok":

          Sending of the message failed.
          The message could not be sent using Outgoing server
          (SMTP) smtp.omc-mail.de for an unknown reason. Please
          verify that your Outgoing server (SMTP) settings are
          correct and try again.

An "unknown reason", how nice!

So, I had to return to my good old Thunderbird.78.12.0.

Bye, Wolfgang

I installed Thunderbird.91.0.3 under Leap 15.3, and everything worked fine. But I was able to send mail messages only, but no postings to newgroups. When I tried to post to a newsgroup, Thunderbird.91.0.3 refused to send it, displaying this error message: A News (NNTP) error occurred: posting failed and after pressing "ok": Sending of the message failed. The message could not be sent using Outgoing server (SMTP) smtp.omc-mail.de for an unknown reason. Please verify that your Outgoing server (SMTP) settings are correct and try again. An "unknown reason", how nice! So, I had to return to my good old Thunderbird.78.12.0. Bye, Wolfgang

Alle Antworten (1)

more options

It would be interesting to see if setting "mailnews.send.jsmodule" and "mailnews.smtp.jsmodule" to false fixed the issue.

Thunderbird 88beta introduced a new JS based sendmail.

Those settings revert to the previous sending code. If it does work then it sounds like you have actually found a bug in the new code. Given the exceedingly low numbers actually using NNTP it does not get much exposure in the beta cycle and is unlikely to be fixed unless it get documented as a bug.