errata logo graphic

Found 2 records.

Status: Verified (1)

RFC5965, "An Extensible Format for Email Feedback Reports", August 2010

Source of RFC: marf (app)

Errata ID: 4421

Status: Verified
Type: Editorial

Reported By: Simon Leinen
Date Reported: 2015-07-19
Verifier Name: Barry Leiba
Date Verified: 2015-07-19

Section B.2 says:

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

   From: <somespammer@example.net>
   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

It should say:

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

   From: <somespammer@example.net>
   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.


Status: Held for Document Update (1)

RFC5965, "An Extensible Format for Email Feedback Reports", August 2010

Source of RFC: marf (app)

Errata ID: 3120

Status: Held for Document Update
Type: Technical

Reported By: John Levine
Date Reported: 2012-02-14
Held for Document Update by: Pete Resnick

Section 2.d. says:

This part MUST be included (contrary to [REPORT])

It should say:

This part MUST be included if the entity creating the report has 
received the message.

Notes:

Reports can be created from info collected in SMTP transactions that don't accept a message, a scenario we didn't consider when we wrote this section.


Report New Errata