🚀 go-pugleaf

Far too many people want others to solve their problems for them.  The
right way to solve any problem is to address it oneself.

mathew@mantis.co.uk writes:
   But first they have to somehow find out about the dropping.

So test your ability to reach the known universe:

	[52] [10:04am] ashley:/usr/lib/news> fgrep .test newsgroups
	alt.test                Alternative subnetwork testing.
	bit.test                Simply for testing.
	biz.test                Biz newsgroup test messages.
	dnet.test
	eunet.test              EUnet-wide test group.
	gnu.gnusenet.test       GNU's Not Usenet alternative network testing.
	misc.test               For testing of network software.  Very boring.
	oar.test                Testing OARnet propogation?
	sub.test                Fuer Superschachteln und andere wichtige Tests
	trial.test              Testing of the Trial distribution.
	u3b.test                3B Distribution Testing.
	unix-pc.test            Test group.
	vmsnet.test             Test messages.
	[53] [10:04am] ashley:/usr/lib/news>

Pick one or more; I recommend misc.test with a world distribution.
Auto-responders for *.test the world over will babble happily at you
about your postings, if and when they get them.  Lack of response is a
wonderful indicator of failing software.  If necessary, you can then
argue with your feed's newsadmin over the issue.

So much for non-notification.  Anyone suspecting that their articles
aren't escaping the local feed's gravity well can always attempt a
*.test posting to see what comes back.

--karl