The following errata report has been verified for RFC5965,
"An Extensible Format for Email Feedback Reports". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5965&eid=4421

--------------------------------------
Status: Verified
Type: Editorial

Reported by: Simon Leinen <[email protected]>
Date Reported: 2015-07-19
Verified by: Barry Leiba (IESG)

Section: B.2

Original Text
-------------
   --part1_13d.2e68ed54_boundary
   Content-Type: message/rfc822
   Content-Disposition: inline

   From: <[email protected]>
   Received: from mailserver.example.net (mailserver.example.net
        [192.0.2.1]) by example.com with ESMTP id M63d4137594e46;
        Thu, 08 Mar 2005 14:00:00 -0400

   To: <Undisclosed Recipients>
   Subject: Earn money


Corrected Text
--------------
   --part1_13d.2e68ed54_boundary
   Content-Type: message/rfc822
   Content-Disposition: inline

   From: <[email protected]>
   Received: from mailserver.example.net (mailserver.example.net
        [192.0.2.1]) by example.com with ESMTP id M63d4137594e46;
        Thu, 08 Mar 2005 14:00:00 -0400
   To: <Undisclosed Recipients>
   Subject: Earn money


Notes
-----
In the second example report, there is an empty line in the middle of the 
headers section of the quoted rfc822 message.  This seems wrong.

--------------------------------------
RFC5965 (draft-ietf-marf-base-06)
--------------------------------------
Title               : An Extensible Format for Email Feedback Reports
Publication Date    : August 2010
Author(s)           : Y. Shafranovich, J. Levine, M. Kucherawy
Category            : PROPOSED STANDARD
Source              : Messaging Abuse Reporting Format
Area                : Applications
Stream              : IETF
Verifying Party     : IESG

_______________________________________________
marf mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/marf

Reply via email to