🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.folklore.computers
Article #124597

Re: Why do we use '-- ' as a .sig separator ?

#124597
From: ab... Joe Thompson
Date: Fri, 30 Jan 1998 00:00
24 lines
1517 bytes
In article <6anoq6$8a3$1...@news3.tufts.edu>, kis...@allegro.cs.tufts.edu
(Kirk Is) wrote:

> Is the "official" convention that it's dash-dash-space, not 
> just dash-dash?

Actually convention is dash, dash, space, newline, or in ASCII:

45 45 32 13 (decimal)
2D 2D 20 0D (hex)

So anytime you see 2D2D200D followed by text followed by an EOF, you can
treat everything in between as a sig (if it's an RFC 822 message,
presumably).

It may (or may not) be worth noting that 2, D and 0 are the only characters
needed to express the sig header in hex.  Are they particularly significant
for some reason? -- Joe
-- 
      Joe Thompson | By sending commercial | Tech support is a fine 
Charlottesville VA | e-mail, you agree to  | art which once mastered,
 Expert PC service | pay US$1000.00/item.  | ensures loss of sanity.
                  http://kensey.home.mindspring.com/
Technical Details
Message-ID: <abuse-ya02408000R3001982219350001@news.mindspring.com>
Path: mbox-mo1.pugleaf.net!unknown!not-for-mail
References: <B0F2C431966822BA4C@hearsay.demon.co.uk> <hnsngr-ya023180002601981909440001@news.sirius.com> <6ajn4i$sn7@sifon.cc.mcgill.ca> <34ceca7b.0@news.wizvax.net> <6anoq6$8a3$1@news3.tufts.edu>

Show Full Headers
Complete Article Headers
From: ab...@orion-com.com (Joe Thompson)
Subject: Re: Why do we use '-- ' as a .sig separator ?
Date: 1998/01/30
Message-ID: <abuse-ya02408000R3001982219350001@news.mindspring.com>
X-Deja-AN: 320748516
References: <B0F2C431966822BA4C@hearsay.demon.co.uk> <hnsngr-ya023180002601981909440001@news.sirius.com> <6ajn4i$sn7@sifon.cc.mcgill.ca> <34ceca7b.0@news.wizvax.net> <6anoq6$8a3$1@news3.tufts.edu>
X-Server-Date: 31 Jan 1998 03:19:20 GMT
Mime-Version: 1.0
Organization: Orion Computer Consulting
Newsgroups: alt.folklore.computers
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit