Re: Remailers needed NOW.

[nobody@cicada.berkeley.edu]

Thanks to Alan Barrett for help with this silly command-line computer
interface, and to all the "Mr. Remailer Operator"s out there. I have
succeeded in automating the task of sending Gary Edstrom's PGP FAQ and
my "Here's How to MacPGP!" guide, chained through two remailers, selected
randomly. You can all worry a little less about not having enough traffic.
Julf can relax now that I'm no longer pumping 1-3 MB of mail through
anon.penet.fi.

I think this should not bomb any remailers too badly, unless they are very
unlucky with the roll of the dice (and I'll see that happening and back off
anyway). Each "session" will involve me waking up in the morning and firing
off between zero and maybe ten packages (5 x ~45K).

The following remailers have worked out, in being fast enough on a regular
basis for me to run a <5 minute "Ping!" test round with a small e-mail to
myself, and not stripping the Subject header from the e-mail. I had to remove
jarthur since it today as is so many days, is adding at least an hour delay so
I cant ping it conveniently.

      1  hh@pmantis.berkeley.edu <-[Very fast.]
      2  elee7h5@rosebud.ee.uh.edu <-[Very fast.]
      2  hfinney@shell.portal.com <-[Fast. Warning header.]
      1  hh@cicada.berkeley.edu <-[Very fast, may die and bounce mail.]
      1  hh@soda.berkeley.edu <-[Very fast, may add an hour.]
      ?  catalyst@netcom.com <-[Fast. Warning header.]

      2  ebrandt@jarthur.claremont.edu <-[Fast, often adds an hour.]

I will however continue to ping jarthur. I imagine I will get to know these
remailers very well, and learn their characters. If I cause any problems, let
me know (the list is faster than anon.penet.fi) and I will adjust my ways. If
it doesn't work out, I can switch to a Netcom account or something instead.

-Xenon