Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

Este site irá ter funcionalidade limitada enquanto fazemos manutenção para melhorar a sua experiência. Se um artigo não resolve o seu problema e quiser colocar uma questão, temos a nossa comunidade de apoio à espera de o ajudar em @FirefoxSupport no Twitter, /r/firefox no Reddit.

Avatar for Username

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Esta discussão foi arquivada. Se precisar de ajuda, por favor, coloque uma nova questão.

Error when sending mail

  • 1 resposta
  • 1 tem este problema
  • 5 visualizações
  • Última resposta por 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.

Todas as respostas (1)

Matt
Matt
  • Top 25 Contributor
  • Moderator
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.