Arrogant Cheshire succeeds in having Sassaman (randseed)
block him. 

If this kept up, Cheshire would have to run a few extra remailers,
providing himself with chaining ability to and from himself, because
there wouldn't be any other remailers accepting his traffic.

Stupid is as stupid does. (Listening, Frog?)

====================================================
http://freedom.gmsociety.org/pipermail/remops/2003-February/012235.html

[Remops] Cheshire Dest Blocks 

Len Sassaman rabbi@abditum.com 
Wed, 12 Feb 2003 10:03:57 -0800 (PST) 

     Previous message: [Remops] Not The Remp's Place To Play Editor 
     Next message: [Remops] Cheshire Dest Blocks 
     Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] 



On 12 Feb 2003, Cheshire Admin wrote:

> So consider these remailers dest-blocked. I'll wait 24 hours before
> actually doing the blocking, to let mail go through that is already in
> the pipeline:

Thank you. (You may want to wait longer, to give users a chance to update
their reply-blocks if need be.)

> I'm not sure how JBN and QS handle dest-blocks, but it may be that you
> cannot include Cheshire in a list of Auto or Random remailers, because
> of the danger that it will be followed by one of the growing list of
> no-filter dest-blocked remailers, and will have to use it only as the
> last-hop remailer in your chain.

Right. If you destblk other remailers, mail to them will silently be lost,
and random chains using Cheshire anywhere but the last hop are likely to
result in lost mail.

To help prevent this, I have added (cheshire *) to my broken chains list.


--Len.