Re: [ietf-822] "--" first in lines to indicate start of signature

Hector Santos <hsantos@isdg.net> Mon, 04 January 2016 19:54 UTC

Return-Path: <hsantos@isdg.net>
X-Original-To: ietf-822@ietfa.amsl.com
Delivered-To: ietf-822@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A0421A90CF for <ietf-822@ietfa.amsl.com>; Mon, 4 Jan 2016 11:54:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.079
X-Spam-Level:
X-Spam-Status: No, score=-101.079 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XEDlpzJ7VDzz for <ietf-822@ietfa.amsl.com>; Mon, 4 Jan 2016 11:54:10 -0800 (PST)
Received: from ftp.catinthebox.net (dkim.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 063991A90BF for <ietf-822@ietf.org>; Mon, 4 Jan 2016 11:54:09 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2421; t=1451937243; atps=ietf.org; atpsh=sha1; h=Received:Received:Received:Received:Message-ID:Date:From: Organization:To:Subject:List-ID; bh=yxa77pMVA8vPOKg3BvpWc9y4JYg=; b=r6w0/COvRLq4RkD3sTcl7wWik9GoaT1YMAzm6py6UVZgqh8W5Ko7qP6eXAAxST fGG8z9zGsYHHOu9yDG1MaeN/v8BOE78JJRo9Mqn2H4bVdDWiLEZeeCWWm6wJYWfn MTy8+ddfruDL5oOov/Q0fTyXPoaroYzwhB54NigJIFXkY=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.5) for ietf-822@ietf.org; Mon, 04 Jan 2016 14:54:03 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com; adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com; dmarc=pass policy=none author.d=isdg.net signer.d=beta.winserver.com (atps signer);
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.5) with ESMTP id 96436448.4.3876; Mon, 04 Jan 2016 14:54:02 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2421; t=1451937237; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=BcdRQXS EXSCXa8oPTns8uLIiWDufmOr1cs4NrruVZJg=; b=Z0R42riNwE3PMtOhIC/eGX5 7ZnPyEbWG2k7gH2dO9FjgI+xxDhgxzLxAmfPUlVZykPPTvqcC//A95iPwgnq8Ifm 3XyKrMLuv9JkOsG1ZNTYAVKC21hEKz+T/+IBv46/mqJs3wPDOMrkNVc2WdJt3un7 GRaVH7ThM8/zGVSVOBiY=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.5) for ietf-822@ietf.org; Mon, 04 Jan 2016 14:53:57 -0500
Received: from [192.168.1.2] ([99.121.4.202]) by beta.winserver.com (Wildcat! SMTP v7.0.454.5) with ESMTP id 96521125.9.2216; Mon, 04 Jan 2016 14:53:56 -0500
Message-ID: <568ACDD6.1060306@isdg.net>
Date: Mon, 04 Jan 2016 14:53:58 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.8.1
MIME-Version: 1.0
To: Jacob Palme <jpalme@dsv.su.se>, "Murray S. Kucherawy" <superuser@gmail.com>
References: <D6D98A12-74D5-45CB-86AD-3BDE6A931CFF@dsv.su.se> <87vb7bwv7n.fsf@hope.eyrie.org> <CAL0qLwYRTvLFwEZPNFbaNybGwj+e_g33kZQkFeLN4YTsZ=KSZg@mail.gmail.com> <86B20CD4-A452-4FA3-BBAF-D2BE99104BA9@dsv.su.se>
In-Reply-To: <86B20CD4-A452-4FA3-BBAF-D2BE99104BA9@dsv.su.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-822/3l1FPHHZU7IeqIHTOR9RbumBzJg>
Cc: ietf-822@ietf.org, Russ Allbery <eagle@eyrie.org>
Subject: Re: [ietf-822] "--" first in lines to indicate start of signature
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of issues related to Internet Message Format \[RFC 822, RFC 2822, RFC 5322\]" <ietf-822.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-822/>
List-Post: <mailto:ietf-822@ietf.org>
List-Help: <mailto:ietf-822-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jan 2016 19:54:12 -0000

On 1/4/2016 8:39 AM, Jacob Palme wrote:
>
> On 3 jan 2016, at 00.05, Murray S. Kucherawy wrote:
>
>> What other uses of "--" on a line by itself are there?  The only thing I can think of is ASCII art.
>
> I have used "--" to separate sections in a longer plain text document. I
>have learned to not use it in that way in mail messages, and use "=="
>instead of "--".

That will still get you in trouble. Overall, when you begin to depend 
on such ideas, you need ways to escape it as well.

> But it is a simple mistake to make if you are not aware of its special
> meaning in mail messages.

IMO, there is no "special meaning."  The idea of a 'Signature" may be 
traditionally at the bottom, but there is no real hard core rule you 
(a mail processor) can rely on.

The MUA software does not use normally this.  It is the USER with his 
optional signature fields and thats just added straight to the bottom. 
   The same software COULD check if the same block was already added 
but I don't believe it will add "-- " for you, well, at least my TBird 
doesn't.   I noticed that TBIRD can not tell the difference between 
the signature fields when you change your "From: " field in the MUA, 
so you have to clean that up yourself.

> Which probably many mail users are, everyone is not an expert on mail protocols,
>as we who subscribe to this mailinglist are.

Right, outside the tech forums, you generally don't see this in the 
user market unless the MUA has direct support for this where it works 
off a "standard delimiter" of some sort.

We had such logics in older Fidonet/QWK readers. When we began to use 
RFC based formats, it felt like we began to deprecate the idea. It 
wasn't a big thing anymore because the body text can have anything. 
The then "new" Internet Format brought on a new Democracy of mail 
where it can have anything.  I was more concerned with transport 
related network control lines.   The signature is not a network or 
mail control Line.  Offhand, I would not classify it as such.

I guess the point is unlike MIME block where we have distinct line 
delimiting logic to separate blocks of text lines with border lines, 
etc,  we don't have such a thing for signatures.   What would be the 
rules? Is there a MIME type for signatures?  Are there limits (length 
of line, # of lines) in what junk people can add?  Look at the extra 
stuff a few of the IETF guys add.

***
HLS