Closed
Bug 336581
Opened 20 years ago
Closed 18 years ago
MDN contains Disposition-Notification-To: header (RFC3798 non conformance)
Categories
(MailNews Core :: Backend, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: adb, Unassigned)
References
(Blocks 1 open bug)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.0.2) Gecko/20060308 Firefox/1.5.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.0.2) Gecko/20060308 Firefox/1.5.0.2
When TB generates an MDN it adds the Disposition-Notification-To: header to the MDN. This breaks RFC3798
MDN headers were:
----------------------------------------------------------------------------
Return-Path: <me@myhost.com>
Received: from [127.0.0.1] ([127.0.0.1]) by aconcagua with ESMTP
id m54aa9p1; 4 May 2006 10:10:00 +0300
Date: Thu, 04 May 2006 10:10:41 +0300
From: me@myhost.com
Message-ID: <4459A8F1.5070808@myhost.com>
Subject: Return Receipt (displayed) - RE: 060327-000000 TOALARM
To: "Original Sender" <original.sender@theirhost.com>
References: <4812B0D72240C04E8A8F26F04A4DD2A2CD1B0A@host.com>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=disposition-notification;
boundary="------------mdn040107020400020609030607"
Disposition-Notification-To: me@myhost.com
----------------------------------------------------------------------------
Section "2.1 The Disposition-Notification-To Header" of the spec says about the DNT header:
An MDN MUST NOT itself have a Disposition-Notification-To header. An
MDN MUST NOT be generated in response to an MDN.
Reproducible: Always
Steps to Reproduce:
1. Respond OK to generate a receipt when receiving a message requesting receipt
2. MDN Contains DNT header
3.
Actual Results:
MDN Contains DNT header
Expected Results:
MDN should not contain DNT header
Comment 1•19 years ago
|
||
Moving this to Core:MailNews Backend, like bug 270781.
(Note there is a Return Receipts component, but that's only under the Mozilla suite and the MDN code is shared between suite and TB.)
I can't reproduce this using TB 1.5 or TB 2b1-1111, Win2K.
Component: General → MailNews: Backend
Product: Thunderbird → Core
Version: unspecified → Trunk
Updated•19 years ago
|
Assignee: mscott → nobody
QA Contact: general → backend
Comment 2•18 years ago
|
||
->WFM on Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b3pre) Gecko/2007123104 Thunderbird/3.0a1pre ID:2007123104
Possibly this was a misconception. TB cites the original headers, and of course in those Disposition-Notification-To exists, but it's in the MDN body and totally ok.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Tried to reproduce with 2.0.0.9 and it must have been fixed in v2 at some point.
Resolution: WORKSFORME → FIXED
Updated•18 years ago
|
Resolution: FIXED → WORKSFORME
Comment 4•18 years ago
|
||
This isn't "FIXED" unless you can point to the exact bug that fixed it. :)
--> WFM
Resolution: FIXED → WORKSFORME
| Assignee | ||
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•