[Ietf-message-headers] Re: For review: Apparently-To

Frank Ellermann <nobody@xyzzy.claranet.de> Mon, 02 April 2007 18:22 UTC

Return-path: <ietf-message-headers-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HYRAg-0006YM-47; Mon, 02 Apr 2007 14:22:26 -0400
Received: from ietf-message-headers by megatron.ietf.org with local (Exim 4.43) id 1HYRAf-0006YH-Dp for ietf-message-headers-confirm+ok@megatron.ietf.org; Mon, 02 Apr 2007 14:22:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HYRAf-0006Y9-4A for ietf-message-headers@lists.ietf.org; Mon, 02 Apr 2007 14:22:25 -0400
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HYRAd-00056V-Q9 for ietf-message-headers@lists.ietf.org; Mon, 02 Apr 2007 14:22:25 -0400
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HYRAc-00076g-Fs for ietf-message-headers@lists.ietf.org; Mon, 02 Apr 2007 20:22:22 +0200
Received: from d247224.dialin.hansenet.de ([80.171.247.224]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf-message-headers@lists.ietf.org>; Mon, 02 Apr 2007 20:22:22 +0200
Received: from nobody by d247224.dialin.hansenet.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf-message-headers@lists.ietf.org>; Mon, 02 Apr 2007 20:22:22 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: ietf-message-headers@lists.ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Mon, 02 Apr 2007 20:21:09 +0200
Organization: <URL:http://purl.net/xyzzy>
Lines: 23
Message-ID: <46114995.3BAA@xyzzy.claranet.de>
References: <4605CED1.70A@xyzzy.claranet.de> <460F8528.36E2@xyzzy.claranet.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: d247224.dialin.hansenet.de
X-Mailer: Mozilla 3.0 (OS/2; U)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc:
Subject: [Ietf-message-headers] Re: For review: Apparently-To
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
Errors-To: ietf-message-headers-bounces@ietf.org

Another update, credits to Robert A. Rosenberg:  It only 
affected messages with no To:, Cc:, or Bcc: at all, see
<http://permalink.gmane.org/gmane.ietf.smtp/5486>

~~~ cut ~~~
PROVISIONAL MESSAGE HEADER FIELD REGISTRATION TEMPLATE:

Header field name:         Apparently-To
Applicable protocol:       mail
Status:                    deprecated
Author/Change controller:  IETF
Specification document(s): RFC 2076, section 3.4
Related information:
        This header field was never formally standardized.  It
        was added by a popular mailer in absence of recipient
        header fields (To, Cc, Bcc) listing all envelope RCPT TO
        addresses, thereby disclosing the addresses of blind
        carbon copies to all recipients.

        Mentioned in RFC 1211 appendix F.18.a and RFC 2076 3.4,
        discussed in RFC 2821 7.2 (summary: "SHOULD NOT be used"),
        this was later copied verbatim into RFC 3552 6.1.1.2.




_______________________________________________
Ietf-message-headers mailing list
Ietf-message-headers@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-message-headers