Re: Tin problem - reconnection always needed?

On 5/3/07, Urs Janßen <[email protected]> wrote:
>
> Joey Mukherjee wrote:
> >
> > My guess is the remote site closed the connection (the above error)
> > while I was waiting for the response to LIST overview.fmt cmd.
>
> which is strange as this should only happen after a timeout (600
> secs. default on this server).
>
> > So why can't tin keep this connection?
>
> cause the _remote_ site closed the connection.


I don't believe this to be true.  You say above that there is a timeout of
600 secs on the server, yet my copy of tin needs to reconnect almost
immediately.  Why would the remote connection drop only my client early and
only do it with tin?  Furthermore, every remote NNTPSERVER does this?

As I mentioned earlier, I only have problems with tin.  Sylpheed works.

Clearly the problem is not in the remote site.  The problem may not be in
the tin source either.  I'm guessing it has to do with either an environment
setting on our side or some other insidious network reason, but I don't know
where to look or where to check.  Significantly, connecting from a different
Solaris machine causes the same problem with a copy of tin that has worked
for years.  Compiling tin on my Mac also has the same issue.

Something has changed with our outbound network issues that only tin is
succeptable.  Our IT group has barely heard of Usenet so I don't know what
to ask or tell them.

Any ideas?

Thanks,
Joey