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.

تلاش سپورٹ

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.

مزید سیکھیں

Send Message Error / The message could not be sent using Outgoing server (SMTP) for an unknown reason.

  • 2 جواب دیں
  • 0 میں یہ مسئلہ ہے
  • 7 دیکھیں
  • آخری جواب بذریعہ david

more options

From one minute to the next, I received the following message:

Send Message Error / Sending of the message failed: The message could not be sent using Outgoing server (SMTP) smtp.gmail.com for an unknown reason. Please verify that you Outgoing server (SMTP) settings are correct and try again.

Some of the settings are as follows: Server type: POP Mail server / Port: 995 / SSL/TLS / OAuth2 SMTP server port: 465

Thunderbird: 102.11.0

I am not a technical person so this is all that I know to include here.

From one minute to the next, I received the following message: Send Message Error / Sending of the message failed: The message could not be sent using Outgoing server (SMTP) smtp.gmail.com for an unknown reason. Please verify that you Outgoing server (SMTP) settings are correct and try again. Some of the settings are as follows: Server type: POP Mail server / Port: 995 / SSL/TLS / OAuth2 SMTP server port: 465 Thunderbird: 102.11.0 I am not a technical person so this is all that I know to include here.

تمام جوابات (3)

more options

You gave info in incoming server, but just port number for SMTP server. Maybe seeing full info would be useful. Be sure also that you use complete email id, e.g., xxxx@gmail.com

more options

And now, 2 days later, Thunderbird is working. I did nothing. Hmm. Will this continue?

more options

Since the error was for 'unknown reasons', it may have been a server fluke.