Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Sending of the message failed in version 60 (Forwarding Message in Message Filter)

  • 4 wotmołwy
  • 1 ma tutón problem
  • 3 napohlady
  • Poslednja wotmołwa wot user1534406

more options

I used Message Filter to forward message in version 60.0 (32-bit). But, it didn't work.

The following message is displayed.

"Send Message Error Sending of the message failed. The message could not be sent because the connection to Outgoing server (SMTP) 123.456.789.12 timed out. Try again."

It worked correctly in version 52.9.1.

I tried Safe Mode already.

There is no problem with normal mail transmission.


--- OS --- Windows 10 Proffesional and Windows 2008 R2

--- Version --- Thunderbird 60.0 (32-bit) (Both en-US and ja version)

--- SMTP settings--- Server Name : 123.456.789.12 (Dummy number, not alphabetical character) Port : 587 Connection security : None Authentication method : Password, transmitted insecurely

I used Message Filter to forward message in version 60.0 (32-bit). But, it didn't work. The following message is displayed. "Send Message Error Sending of the message failed. The message could not be sent because the connection to Outgoing server (SMTP) 123.456.789.12 timed out. Try again." It worked correctly in version 52.9.1. I tried Safe Mode already. There is no problem with normal mail transmission. --- OS --- Windows 10 Proffesional and Windows 2008 R2 --- Version --- Thunderbird 60.0 (32-bit) (Both en-US and ja version) --- SMTP settings--- Server Name : 123.456.789.12 (Dummy number, not alphabetical character) Port : 587 Connection security : None Authentication method : Password, transmitted insecurely

Wot Wayne Mery změnjeny

Wubrane rozrisanje

Server administrator has specified to use IP address.

Because it is a private server, I use dummy data.

I think Thunderbird 60.0 has a bug.

If asking a question here is mistake, please tell me the appropriate contact.

Tutu wotmołwu w konteksće čitać 👍 0

Wšě wotmołwy (4)

more options

Check what account is chose in "Filters for...". You need to check its SMTP configuration and make absolutely sure it's OK.

You may be sending through another SMTP account while the filters are being applied/used to send via another one.

more options

>Check what account is chose in "Filters for...". I tried both email account and local folder. ver 52.9.1 is OK, 60.0 does not work.

>You need to check its SMTP configuration and make absolutely sure it's OK. SMTP setting is correct because I can send email. Is there special setting for filtering?

>You may be sending through another SMTP account while the filters are being applied/used to send via another one. I use only one account.

more options

why is the error message using an IP address? It is normal to use a dNS resolvable server name in that firld. seeing an IP address usually meant cut price hosting with similarly cut price support and thecnical staff

And do you think you could actually post the correct IP address or domain name? Providing support for specific problems using hypotheticals has knobs on it. It is almost always a complete waste of time as the problem is most often at the server end or the anti virus that thinks it knows how mail works but should not be allowed to operate a firewall or email scanner.

A filter is nothing more than an automation of something you can do yourself. so you will not be finding anything special aout them except when they execute and how fast they go. To this end it is often a good idea to execute them after classification as that ensures a longer time between Thunderbird becoming aware of the message and trying to apply tests against the body content (the last thing to arrive in an IMAP situation).

more options

Wubrane rozrisanje

Server administrator has specified to use IP address.

Because it is a private server, I use dummy data.

I think Thunderbird 60.0 has a bug.

If asking a question here is mistake, please tell me the appropriate contact.