[apps-discuss] RFC 7103 on Advice for Safe Handling of Malformed Messages

rfc-editor@rfc-editor.org Wed, 15 January 2014 05:17 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5F571AE2BE; Tue, 14 Jan 2014 21:17:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level:
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 iawSzjBZ-Zzf; Tue, 14 Jan 2014 21:17:45 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 7F3501AE2B2; Tue, 14 Jan 2014 21:17:45 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id D3C897FC175; Tue, 14 Jan 2014 21:17:33 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20140115051733.D3C897FC175@rfc-editor.org>
Date: Tue, 14 Jan 2014 21:17:33 -0800
Cc: drafts-update-ref@iana.org, apps-discuss@ietf.org, rfc-editor@rfc-editor.org
Subject: [apps-discuss] RFC 7103 on Advice for Safe Handling of Malformed Messages
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 05:17:47 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7103

        Title:      Advice for Safe Handling of 
                    Malformed Messages 
        Author:     M. Kucherawy, G. Shapiro,
                    N. Freed
        Status:     Informational
        Stream:     IETF
        Date:       January 2014
        Mailbox:    superuser@gmail.com, 
                    gshapiro@proofpoint.com, 
                    ned.freed@mrochek.com
        Pages:      24
        Characters: 48387
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-appsawg-malformed-mail-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7103.txt

Although Internet message formats have been precisely defined since
the 1970s, authoring and handling software often shows only mild
conformance to the specifications.  The malformed messages that
result are non-standard.  Nonetheless, decades of experience have
shown that using some tolerance in the handling of 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; it is to be used as
implementation guidance.

This document is a product of the Applications Area Working Group Working Group of the IETF.


INFORMATIONAL: This memo provides information 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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

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