Moved to Historic: RFC 4405 on SMTP Service Extension for Indicating the Responsible Submitter of an E-Mail Message
rfc-editor@rfc-editor.org Wed, 12 February 2020 19:03 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2BFF120AAC for <ietf-announce@ietfa.amsl.com>; Wed, 12 Feb 2020 11:03:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 9rTYcl60bcbV for <ietf-announce@ietfa.amsl.com>; Wed, 12 Feb 2020 11:03:23 -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 40CCB120AA5 for <ietf-announce@ietf.org>; Wed, 12 Feb 2020 11:03:23 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 177D3F40714; Wed, 12 Feb 2020 11:02:59 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: Moved to Historic: RFC 4405 on SMTP Service Extension for Indicating the Responsible Submitter of an E-Mail Message
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200212190259.177D3F40714@rfc-editor.org>
Date: Wed, 12 Feb 2020 11:02:59 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/qFVrgWkBan99NwkdlS06dg3AD3g>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Feb 2020 19:03:26 -0000
RFC 4405 has been reclassified as Historic.
RFC 4405
Title: SMTP Service Extension for Indicating
the Responsible Submitter of an E-Mail
Message
Author: E. Allman,
H. Katz
Status: Historic
Stream: IETF
Date: April 2006
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-katz-submitter-01.txt
URL: https://www.rfc-editor.org/info/rfc4405
DOI: 10.17487/RFC4405
This memo defines an extension to the Simple Mail Transfer Protocol
(SMTP) service that allows an SMTP client to specify the
responsible submitter of an e-mail message. The responsible
submitter is the e-mail address of the entity most recently
responsible for introducing a message into the transport stream.
This extension helps receiving e-mail servers efficiently determine
whether the SMTP client is authorized to transmit mail on behalf of
the responsible submitter's domain. 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