[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [leafnode-list] Posting Problem
Matthias Andree wrote:
> leafnode had a function delposted(), which would clean up the
> out.going queue at the end of a fetchnews run, assuming that the failed
> articles had been moved to the failed.postings queue.
I don't agree with you...
delposted() deletes _only_ posted articles using the stringlist *posted.
> However, if all upstream servers are down, the articles are not moved to
> the failed.postings queue, because the postarticles() function has never
> been called.
Of course, true.
> If no server has the group the article has been posted to any more, the
> article is also gone.
Sorry, this is not true.
> Removing the delposted() line will defer the
> article removal to the point where an article with the same Message-ID,
> which should be ours, is found upstream. It breaks (i. e. sends
> duplicates or catches posting errors) if the interval between fetchnews
> runs is longer than the expire time for the corresponding news group and
> history, but usually, articles that predate the history expiry are
> rejected, so removing delposted() should be safe enough. It may slow
> down the posting process because we try to post every article at least
> twice, but better slow than lost.
I may be wrong :-)
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list