In article <8UZV3cun8fXa092yn@swol.de>, rgriech@swol.de (Hardy Griech) wrote: >On Thu, 27 May 1999 19:08:28 -0400, >Andrew@hodgsons.freeserve.co.uk (Andrew Hodgson) wrote: >> The only thing I don't like about vsoup is that it overwrites the x-newsreader >> field, and I would rather not let it put anything in there like souper does. If >> this were the case then I would use it. Is there a way to do this? > >VSoup does not overwrite an existing x-newsreader line! It appends >_another_ x-newsreader line to the header (since 1.2.9.xBeta). >Previously appearing other x-newsreader lines are not touched. > >I'm not sure, if this is RFC compliant, but (nevertheless) I wanted to >get some usage feedback of VSoup. Check >http://www.cs.uit.no/~kjelli/newschart.html for statistitics, although >I'm not sure, which groups were scanned (e.g. is the de.* tree scanned, >I suppose not...). >
Yes I can see your point exactly when you are talking about feedback and
statistics, however, I would rather only have one x-newsreader line, when I used
vsoup before I got two and was flamed in a linux ng for not sorting out my
headers properly, and I would like to keep the yarn header in by default if
possible.
--
Sincerely,
Andrew.
There has been opposition to every innovation in the history of man, with the
possible exception of the sword.
-- Benjamin Dana