retitle 459980 leafnode: Article propagation problem severity 459980 normal tag 459980 - patch tag 459980 + moreinfo kthxbye
On Thu, Jan 10, 2008 at 12:17:39AM +0100, Michael Weitzel wrote: > Severity: important If this really were a severity important bug it would be affecting everyone who uses Leafnode who uses upstream servers that allow them to post a Path:. Since the behaviour has been as it is for a considerable period of time I would really expect this to have been reported before if it were a general problem. > optimal solution (if possible, the suggestion of the news-server should > be chosen -- tin seems to work like this). Could you clarify what you mean by the "the suggestion of the news-server", please? Also note that Leafnode may be posting the article to multiple upstream servers. > However, the header line "Path: <nntp-server-fqdn>!news" causes a > problem with the news-servers lying upstream to my provider's news-server > and my articles are rejected. I figured out, that the entry "news" is > responsible for this and I suggest to use "Path: not-for-mail" in Could you please explain what it is leads you to believe that this is the case? You have provided none of the analysis that either shows the problem occurring or explains how the changes you suggest would help which makes it difficult to understand your report. I note that looking at a portion of my news spool it seems that if a trailing !news in a Path: were causing problems then something around 10% of articles in some groups would experience problems. > general, since leafnode should (IMO) behave like a news-client, not like > a server. Leafnode is in a very real sense a server to its clients and the direction of development is very much towards adding more server facilities - for example, development versions support both local groups and instantaneous local posting of articles. Do you experience any problems if you configure the FQDN used by Leafnode to be something other than the FQDN of the upstream news server you are using? It is difficult to tell what is happening but based on the information you have provided I would guess that what is happening is that either the upstream server you are using is rejecting your posts or it is also inserting its FQDN into the path, leading to a duplicate path entry which causes some other servers to drop the article as malformed. -- "You grabbed my hand and we fell into it, like a daydream - or a fever."
