Last Call: <draft-ietf-appsawg-malformed-mail-09.txt> (Advice for Safe Handling of Malformed Messages) to Informational RFC

The IESG <> Tue, 15 October 2013 22:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 26CAB21F9DB0; Tue, 15 Oct 2013 15:45:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.43
X-Spam-Status: No, score=-102.43 tagged_above=-999 required=5 tests=[AWL=0.170, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 9SM3Sc59DfA3; Tue, 15 Oct 2013 15:45:30 -0700 (PDT)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 7F61821F8263; Tue, 15 Oct 2013 15:45:24 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Last Call: <draft-ietf-appsawg-malformed-mail-09.txt> (Advice for Safe Handling of Malformed Messages) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Tue, 15 Oct 2013 15:45:23 -0700
X-Mailman-Version: 2.1.12
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 15 Oct 2013 22:45:31 -0000

The IESG has received a request from the Applications Area Working Group
WG (appsawg) to consider the following document:
- 'Advice for Safe Handling of Malformed Messages'
  <draft-ietf-appsawg-malformed-mail-09.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the mailing lists by 2013-10-29. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   Although Internet mail formats have been precisely defined since the
   1970s, authoring and handling software often show only mild
   conformance to the specifications.  The malformed messages that
   result are non-standard.  Nonetheless, decades of experience has
   shown that handling with some tolerance the malformations that result
   is often an acceptable approach, and is better than rejecting the
   messages outright as nonconformant.  This document includes a
   collection of the best advice available regarding a variety of common
   malformed mail situations, to be used as implementation guidance.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.