Gnus development mailing list
 help / color / mirror / Atom feed
From: Leonard Blanks <ltb@haruspex.demon.co.uk>
Subject: Re: "-- " for signatures?
Date: 27 Nov 1998 22:47:31 +0000	[thread overview]
Message-ID: <m24srkkb24.fsf@haruspex.demon.co.uk> (raw)
In-Reply-To: Russ Allbery's message of "27 Nov 1998 12:14:08 -0800"

>>>>> "RA" == Russ Allbery <rra@stanford.edu> writes:

 RA> Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
 >> "KG" == Kai Grossjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:

 KG> Where was it again where it is specified that signatures should be
 KG> separated from the rest of the message by a "-- " line?

 >> One of the Internet RFCs specifies it... but I cannot for the life of me
 >> remember which one.

 RA> Are you sure it's an RFC?  I thought the only "official" reference was in
 RA> Son-of-1036.

Yes.  In Section 4.3.2:

          Early  difficulties in inferring return addresses from arti-
          cle headers led to "signatures": short closing texts,  auto-
          matically  added  to  the end of articles by posting agents,
          identifying the poster and giving his network addresses etc.
          If  a  poster or posting agent does append a signature to an
          article, the signature SHOULD be preceded with  a  delimiter
          line  containing  (only)  two hyphens (ASCII 45) followed by
          one blank (ASCII  32).   Posting  agents  SHOULD  limit  the
          length  of  signatures,  since  verbose  excess bordering on
          abuse is common if no restraint is imposed;  4  lines  is  a
          common limit.

-- 
Len

We are all just prisoners here of our own MAKEDEV.



  parent reply	other threads:[~1998-11-27 22:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-27 19:05 Kai.Grossjohann
     [not found] ` <x7emqprll2.fsf@peorth.gweep.net>
1998-11-27 20:14   ` Russ Allbery
1998-11-27 21:33     ` Christian Kurz
1998-11-27 22:47     ` Leonard Blanks [this message]
1998-11-27 22:52     ` Kai.Grossjohann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m24srkkb24.fsf@haruspex.demon.co.uk \
    --to=ltb@haruspex.demon.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).