Atozed Forums
Freezing nntp connect at port 563 for some addresses - Printable Version

+- Atozed Forums (https://www.atozed.com/forums)
+-- Forum: Indy (https://www.atozed.com/forums/forum-8.html)
+--- Forum: Indy General Discussion (https://www.atozed.com/forums/forum-9.html)
+--- Thread: Freezing nntp connect at port 563 for some addresses (/thread-1465.html)



Freezing nntp connect at port 563 for some addresses - AndrzejB - 01-03-2020

IdNNTP1.Port:=563;
IdNNTP1.ConnectTimeout:=1500;

Freezing:
de.newsgroupdirect.com
nl.newsgroupdirect.com
us.newsgroupdirect.com
news.alt.net
news.panix.com
news.usenetexpress.com
newszilla.xs4all.nl
secure-eu.news.easynews.com
secure-us.news.easynews.com
secure.news.easynews.com
secure6.news.easynews.com
secure6.news.eu.easynews.com
secure6.news.us.easynews.com

Delayed:
news.usenet.farm
news.vipernews.com


RE: Freezing nntp connect at port 563 for some addresses - rlebeau - 01-03-2020

Are you setting IdNNTP1.UseTLS to utUseImplicitTLS when using port 563? On port 563, an NNTP server requires the client to complete a successful TLS handshake before the server can then issue the NNTP greeting.

Note that modern usage of TLS for NNTP discourages the use of port 563, instead preferring the 'STARTTLS' command on port 119 instead, which delays the TLS handshake until the client explicitly requests permission to initiate the handshake after validating that the server even supports TLS.

Do you have the same problem if you set IdNNTP1.Port to 119 and set IdNNTP1.UseTLS to utUseExplicitTLS?


RE: Freezing nntp connect at port 563 for some addresses - AndrzejB - 01-04-2020

Now is not freezing , thanks,
but is
Code:
procedure TIdExplicitTLSClient.CheckIfCanUseTLS;
begin
  if not (IOHandler is TIdSSLIOHandlerSocketBase) then begin
    raise EIdTLSClientSSLIOHandlerRequred.Create(RSTLSSSLIOHandlerRequired);
  end;
end;
for  de.newsgroupdirect.com (I not sure it is handled ssl)
but anyway not freezing