Sounds like it might be a problem handling the NNTP protocol we're
receiving from that particular server. I've filed a bug (
http://bugzilla.mozilla.org/show_bug.cgi?id=65975 ) . If you have a
bugzilla account, you can add yourself to the cc list and attach a
protocol log to the bug, captured during a run when you see the problem
(preferrably when it happens after 8 articles instead of 500!) If you
don't have or want a bugzilla account, you can send the protocol log to
me ([EMAIL PROTECTED]) and cc [EMAIL PROTECTED]
Here are instructions for generating a protocol log:
http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap
To answer your questions, in general, we use the same connection for
each message. If the message load gets interrupted, we will drop one
connection, and open a new one (but we should be logging out of the
first connection).
- David
Gord McFee wrote:
> I apologize if I am posting this in the wrong place. Quite frankly, I
> don't even know if it is a bug, except that it only happens with
> Mozilla. Bear with me.
>
> When I am reading news, I unpredictably get the following message, only
> with one of the newsservers (I have 3):
>
> <message>
>
> A News (NNTP) error occurred: Too Many Connections [sympatico-dial
> allows 5 per host/0 per feed (0==nolimit)] (Typhoon v1.2.2)
>
> <end message>
>
> Once this message occurs, I cannot open any more posts on that server
> unless I close Mozilla all the way down and restart it. The message
> does not occur with any frequency that I can determine, e.g. I can read
> 500 articles and suddenly it starts out of the blue; with tonight's
> build, it started on about the 8th article I read. Thus, I can't see
> any connection between the actual number of articles I open and the
> message. I was wondering if there is some reason the connection would
> not be being closed when I move from article to article, but would
> imagine that would mean it would happen on all servers and with a
> determined frequency, neither of which is the case. Finally, it only
> happens with Mozilla. I have tested under Forte Agent, Outlook Express
> and Netscape Communicator 4.76.
>
> Since I know I lost my mind several years ago, I was wondering if anyone
> knows what the alternate explanation is?
>
> Thanks.
>
