Xref: utzoo news.admin:15302 news.software.b:8300
Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!elroy.jpl.nasa.gov!lll-winken!uunet!zephyr.ens.tek.com!tektronix!percy!m2xenix!quagga!undeed!barrett
From: barrett@Daisy.EE.UND.AC.ZA (Alan P Barrett)
Newsgroups: news.admin,news.software.b
Subject: Re: Learning about dropped articles
Message-ID: <1991Jun17.144122.24544@Daisy.EE.UND.AC.ZA>
Date: 17 Jun 91 14:41:22 GMT
References: <1991Jun13.141538.21196@oar.net> <1VgJ46w164w@mantis.co.uk>
Organization: Univ. Natal, Durban, S. Africa
Lines: 26

In article <1VgJ46w164w@mantis.co.uk>,
mathew@mantis.co.uk (Giving C News a *HUG*) writes:
> Besides, are you really suggesting that every user should post to misc.test
> periodically, just to make sure some new revision of C News hasn't moved the
> goalposts and rendered his articles illegal overnight?

The goalposts haven't been moved since December 1987, when RFC 1036 was
published.  (Unless you count the publication in October 1989 of RFC
1123, which updates RFC 822, which is referenced by RFC 1036.)

Mathew, I sympathise with you about having your articles dropped without
notification, but frankly I wish you would shut up now.  While blaming
others for your problems might be emotionally satisfying, it is not very
productive.

I hope that Henry and Geoff will implement a suitable and robust error
reporting scheme some time; indeed, I have every confidence that they
will.  However, that does not alter the fact that any news transport
software is primarily concerned with correctly formatted articles.  If
bad articles are dropped with no more notification than a line in a log
file which might or might not be noticed, then that's certainly
regrettable, but life can be tough sometimes.

--apb
Alan Barrett, Dept. of Electronic Eng., Univ. of Natal, Durban, South Africa
RFC822: barrett@ee.und.ac.za             Bang: m2xenix!quagga!undeed!barrett