Sonneveld, Rolf wrote:
> On 04-10-10, *Hector Santos *<[email protected]> wrote:
>> I am wondering or under what scenario would a DSN (bounce) agent keep
>> the original signature in its bounce notification 5322 headers?
>>
>> It was a legitimate bounce for a non-delivery address.� But it kept
>> several headers from the original message in the DSN message headers:
>>
>> ��� DKIM-Signature:
>> ��� Organization:
>> ��� X-Mailer:
>>
>> What logic is there to this?
>
> RFC 3462, chapter 2.
>
> <quote>
>
> �� The Text/RFC822-Headers body part should contain all the RFC822
> <http://tools.ietf.org/html/rfc822>
> �� header lines from the message which caused the report.� The RFC822
> <http://tools.ietf.org/html/rfc822>
> �� headers include all lines prior to the blank line in the message.
> �� They include the MIME-Version and MIME Content-Headers.
> </quote>
>
> /rolf
The report does contain the original message. I speak of the actual
bounce message from the mailer-daemon contain a copy of above headers:
DKIM-Signature: d=santronics.com; .... <--- copy
Organization: Santronics Software, Inc. <--- copy
X-Mailer: wcMail v6.3.453.4 <--- copy
Date: Fri, 01 Oct 2010 09:18:26 -0400
From: [email protected]
To: [email protected]
Subject: DELIVERY FAILURE: .........
The rest of the DSN body message with the message/rfc822 report
attachment containing the original message was fine.
Am I still missing something?
--
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html
