#<text/x-pgp -----BEGIN PGP SIGNED MESSAGE----- In message <199411171606.AA18990@xtropia> you write:
here are some other ideas to consider in addition to or instead of the 20k limit: * require encryption for incoming messages.
Good idea in theory but won't work in practice. The stats generated by the anonymous remailer show that less than 40% of the messages passing thru are encrypted. Most people would find being forced to encrypt a huge inconvenience. BTW everyone, when I say stats, I mean the primitive stats generated by the remailer and are available to anyone sending email to remailer@jpunix.com with the subject being remailer-stats. Don't start asking me if I get these stats by logging! I don't log.
* require that the sender, the receiver, or both be a known remailer address. at least one other remailer has to be involved.
You are talking about fortress remailers. This is currently under discussion. Stay tuned.
* impose a 20k limit on message unless they are received from a known remailer and sent to a known remailer.
Good in theory once again, but bad in practice. This would entice the abusers to jeopardize several remailers instead of just one. Every remailer that spam/proprietary-stuff goes through would be potentially at risk also. If remailers are going to be legally jeopardized, I would think the impact would be less if it were one instead of many. But, there is also safety in numbers. Hmm... John A. Perry - KG5RG - perry@jpunix.com WWW - http://jpunix.com PGP 2.62 key for perry@jpunix.com is on the keyservers. PGP-encrypted e-mail welcome! Finger kserver@jpunix.com for PGP keyserver help. Finger remailer@jpunix.com for remailer help. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: Finger kserver@jpunix.com for PGP keyserver help. iQCVAwUBLsvawFOTpEThrthvAQGQQgP/RMC1DZXKPfGQzQd+3TQv8czp9AGRvuAq 8sTiJ+vt8XLrSumZ+2UUHSv/wJovA5pq64lC0U4EtrZY9t6rexnSmgDrBnLyn5VJ wZ/bi+0GQa7xxfcxJWgqf372n/RjNT3Kbpg6XhNF1dQtwpq3VMkKbHqfsvwDdR2h 65kzLPGd5VA= =P/Bk -----END PGP SIGNATURE----- #