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

After installation to 115.4.1 for Thunderbird get SMTP Timeout messages. Messages send ok.

  • 6 respostas
  • 1 tem este problema
  • 23 visualizações
  • Última resposta por John Holmes

more options

Timeout message(s) show up after message(s) sent. Began after update to 115.4.1 (32 bit) level. Messages send OK.

Timeout message(s) show up after message(s) sent. Began after update to 115.4.1 (32 bit) level. Messages send OK.

Modificado por Wayne Mery a

Todas as respostas (6)

more options

Does it happen mainly when sending a message to multiple recipients? (vs a single recipient)

Does it happen less in Windows safe mode? https://support.microsoft.com/en-us/help/12376/windows-10-start-your-pc-in-safe-mode

more options

Single or multiple messages get SMTP timeouts, but messages send OK. This started right after the update as best I can tell. I use filtering and it occurs when a message received and forwarded by filter action.

more options

Have different accounts and occurs on both servers so it seems the update is involved.

more options

> I use filtering and it occurs when a message received and forwarded by filter action.

Only when filters are involved?

more options

It appears that is the case. Will figure out a test to see. Usually it takes a few seconds for messages to pop up after activity. Will watch when messages come in to see if it's only the filter actions on the incoming messages that have filters. A test may help determine.

more options

Sent message from account(A) to account(B) and no message. Created filter to forward to account(C) and used Run Now button for filter and message sent OK. A few seconds later got message. "Sending of the message failed. An error occurred while sending mail: Outgoing server (SMTP) error. The server responded: timeout (#4.4.2)." This test involved 2 different Output Servers and my 3 accounts. Filter action involved for sure.