How do you prevent someone from deleting anon posts using
forged sender info and the Supersedes: header?

[ Post a follow-up to this message ]

"Willy" <nobody@4096.net> wrote in message
 news:f76d6d1fb5b8dcec7e382ccd6fe88e91@40
96.net...
> How do you prevent someone from deleting anon posts using
> forged sender info and the Supersedes: header?
>
]
most do not honor it.

[ Post a follow-up to this message ]

My apologies for the numrous postings Bob ... but this is what I am
experiencing. I post a message then I am able to supersede it - it is then
removed from my ISPs news feed. I agree it's still on Google but it
indicates that there is some removal possible through this method. I have
found a number of my postings going missing on the local feed - and on
accasion - even from Google!

This should not be confused with the "no archive" that I put in which
allows the message to expire after the 6 days or whatever. Messages are
DEFINITELY being removed (sometimes by other) in a non-moderated NG so it
must be possible.

The question I have then is HOW is it possible to remove messages from NG?

[ Post a follow-up to this message ]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Thu, 25 Jan 2007 13:52:45 +0000 (GMT), Willy wrote in
Message-Id: <098e548aaa40b23a41712fa7def7ace0@4096.net>:

> My apologies for the numrous postings Bob ... but this is what I am
> experiencing. I post a message then I am able to supersede it - it is then
> removed from my ISPs news feed.

I just checked this out on my news server and the superseded message is
not removed. So far as I know the Supersedes header isn't used in
any way by the server, it's a function of the client to act on it.

Try this:
telnet <isp newsserver> 119
head <superseded message-id>
body <superseded message-id>

An example:
In alt.privacy.anon-server.stats,
<20070024.060102.changes.daily@stats.bananasplit.info> is superseded by
<20070025.060102.changes.daily@stats.bananasplit.info>.

$ telnet news.bananasplit.info 119
$ head <20070024.060102.changes.daily@stats.bananasplit.info>

Path: news.bananasplit.info!stats.bananasplit.info
From: Banana Stats <fleegle@bananasplit.info>
Newsgroups: alt.privacy.anon-server.stats
Subject: Daily Mixmaster Remailer Changes
Message-ID: <20070024.060102.changes.daily@stats.bananasplit.info>
Date: Wed, 24 Jan 2007 06:01:02 +0000
Summary: Remailer Statistics
Expires: Fri, 26 Jan 2007 06:01:02 +0000
Supersedes: <20070023.060102.changes.daily@stats.bananasplit.info>
Xref: news.bananasplit.info alt.privacy.anon-server.stats:12429

The superseded message is still there and obtainable.

> The question I have then is HOW is it possible to remove messages from NG?
Depends on the news server configuration.  Most don't honour cancels at
all so once it's posted it's there until it expires and nobody can do
anything about it.  You can override the default expiry behaviour with
an Expires: header, but only within bounds defined in the server
configuration.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

 iQEVAwUBRbjWH2oLu9HNUqmMAQpcaQgAqbVfxigw
bwdb4g0UpkLtdNuuLVrYNNJQ
 rOfCAKIMvnaM2NyaEiETWPYhxvvezq5e2Srw1QR3
e9jXxYqoUNLOYcS0Vdzf1Ge7
4LosS6RFU1yxbA4AfmT67/dtr86KqO9WYs95i4XZJ+MXWi/kNq/cK/kfyoq31r7b
 AmMjKSbjam6f4DI5DriG4BsFhhquRHf5srH+1H7o
Xkvfd2xn7eXXhvlfxe86gghG
sEv7QjJfy+qIIev2f0fJ8iT44Vd1L8HbJiW/IQVPLKZlmjEpUSG22XTN1wkZscEn
SAgH9jjLg0qqKlDLbdfwUnt+z1eBW/+TfhHA0qpgb+7FMZIL191I5g==
=0DR3
-----END PGP SIGNATURE-----

--
pub  1024D/8ED57743 2003-07-08 Bananasplit Operator
Key fingerprint = 796F 67E0 E890 A0BB BDAE  EBB4 94A6 7A09 8ED5 7743
uid                            Admin <admin.bananasplit.info>

[ Post a follow-up to this message ]