Prohledat stránky podpory

Vyhněte se podvodům. Za účelem poskytnutí podpory vás nikdy nežádáme, abyste zavolali nebo poslali SMS na nějaké telefonní číslo nebo abyste sdělili své osobní údaje. Jakékoliv podezřelé chování nám prosím nahlaste pomocí odkazu „Nahlásit zneužití“.

Zjistit více

version 115 forwarding email times out

  • 7 odpovědí
  • 0 má tento problém
  • 1 zobrazení
  • Poslední odpověď od Wayne Mery

more options

Ever since upgrading to Thunderbird 115 forwarding email does not work consistently.

I get this error very often

Sending of the message failed. An error occurred while sending mail: Outgoing server (SMTP) error. The server responded: Timeout - closing connection.

Learn more at
https://support.google.com/a/answer/3221692 p8-20020a05620a22e800b0077d6470241asm1303304qki.61 - gsmtp.
Ever since upgrading to Thunderbird 115 forwarding email does not work consistently. I get this error very often Sending of the message failed. An error occurred while sending mail: Outgoing server (SMTP) error. The server responded: Timeout - closing connection. Learn more at https://support.google.com/a/answer/3221692 p8-20020a05620a22e800b0077d6470241asm1303304qki.61 - gsmtp.

Upravil uživatel Wayne Mery dne

Všechny odpovědi (7)

more options

What is your anti-virus software?

more options

Windows Defender

more options

Try to start Windows 10 in safe mode with networking enabled.

Does the problem go away?

Windows safe mode disables anti-virus software. This is a troubleshooting step, not a solution.

more options

Started up in safe mode, got the same message on forwarding emails on 3 Emails to @fuse.net. Changed them to a gmail address and the outgoing server to smtp gmail.

more options

Went back to normal W10 and got the message while sending out on smtp gmail server to gmail and hotmail address.

more options

Went back to safe mode. Two emails from herberthome5760@gmail.com to ja.herbert60@gmail.com, one got through and the other got the smtp error. The one with the smtp error was sent at 3:20pm and the one that went through was sent at 3:32PM.

more options

There is a general timeout bug which is being worked on