From: Richard Childers <rchilder@us.oracle.com>
To: cypherpunks@toad.com
Message Hash: 417506eb219da1e82e73552d6004914c7a1de1833128226dae38c41e0f92442b
Message ID: <9211280841.AA23039@rchilder.us.oracle.com>
Reply To: N/A
UTC Datetime: 1992-11-28 08:42:52 UTC
Raw Date: Sat, 28 Nov 92 00:42:52 PST
From: Richard Childers <rchilder@us.oracle.com>
Date: Sat, 28 Nov 92 00:42:52 PST
To: cypherpunks@toad.com
Subject: Re: ping..mailing list integrity..
Message-ID: <9211280841.AA23039@rchilder.us.oracle.com>
MIME-Version: 1.0
Content-Type: text/plain
"So if you posted a message, you could check in the evening if it got
out or not. If you are not sure if you are receiving all the messages,
you could maintain a simlar file yourself, and at the end of day compare
your notes with what is received from the list."
This could be spoofed by an intermediate delivery agent also ...
Generally, in netnews, I regard mail back from individuals or test sites
which honor posts to *.test newsgroups as adequate confirmation. These,
too, could be spoofed, I suppose, but that's a degree of duplicity that
is so complicated to maintain for an indefinite period of time that it is
unlikely to ever be put into practice, IMHO, since it's bound to fail in
the long term, and would probably result in a backlash of disfavor towards
organizations practicing, supporting or funding such behavior.
Perhaps an equivalent service could be implemented where some people's
systems make a point of sending mail directly to posters to verify that
their posting was posted. Bitnet's LISTSERV software does this, which is
very convenient when one is managing a listserver entirely by email from
a few thousand miles away. Other mail servers - Home Brew Digest comes to
mind - do the same thing ...
Grist for the collective mill.
-- richard
Return to November 1992
Return to “yanek@novavax.nova.edu (Yanek Martinson)”