Nicer display and translation of "message/delivery-status" attachments

NEW
Unassigned

Status

MailNews Core
MIME
--
enhancement
13 years ago
a year ago

People

(Reporter: Rob Janssen, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b4) Gecko/20050913 SeaMonkey/1.0a
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b4) Gecko/20050913 SeaMonkey/1.0a

When a mail delivery problem report is received, it often contains an attachment with mimetype "message/delivery-status" which holds some result codes for the delivery attempt.
This attachment is only displayed literally as text.  In the attachment list it is usually showing up as "Part 1.2", which the OS does not know how to handle.

I think it would be more userfriendly to show this attachment in an aestecically pleasing way, both when showing it inline and when the attachment is doubleclicked to view what is in there.
The display should attempt to convert the technical reason codes to messages a typical user would understand, and that are translated into the local language.


Reproducible: Always

Steps to Reproduce:
(Reporter)

Comment 1

11 years ago
Those attachments conform to RFC 1794.
Example:

Content-Type: message/delivery-status

Reporting-MTA: dns;receiver.example.com
Received-From-MTA: dns;sender.example.com
Arrival-Date: Fri, 29 Jun 2007 10:09:43 +0200

Final-Recipient: rfc822;user@receiver.example.com
Action: failed
Status: 5.2.3
X-Display-Name: Joe User


This report means: the message you sent was larger than the maximum for this user.
That can be derived from the "Status: 5.2.3" which is defined in RFC 1893.

Of course this is all way beyond today's typical user.  We really need to decode those attachments because mail servers like Exchange no longer provide a textual reason for non-delivery in their delivery-status messages.
Severity: enhancement → normal

Comment 2

11 years ago
(In reply to comment #1)
> Those attachments conform to RFC 1794.

This is almost certainly the wrong RFC. Status codes are RFC 3463 (obsoleting RFC 1893), delivery status notifications RFC 3464.

As one of the main benefits of those concepts seems to be independence of one specific human language, it would be the receiver MUA's task to display the information in the preferred language of its user. Displaying only the codes is very likely not the intention of those RFCs.
(Reporter)

Comment 3

11 years ago
(In reply to comment #2)
> (In reply to comment #1)
> > Those attachments conform to RFC 1794.
> 
> This is almost certainly the wrong RFC. Status codes are RFC 3463 (obsoleting
> RFC 1893), delivery status notifications RFC 3464.

You are right, it was a typo and should have been 1894 instead of 1794.  Anyway, when those newer RFCs are available they should be referenced instead.
No activity since July 2007. Is this still happening with current builds?

Comment 5

10 years ago
(In reply to comment #4)
> No activity since July 2007. Is this still happening with current builds?

Yes, still an issue. Got a delivery status recently in TB 2.0.0.12, and it still rendered as the same text with its numeric code.
(In reply to comment #5)
> (In reply to comment #4)
> > No activity since July 2007. Is this still happening with current builds?
> 
> Yes, still an issue. Got a delivery status recently in TB 2.0.0.12, and it
> still rendered as the same text with its numeric code.
> 

OK. Could you paste the user-agent string from that mailer version? For Thunderbird it might be something looking like "Thunderbird 2.0.0.12 (Windows; 20080213)" -- you get it from the "Help -> About Thunderbird" menu. For SeaMonkey it would be different, like the "User-Agent" at the top of this bug.
Assignee: mail → nobody
Status: UNCONFIRMED → NEW
Component: MailNews: Main Mail Window → MailNews: MIME
Ever confirmed: true
Product: Mozilla Application Suite → Core
QA Contact: mime
Oh, and BTW -- does it happen also on Thunderbird 3 / SeaMonkey 2.0a1pre ? (If it isn't, the "Version" field should be changed from "Trunk" to "1.8 Branch".
Version: unspecified → Trunk

Comment 8

10 years ago
Created attachment 314524 [details]
Stripped-down test case

(In reply to comment #6)
> OK. Could you paste the user-agent string from that mailer version?

This is version 2.0.0.12 (20080228) on Gentoo Linux, so it might contain slight patches.

(In reply to comment #7)
> Oh, and BTW -- does it happen also on Thunderbird 3 / SeaMonkey 2.0a1pre ? (If
> it isn't, the "Version" field should be changed from "Trunk" to "1.8 Branch".

I don't have either of these checked out, and don't have the time to compile TB3 any time soon.

Instead I've stripped my most recent delivery status report, mainly to remove all personal information, but also to make it simpler to debug. Someone with a current build, probably live from the repository, could use this testcase to try this out in recent development builds.
(In reply to comment #8)
[...]
> (In reply to comment #6)
[...]
> (In reply to comment #7)
> > Oh, and BTW -- does it happen also on Thunderbird 3 / SeaMonkey 2.0a1pre ? (If
> > it isn't, the "Version" field should be changed from "Trunk" to "1.8 Branch".
> 
> I don't have either of these checked out, and don't have the time to compile
> TB3 any time soon.
[...]

You don't have to compile it: you can grab a .tar.bz2 from http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-trunk/ or http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/ ; but if you aren't really willing to test a trunk build, which, after all, "is the bleeding edge of software development and may contain many bugs", I can understand your reticence.
(Reporter)

Comment 10

10 years ago
This is an enhancement request that is not going to go away "by accident" just because the major version number was bumped.  It requires quite some work to build the tables of status codes to text messages and translate them to the different local languages.  Apparently nobody has taken up the work.
So, I'd expect the addition of this feature to a new version to be mentioned and noticed in release notes.
(Assignee)

Updated

10 years ago
Product: Core → MailNews Core

Comment 11

a year ago
Confirmed, changing to enhancement.

Thunderbird 52.0.1 (32-bit)
Windows 7 64-bit
Severity: normal → enhancement
You need to log in before you can comment on or make changes to this bug.