[rfc-dist] Moved to Historic: RFC 4407 on Purported Responsible Address in E-Mail Messages

rfc-editor@rfc-editor.org Wed, 12 February 2020 19:04 UTC

Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28320120BCA for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 12 Feb 2020 11:04:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=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 h6zarZMR6DUy for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 12 Feb 2020 11:04:09 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2103A120B4E for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 12 Feb 2020 11:04:04 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 07FCAF4073A; Wed, 12 Feb 2020 11:03:14 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 76355F40739; Wed, 12 Feb 2020 11:03:13 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200212190313.76355F40739@rfc-editor.org>
Date: Wed, 12 Feb 2020 11:03:13 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?Moved_to_Historic=3A_RFC_4407_on_Purported_?= =?utf-8?q?Responsible_Address_in_E-Mail_Messages?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

RFC 4407 has been reclassified as Historic.
        
        RFC 4407

        Title:      Purported Responsible Address in E-Mail 
                    Messages 
        Author:     J. Lyon
        Status:     Historic
        Stream:     IETF
        Date:       April 2006
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-lyon-senderid-pra-01.txt

        URL:        https://www.rfc-editor.org/info/rfc4407

        DOI:        10.17487/RFC4407

This document defines an algorithm by which, given an e-mail message,
one can extract the identity of the party that appears to have most
proximately caused that message to be delivered.  This identity is
called the Purported Responsible Address (PRA).This memo defines an Experimental Protocol for the Internet community.  


HISTORIC: This memo defines a Historic Document for the Internet
community.  It does not specify an Internet standard of any kind.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org