From: Eric Hughes <hughes@soda.berkeley.edu>
To: cypherpunks@toad.com
Message Hash: a81cd126963b7f8226f4ffc81434bdd2e2e4d7f782ed217e0bfec6a3e639d3a6
Message ID: <9306111523.AA11809@soda.berkeley.edu>
Reply To: N/A
UTC Datetime: 1993-06-11 15:26:58 UTC
Raw Date: Fri, 11 Jun 93 08:26:58 PDT
From: Eric Hughes <hughes@soda.berkeley.edu>
Date: Fri, 11 Jun 93 08:26:58 PDT
To: cypherpunks@toad.com
Subject: MAIL: logging that happens on soda
Message-ID: <9306111523.AA11809@soda.berkeley.edu>
MIME-Version: 1.0
Content-Type: text/plain
I was rooting around soda for some other reason and stumbled upon the
mail logs (!) for soda. I just sent myself some mail to generate a
sample entry. It's got complete traffic analysis data, complete with
to/from pairs, time of day, and message size.
Jun 11 08:13:35 soda sendmail[11298]: AA11298: message-id=<9306111513.AA11298@soda.berkeley.edu>
Jun 11 08:13:35 soda sendmail[11298]: AA11298: from=hughes, size=66, class=0, received from local
Jun 11 08:13:36 soda sendmail[11300]: AA11298: to=hughes, delay=00:00:01, stat=Sent
I would recommend that all remailer operators find out what kind of
mail logging, if any, takes place on their machines. If you need a
place to start looking, the mail log on soda was in the same directory
as the syslog messages.
I would also recommend that this information on mail logging by the
system be put in Karl's remailer list.
Eric
Return to June 1993
Return to “Peter Shipley <shipley@tfs.COM>”