472085 - not all mime parts of listserv formated digest are displayed

Status: RESOLVED DUPLICATE of bug 276991

(MailNews Core :: MIME, defect)

Description

[Wayne Mery (:wsmwk)]

Attachment: digests

David, this the case I emailed on 12/23.

listserv digest (http://www.lsoft.com/) doesn't display fully in thunderbird 2 and 3, but does in Mac mailapp and my ISP's roundcube driven webmail
 
click link "Results from 2008 ResNet Survey Now Available (12/22)" fails because thunderbird isn't displaying the referenced mail below the point of "Powered by LISTSERV(R) <http://www.lsoft.com/LISTSERV-powered.html> Browse the 
SIGUCCS online archives."

i.e. starting at
  ------------------------------
  Content-ID: <[e-mail]>
  Content-Type: message/rfc822

message header has
 Content-Type: multipart/related; type="text/html";
              boundary="----------------------------"

Comment 1

[Karsten Düsterloh]

The message itself shows correctly here (current Linux TB/SM trunk, SM 1.1.14); just be aware that it's multipart/related, not multipart/alternativ, as you probably did expect?

I see a table of content, linking to the single messages, and each message in turn has a (CID:) link to its content. Clicking this link will show the message in SM, but TB requests to specify a handler for an "ASC" file - which is strange indeed, but not what you filed this bug for?

Probably (slightly) related: bug 61815.

OTOH, the attached mbox does neither contain the 12/22 link nor the Content-ID <[e-mail]>, so maybe you attached the wrong file?

Comment 2

[Wayne Mery (:wsmwk)]

Attachment: digest screen shot (TB on top)

(In reply to comment #1)
> The message itself shows correctly here (current Linux TB/SM trunk, SM 1.1.14);
> just be aware that it's multipart/related, not multipart/alternativ, as you
> probably did expect?

I have no idea.

> I see a table of content, linking to the single messages, and each message in
> turn has a (CID:) link to its content. Clicking this link will show the message
> in SM, but TB requests to specify a handler for an "ASC" file - which is
> strange indeed, but not what you filed this bug for?
> 
> Probably (slightly) related: bug 61815.
> 
> OTOH, the attached mbox does neither contain the 12/22 link nor the Content-ID
> <[e-mail]>, so maybe you attached the wrong file?

Yeah, wrong file.  Sticking with that file (which fails for me in SM 1.1.4) I see on my other ISP something similar to the bottom of the screen shot.  Versus Thunderbird which doesn't display the full message.

Are there TB settings which might cause incorrect display?

Comment 3

[Karsten Düsterloh]

(In reply to comment #2)
> I see on my other ISP something similar to the bottom of the screen shot.
> Versus Thunderbird which doesn't display the full message.

Actually, I think that your webmail does it wrong.
The attached mail in question has this MIME structure:

- Content-Type: multipart/related; type="text/html"
  - Part 1: text/html as shown by TB, referencing <[e-mail]> 
            and <cid:[e-mail]>
  - Part 2: message/rfc822 with Content-ID: <[e-mail]>, 
    which itself is multipart/alternative:
    - text/plain variant of the message
    - text/html variant of the message
  - Part 3: message/rfc822 with Content-ID: <[e-mail]>, 
    which itself is multipart/alternative:
    - text/plain variant of the message
    - text/html variant of the message

Parts 2 and 3 not attachments, but integral parts of part 1, see eg. <http://en.wikipedia.org/wiki/MIME#Related> about the use of multipart/related.

The only bug-worth issue I see for TB here is that TB doesn't recognize the sub parts as message/rfc822 but just "ASC files".

Comment 4

[Karsten Düsterloh]

Maybe you want bug 240743?

Comment 5

[Wayne Mery (:wsmwk)]

(In reply to comment #4)
> Maybe you want bug 240743?

unsure - it's testcase doesn't lend itself to testing since it contains a virus. You may be in a better position to judge - dupe?

Comment 7

[Peter Reynolds]

This is still a problem - duplicate it may be but who is going to try and fix a bug on behalf of a virus, whereas displaying Listserv digests correctly is something that *ought* to be done.   

I am currently set up to receive a Listserv 16.0 Digest (HTML format).  What I get is the list of messages, each clickable, and nothing else *visible*.  If I click on an individual message it opens in a text editor.

What I would like to happen is what happens with Yahoo Groups.  The list of messages is at the top, it's clickable, and when you click it scrolls down to the appropriate place in an HTML-formatted digest.  Clicking "View Message Source" makes it plain that there *is* a scrollable digest.