RE: [leafnode-list] Message-ID already in use.

["Jeff Grossman" <jeff@xxxxxxxxxxx>]

> -----Original Message-----
> From: Matthias Andree [mailto:ma@xxxxxxxxxxxxxxxxxxxxxxxxxxxx]
> Sent: Sunday, November 03, 2002 6:51 AM
> To: leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> 
> Grahame Cooper <Grahame@xxxxxxxxxxxxxxxx> writes:
> 
> > I am fairly new to leafnode, but have spent a lot of time trying to
get
> > it to work properly for me.
> 
> Can you check whether the article is available upstream and if it's
> yours? I believe what you're seeing is an artifact of the current
> implementation, to avoid losing articles.
> 
> In a previous version, we used to post articles to any server that was
> up and then delete the whole queue. This has caused the loss of all
> upstream postings when the network connection went down -- so the code
> was removed, and we may only delete articles in the out.going queue on
> the second fetchnews run that tries to post.

If it worked as you describe above, I probably would not mind this
implementation that much,  But, here is an example of why I don't like
it.

1.  I run fetchnews.  I have 4 servers which I connect to.
2.  Server number 1 posts the article.
3.  Server number 2 does not carry the newsgroup, so nothing happens.
4.  Server number 3 tries to post the article, but the article is
already available upstream, so it discards it.
5.  Server number 4 never tries to post the article because it is
already deleted.

If you made sure that the post was at least tried at each server at
least once, I would not mind.  But, right now, server number 4 will only
be able to get the post if it receives it from another server.  I say
keep the article in the out.going queue for at least a complete
fetchnews run.

Jeff


-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list