Re: one bad article ruins the fetch for that server

On 14-May-2003 Dan Jacobson wrote:
> Bug: say one has two postings queued for a certain server.  If the
> first one fails, e.g.  441 No valid newsgroups in "alt.cons....
> Then not only will the second article not be tried, but the fetch for
> that server won't be tried.
> 
> Or maybe the server (news.cis.dfn.de) hung up at that point.

Thanks for the report. I've spotted this now - it's a silly bug in the code
that measn that all posting failures get treated as line drops. I'll try to fix
it tomorrow.

> The user isn't notified that something bad happened too.

Same bug. Line drops/lost connections shouldn't get reported to the user but
will be logged - that's assumed an admin problem. If a posting fails the post
should get mailed back to the sender. At present this isn't happening properly.

-- 
Jim Hague - [email protected]          Never trust a computer you can't lift.


-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge