Bugzilla

> I expect a timeout issue!

I don't know if you are still seeing this problem. If you suspect a timeout, the only parameter in TB that might affect network timeout is ```mailnews.tcptimeout``` which defaults to 100s. But I doubt that this will help unless wtnet is seeing more than 100s for TB or nmap to respond.

I ran the nmap command shown here: bug 1870909 comment 2. I see the same errors reported there and the time to complete the nmap command is 4.83s. I don't know if those errors are significant.

I can also successfully connect using ```openssl s_client -connect mail.wtnet.de:465``` and execute the ```ehlo charter.net``` smtp command.

> why does it work with several mails but not when sending a single one?

There is a change that is now in 115 that might affect this. But seem like it would have the opposite effect as you describe. But if you are using 115.9 or later and not seeing the problem any more, then this may have fixed it: Bug 1864924.

If you are still having problems, I can do more testing using TB only with a temporary test account at the wtnet server. You can send me the need credentials via email.

> I expect a timeout issue!

I don't know if you are still seeing this problem. If you suspect a timeout, the only parameter in TB that might affect network timeout is ```mailnews.tcptimeout``` which defaults to 100s. But I doubt that this will help unless wtnet is seeing more than 100s for TB or nmap to respond.

I ran the nmap command shown here: bug 1870909 comment 2. I see the same errors reported there and the time to complete the nmap command is 4.83s. I don't know if those errors are significant.

I can also successfully connect using ```openssl s_client -connect mail.wtnet.de:465``` and execute the ```ehlo charter.net``` smtp command.

> why does it work with several mails but not when sending a single one?

There is a change that is now in 115 that might affect this. But seem like it would have the opposite effect as you describe. But if you are using 115.9 or later and not seeing the problem any more, then this may have fixed it: Bug 1864924.

If you are still having problems, I can do more testing using TB only with a temporary test account at the wtnet server. You can send me the needed credentials via email.