1992-10-22 - BBS E-mail policy

Header Data

From: omega@spica.bu.edu (The Omega)
To: cypherpunks@toad.com
Message Hash: 8a24672636a42d5225524b26c5cc78e1b0ba1b62a4c1e1fe1825463951a6b9e0
Message ID: <9210221623.AA00440@spica.bu.edu>
Reply To: N/A
UTC Datetime: 1992-10-22 16:25:56 UTC
Raw Date: Thu, 22 Oct 92 09:25:56 PDT

Raw message

From: omega@spica.bu.edu (The Omega)
Date: Thu, 22 Oct 92 09:25:56 PDT
To: cypherpunks@toad.com
Subject: BBS E-mail policy
Message-ID: <9210221623.AA00440@spica.bu.edu>
MIME-Version: 1.0
Content-Type: text/plain


>>
One incentive would be for the BBS operators to phase in a policy that
they will accept no e-mail which is _not_ encrypted.  Comments?
<<
 
And how does your BBS software tell whether or not you've just sent
encrypted mail, plaintext mail or line-noise?
(in an encryption/decryption-at-user's-end scenario)
 
-- Omega@spica.bu.edu





Thread