Frog's vendetta with Sassman has nothing to do with
the events of 9/11. It has its genesis in the situation
described below by Len Sassaman (randseed)

http://www.google.com/groups?q=frog+abuse+group:alt.privacy.anon-server+author:sassaman&hl=en&lr=lang_en&ie=UTF-8&newwindow=1&safe=off&scoring=r&selm=Pine.LNX.4.30.QNWS.0209131201060.18345-100000%40thetis.deor.org&rnum=1

From: Len Sassaman (rabbi@abditum.com)
 Subject: Re: Repost: Salon.com: Send in the Online Spooks?
 Newsgroups: alt.privacy.anon-server
 Date: 2002-09-13 12:16:44 PST


On Fri, 13 Sep 2002, Anonymous wrote:

> On Fri, 13 Sep 2002, Len Sassaman <rabbi@abditum.com> wrote:
>
> >you may wish to run your own remailer.
> >
> >It benefits you, as you have a trusted hop to rely upon. It benefits
> >the network and the users, since we have another remailer (and one
> >with a remop who is obviously not going to collude with me!).
>
> If your hostility leads you to dest-block such remailer, the same way
> your xenophobia ultimately led you to dest-block the french
> remailers, another broken link will be of little use to the network.
> Newcomers try to send a few messages, and if none of their posts
> emerges, their conclusion will be: "remailing doesn't work",
> "remailers suck", "I give up". It won't be: "Len Sassaman suffers
> permanent PMS".

First, let me point out that broken links are easily observable via the
pinging websites.

Secondly (and this, I hope, will be the last time I have to revisit
these issues), let me state that it is my impression that there is no
bad blood between Frog-Admin and me.

Over a year ago, he and I had a public disagreement over his use of a
third-party ISP's abuse address in frog-remailer's return address, that
was resulting in bounce messages from randseed's auto-responder
flooding that ISP, causing them to complain to me. Frog-admin did not
realize this would occur, and corrected the problem and apologised once it was
brought to his attention. I had made a flippant remark about him that
was more offensive than I had intended it to be, and I apologised for that. End
of story, end of issue. Frog-Admin and I are again on good terms.

A separate problem occurred early this year: someone was flooding the
remailer network, apparently targeting frog. Mail was coming to
randseed via multiple other remailers (including a lot of mail from
frog-remailer), all destined for frog-remailer. Frog-remailer was not
able to keep up with this heavy flood, and was answering lots of connections from
randseed but not properly accepting the mail or closing the connections.

This was causing sendmail on randseed to consume a huge amount of
system resources, which threatened to bring randseed to its knees. I
acted quickly to ensure that randseed stayed up by blocking the flood of
messages heading to frog-remailer. Had I permitted this flood to
continue, it was likely that randseed would have been brought down,
resulting in even more mail loss. Given the option of breaking (randseed frog) or
(randseed *), I chose the former. I acted based on the technical
circumstances. My actions had nothing to do with the fact that the
other remailer involved in this was run by Frog-Admin.

As a footnote, that day I replaced sendmail with postfix on randseed,
and have not witnessed such problems since. Mail to frog-remailer has
been flowing smoothly.

--Len.