Bernd Rose wrote:
Lars Anders wrote:
In 40tude Dialog when computer lose or slow Internet and then reconnect but >> I next try to get new messages in Newsgroup A, it will not get messages.
...
I lower all timeouts in
"Settings => General settings => Connections => Available"
Only "Disconnect from servers" should matter in your case. Monitor the "Connections" count on the right side of the status bar. As long as it
is not zero, pending connections are kept open.
Apart from aforementioned timeout you also should consider ticking *off*
"Use pipelining" within the server settings. Pipelining assumes stable connections with reduced handshake overhead. In cases with frequent connection losses, this assumption is clearly wrong.
https://datatracker.ietf.org/doc/html/rfc3977#page-22
Looks like erratic connects are not the only cause.
"However, certain server implementations throw away all text received
from the client following certain commands before sending their
response. If this happens, pipelining will be affected because one or
more commands will have been ignored or misinterpreted, and the client
will be matching the wrong responses to each command."
Elsewhere in the RFC is noted some commands, like session admin
commands, must not be pipelined. Supposedly Dialog already knows those.
Any idea how much performance boost that pipelining affords?
For e-mail servers, connecting to them usually returns an OK status
along with a list of keywords mentioning the capabilities of the server.
For example:
telnet imap.comcast.net 143
returns a status of (in 1 line, not wrapped as shown below):
OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ STARTTLS LOGINDISABLED] Dovecot ready.
I didn't see that when connecting to my NNTP server via:
telnet news.individual.net 119
I tried sending the CAPABILITIES command after login to the NNTP server,
but got a "What?" meaning it didn't understand the command. However,
from the examples of multi-line status returned by the CAPABILITIES
command, showing the server supports pipelining is not one of the
reported statuses. I'm not sure how you can determine if the NNTP
server supports pipelining.
"Except where stated otherwise, a client MAY use pipelining. That is,
it may send a command before receiving the response for the previous
command. The server MUST allow pipelining and MUST NOT throw away any
text received after a command. Irrespective of whether pipelining is
used, the server MUST process commands in the order they are sent."
Okay, pipelining must be supported by the server, but that may only
apply to NNTP servers that are RFC 3977 compliant. The OP didn't
mention to which NNTP server(s) he was connecting. RFC 3977 was
ratified back in 2006. Give another 6 years for adoption, and NNTP
server should be supporting pipelining since, at least, 2012 - 20 years
ago. But that doesn't stop someone from running an ancient NNTP server,
or a non-compliant one.
The OP is an AOIElian for his thread here. Presumably that's the NNTP
server to which he is connecting when there are connection faults. I've
had pipelining enabled in Dialog for decades, and I've used AIOE in the
past, and don't remember AOIE reports as non-pipeline supporting.
The OP mentioned losing Internet access, and then having to switch
between newsgroups (perhaps on the same NNTP server, or perhaps to
different NNTP servers). I've seen where a loss in Internet access was
caused by loss of the IP bind with the DHCP server. The ISP might
reprovision the cable modem, or there was a power outage and the old
binding expired requiring a new DHCP binding. When that happens, and
instead of rebooting the client hosts downstream of the DHCP server, I
can often run:
ipconfig /release *
ipconfig /flushdns
ipconfig /renew
ipconfig /renew6
Usually just getting rebind on IPv4 works alone, so the /renew6 for IPv6
is superfluous. My setup supports both IPv4 and IPV6 connects, so I do
both for assurance. Bindings survive their expiration, so you could
have a binding that is days, weeks, or months old, but once there is a disconnection, the expired binding has to be renewed with a new one with
a later expiration. My ISP doles out binding that expire in 3 days, but
I usually don't lose it until there is a power outage, I've bounced the
power to the cable modem, or the ISP decides to do some DHCP work that
voids my binding.
Since the OP is just switching between newsgroups (same or different
NNTP servers), could Dialog be forcing a rebind from the DHCP server?
The OP reported only Internet problems with Dialog, not if the Internet
was still accessible via other net clients, like a web browser.
In addition:
I configure Dialog to hide signature blocks as they are typically
off-topic (to the thread, the newsgroup, or both) or is ego fluff. I
didn't notice the OP put the following into a sigblock until I looked at
the raw source of his message (to see his headers to note through which
NNTP server he posted here):
And what does "Minimal blocking threads" describe setting?
No idea why the OP put his 2nd inquiry into his sigblock. I searched
Dialog's on help on "blocking threads" which found the section in the
Help at:
How Dialog works
Threads and Jobs
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)