🚀 go-pugleaf

wolfgang@wsrcc.uucp writes:
   Why do we see all these articles with *Two headers*?  It seems like
   ohio-state.edu or LEHIGH.EDU is pucking perfectly good articles back
   onto the net with a new header tacked onto the top.  Notice that this
   header has a new message ID and a new From field.  What gives?

No, it's not at OSU, and it's probably not at lehigh.edu, either.  The
problem is that, varying slightly from one incantation of news
software to the next, some site out there has the group marked
unmoderated, someone there posts an article, and when the article
first hits a site where it's marked moderated, that site packages up
the article as mail and foists it off on the "moderator."  For
gnu.*.bug groups, this is just the mail reflector at MIT.  The purpose
behind moderating gnu.*.bug is to make sure that things get to
(notably) RMS with a sure-fire mail-replyable header; there are
inherent inconsistencies in the news/mail gateway which sometimes
result in unreplyable headers by the time someone on the mailing list
side would see it.

The really icky thing is that a lot of these news installations add
the extra pile of headers, breaking the From:, and who knows what else
they ruin in the process.

The Solution To The Problem is for sites to finish updating gnu.* as
per the horde of {new,rm}groups I sent out 2 weeks ago and the 2
checkgroups messages sent out the following week.  I could re-issue
the checkgroups one more time, but C News admins tend to develop
problems with adrenalin rushes and feelings of persecution when the
output of their checkgroups tries to convince them to remove 2/3 of
their active file.

Honestly, it works quite well when people adhere to the intended
configuration.

--karl