1993-01-11 - .Sig suppression

Header Data

From: Hal <74076.1041@CompuServe.COM>
To: CYPHERPUNKS <CYPHERPUNKS@TOAD.COM>
Message Hash: bd075ece846c4e4025f0056fe2b81fc7ae03a85ac8c42b430c10b753993f581b
Message ID: <93011116483374076.1041_DHJ37-2@CompuServe.COM>
Reply To: _N/A

UTC Datetime: 1993-01-11 17:03:59 UTC
Raw Date: Mon, 11 Jan 93 09:03:59 PST

Raw message

From: Hal <74076.1041@CompuServe.COM>
Date: Mon, 11 Jan 93 09:03:59 PST
To: CYPHERPUNKS <CYPHERPUNKS@TOAD.COM>
Subject: .Sig suppression
Message-ID: <930111164833_74076.1041_DHJ37-2@CompuServe.COM>
MIME-Version: 1.0
Content-Type: text/plain


-----BEGIN PGP SIGNED MESSAGE-----

Chael> I'm
Chael> sure there are a couple, but I agree with your point that most BBS's on
Chael> any mail network append an identifying "tagline" or signature.  As a
Chael> matter of fact, in many nets it is a requirement that your system append
Chael> a tagline to all messages.  Incidentally, it is preceded often by "--"
Chael> on a line by itself.

I'd like to hear more about systems which do this.  What is the rationale
for adding the system name at the end?  Do these networks not use
Internet-style "From:" headers, so these automatic system-wide .sigs are
used for the same effect?

I guess there must be gateways between these bbs's and the internet,
for this issue to arise.  It's too bad that these gateways don't convert
the .sig info into a more conventional RFC-822 style Internet header.

Hal Finney

-----BEGIN PGP SIGNATURE-----
Version: 2.1

iQCVAgUBK1F586gTA69YIUw3AQFNogP9FU2W3wrHTnfrZeKtrMOq4Zz5aTUN7+vv
04iMOdV975fCzqdmgR7O758qamewguYV8XHmPVloLSMwgnmbzBNs8zRZkVAwTKnB
rpQqeahXPNeC1PVu/ezoiBvc26ujcN2Ga9OuGUWu9RFRvjwQ0rl51mTjHED1fJi+
7I/TV4kT4Kk=
=WeLq
-----END PGP SIGNATURE-----


Distribution:
  CYPHERPUNKS >INTERNET:CYPHERPUNKS@TOAD.COM






Thread