[0.7.5] 'test server' in config fails for ssl-servers

[dijsil]

Version: 0.7.5
OS: debian linux
Install-type: python source
Firewall Software: None
Are you using IPV6? no
Is the issue reproducible? yes

Whenever I fill in the server details for an ssl-connection (port 563 & 'ssl' checked) ans I hit 'test server', I get '[Errno 111] Failed to connect: (110, 'timed out') -1@<server>:563'
If I then only decheck 'ssl' and change the port to '119', the test succeeds.

This is while already downloading from the server through an ssl-connection, so there's no question as to whether it would be an offline server, only 'test server' fails, downloading with these details however works fine.

[shypike]

Often Usenet servers have different URLs for normal and for SSL traffic.
Just changing the port and the SSL toggle isn't always enough.
Example:
ssl-us.astraweb.com versus us.news.astraweb.com

[dijsil]

As I mentioned, I am downloading ok with given settings, it is only the 'test server' that will always fail.
The servers in question use the same settings for ssl & non-ssl traffic, only the port is different (563 instead of 119)

[shypike]

Yeah, didn't read the last part very carefully
Which server is this exactly? So that I can check what's going on.
It's not a general problem, since I can test all of my five Usenet servers properly.
Do you "test server" during download or when paused?

[dijsil]

I had not tested it yet while pausing the downloads, and then it works fine.

Sorry for taking your time

[shypike]

Ideally it should work while downloading, and most of the time it does.
Future improvement.