為了改善您的使用體驗，本網站正在進行維護，部分功能暫時無法使用。若本站的文件無法解決您的問題，想要向社群發問的話，請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問，我們的社群成員將很快會回覆您的疑問。

Avatar for Username

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊，或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

此討論串已被封存。 如果您有需要幫助，請新增一個新問題

Error when sending mail

  • 1 回覆
  • 1 有這個問題
  • 1 次檢視
  • 最近回覆由 Matt

Cedric.BONNIN
Cedric.BONNIN
more options

Hello,

I encounter an error when sending a message with an on-premises exchange server. With Windows, an error window appears and is automatically closed. On Linux, the window remains displayed, which is problematic. In both cases, the message is sent and copied to the sent messages folder The windows error message says "copy to sent folder error" (obviously wrong) In console the error raised after QUIT command of mailnews.smtp with the error code 2152398868.

the error was reported by several of our users and I was able to reproduce it.

Console Log : mailnews.smtp: Message sent successfully. SmtpClient.jsm:1293:21 mailnews.smtp: C: QUIT SmtpClient.jsm:579:19 mailnews.smtp: error { target: TCPSocket, isTrusted: true, name: "NetworkError", message: "Network", errorCode: 2152398868, srcElement: TCPSocket, currentTarget: TCPSocket, eventPhase: 2, bubbles: false, cancelable: false, … } SmtpClient.jsm:434:17 mailnews.send: Sending failed; Le message n’a pas pu être envoyé car la connexion au serveur sortant (SMTP) « ******* » a expiré. Veuillez essayer à nouveau., exitCode=2153066800, originalMsgURI= MessageSend.jsm:336:27 mailnews.smtp: S: 221 2.0.0 Service closing transmission channel SmtpClient.jsm:413:17 mailnews.smtp: Closing connection... 3 SmtpClient.jsm:153:17 mailnews.smtp: Socket closed.

Hello, I encounter an error when sending a message with an on-premises exchange server. With Windows, an error window appears and is automatically closed. On Linux, the window remains displayed, which is problematic. In both cases, the message is sent and copied to the sent messages folder The windows error message says "copy to sent folder error" (obviously wrong) In console the error raised after QUIT command of mailnews.smtp with the error code 2152398868. the error was reported by several of our users and I was able to reproduce it. Console Log : mailnews.smtp: Message sent successfully. SmtpClient.jsm:1293:21 mailnews.smtp: C: QUIT SmtpClient.jsm:579:19 mailnews.smtp: error { target: TCPSocket, isTrusted: true, name: "NetworkError", message: "Network", errorCode: 2152398868, srcElement: TCPSocket, currentTarget: TCPSocket, eventPhase: 2, bubbles: false, cancelable: false, … } SmtpClient.jsm:434:17 mailnews.send: Sending failed; Le message n’a pas pu être envoyé car la connexion au serveur sortant (SMTP) « ******* » a expiré. Veuillez essayer à nouveau., exitCode=2153066800, originalMsgURI= MessageSend.jsm:336:27 mailnews.smtp: S: 221 2.0.0 Service closing transmission channel SmtpClient.jsm:413:17 mailnews.smtp: Closing connection... 3 SmtpClient.jsm:153:17 mailnews.smtp: Socket closed.

所有回覆 (1)

Matt
Matt
  • Moderator
  • Top 10 Contributor
more options

Editing the log to remove the server does not make google translate very friendly at all. But I am guessing that somewhere in this mix is a two factor password that has expired. Or a get before send that has expired. What are you using for SMTP authentication?

Recently Exchange online setting have been changed to disable SMTP entirely by default. I have no idea if that could be occurring locally in a security patch. I certainly would no put it past a Microsoft update.