[leafnode-list] Bug Report leafnode-2.0.0.alpha20040920a snapshot available

[Matthias Andree]

Jim Gifford schrieb am 2004-10-06:

> >Are you using a "feed-only" (or forward-only) news server for posting,
> >that doesn't have its own article spool?
>    feed-only
> 
> They never delete, it just keeps sending and posting. Here is a link to 
> google news groups, where the problem was noticed
> http://groups.google.com/groups?hl=en&lr=&threadm=mailman.1653.1092782026.2011.bug-bash%40gnu.org&prev=/groups%3Fnum%3D25%26hl%3Den%26lr%3D%26group%3Dgnu.bash.bug%26start%3D200

Ouch. This re-posting should normally be harmless. When leafnode has a
posting in its outgoing queue, it has a unique Message-ID - of a different
format than the postings I see in that thread, and I'd expect it to end
in @jg555.com as the Message-ID for this post has done.

Some software replaced the Message-ID headers, causing duplicates of the
article to show up. Google doesn't provide necessary information for
debugging, even in raw mode they leave out Received:/Path: headers :-(

So the site that tramples over your Message-ID should be fixed to leave
the original Message-ID in place; leafnode will also have to change its
posting strategy in one of the next releases, with per-server queues and
perhaps optionally assigning a _single_ server to post upstream
articles for a certain group, think group-based routing if you wish.

The issue at hand is that leafnode is apparently unaware that the group
is moderated, and the upstream site diligently forwards your post to the
moderator every time it is posted (leafnode's groupinfo file should show
m in the 2nd column where the 1st column is gnu.bash.bug - mine does).

Leafnode will try to post articles to moderated groups only once,
regardless if leafnode itself knows the moderator's address or leaves
the forwarding to the maintainer to the upstream.

Summarized, we see three problems:

1. your leafnode appears to be unaware the group is moderated,

2. someone, perhaps the mailman gateway, replacing the Message-ID by a
new and different one in transit (this MUST be fixed, only that I don't
yet know whose fault it is)

3. leafnode trying to post until the article shows up, rather than
posting until accepted.

-- 
Matthias Andree

Encrypted mail welcome: my GnuPG key ID is 0x052E7D95 (PGP/MIME preferred)