From: sameer <sameer@c2.org>
To: hughes@ah.com (Eric Hughes)
Message Hash: 5a605b8797980e9848959167e19f937f6ea98dc51dbe26d88a1c0c9653af1948
Message ID: <199409180143.SAA16949@infinity.c2.org>
Reply To: <9409172331.AA12848@ah.com>
UTC Datetime: 1994-09-18 01:45:47 UTC
Raw Date: Sat, 17 Sep 94 18:45:47 PDT
From: sameer <sameer@c2.org>
Date: Sat, 17 Sep 94 18:45:47 PDT
To: hughes@ah.com (Eric Hughes)
Subject: Re: (fwd) "Will You Be a Terrorist?"
In-Reply-To: <9409172331.AA12848@ah.com>
Message-ID: <199409180143.SAA16949@infinity.c2.org>
MIME-Version: 1.0
Content-Type: text/plain
>
> I'd suggest that a much more productive avenue of approach would be to
> improve the aliasing facilities of a remailer provider to allow a
> pseudonym to look like a fully normal name.
it's done. omega.c2.org
http://www.c2.org/services/blindserver.html
http://www.c2.org/services/blindclient.html
>
> Ownership of root is not necessary for this. I know that Matt Ghio's
> mail delivery set up allows this. At his site there's this
> 'name+extra' syntax which delivers mail to 'name', but because of a
> special sendmail version 8 macro in the Received: field both the
> 'name' and the 'extra' can be recovered. The 'extra' is then an input
> into a remailer as a pseudonym.
>
> The aliasing has to happen somewhere. It can happen at the mailing
> list exploder or at the remailer. Since the mapping at the remailer
> is of much more general use, and since it allows one to leverage _all_
> forms of mail communication and not just mailing list, it seems like a
> much better place for that mapping to exist. Implementation inside a
> remailer is a duplication of function--almost always a bad thing.
>
> Eric
>
--
sameer Voice: 510-841-2014
Network Administrator Pager: 510-321-1014
Community ConneXion: The NEXUS-Berkeley Dialin: 510-549-1383
http://www.c2.org (or login as "guest") sameer@c2.org
Return to September 1994
Return to “tcmay@netcom.com (Timothy C. May)”