[6443] in cryptography@c2.net mail archive
Re: Unrestricted crypto software web posting
daemon@ATHENA.MIT.EDU (Shabbir J. Safdar)
Thu Jan 20 16:21:44 2000
Mime-Version: 1.0
Message-Id: <v04220810b4ad24d9135e@[209.118.97.67]>
In-Reply-To: <200001202037.PAA17152@fbi.crypto.com>
Date: Thu, 20 Jan 2000 15:48:57 -0500
To: Matt Blaze <mab@crypto.com>, "Salz, Rich" <SalzR@CertCo.com>
From: "Shabbir J. Safdar" <shabbir@mindshare.net>
Cc: "'Phil Karn'" <karn@qualcomm.com>,
"'cryptography@c2.net'" <cryptography@c2.net>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Amazing. If you could get this address publicized far wider than the
original BXA address, it would save the folks at EPIC countless hours
of FOIA filings to find out what's been sent to crypt@bxa.doc.gov. :-)
-Shabbir
At 3:37 PM -0500 1/20/00, Matt Blaze wrote:
>Consider it done; the alias:
>
> exports@crypto.com
>
>now appends to http://www.crypto.com/exports/mail.txt, and also mails to
>crypt@bxa.doc.gov (currently empty, but that will change as people use it).
>
>-matt
>
>
> > Wouldn't it be great if "we" could get put on the "crypt@bxa.doc.gov"
> > mailing list? Failing that, perhaps eff.org, crypto.com, or similar
> > could set up a "export-notice" mail alias that forward to the BXA,
> > but also archives them for folks (e.g., JYA :) to keep.
> >
> > /R$
> >
> > PS: Just for the heck of it, I tried something and got back:
> > The message that you sent was undeliverable to the following:
> > majordomo@bxa.doc.gov (user not found)
> > listserv@bxa.doc.gov (user not found)
> >
> > Possibly truncated original message follows:
> > ...elided
> >
