235482 - Need to process embedded mime parts (according content-type) like main message

Status: RESOLVED EXPIRED

(MailNews Core :: Backend, defect)

Description

[Patrick Brunschwig]

User-Agent:       
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113

Currently, Mozilla only handles content-types like application/pkcs7-mime or
application/pgp-signed on the message content-type. If e.g. an S/MIME or
PGP/MIME message is in an embedded MIME part (like newer versions of mailman do
it), Mozilla doesn't recognize the content-type correctly, so that the
corresponding content-type handler is not called. The same holds for
content-types embedded in encrypted messages (like RFC 3156, section 6.1 propose
it).

For correct mail processing, every mime part with a content-type that has some
specific handler, the whole part (including the headers) should be passed to the
content-type handler for further processing. The same should happen with the
resulting data from a content-type handler (e.g. when it decrypts an S/MIME or
PGP/MIME message)



Reproducible: Always
Steps to Reproduce:

Comment 1

[Mike Cowperthwaite]

Patrick Brunschwig, can you provide a sample message showing exactly the header 
configuration you're describing with this bug?  Save the sample as a .EML file 
and attach to this bug using the Create New Attachment link above.

There are several bugs about S/MIME part handling which turn out to be malformed 
messages rather than a failure to process a correct message.

Comment 2

[Patrick Brunschwig]

Attachment: Attachment with embedded PGP/MIME signed message

Here we are. This is a valid PGP/MIME signed message (it verifies OK in
Enigmail). I implemented a workaround to detect such a message in Enigmail, but
my workaround fails if a message contains more than one such embedded mime
parts, furthermore I think this needs to be properly handled by the backend.

Comment 3

[Mike Cowperthwaite]

I tried looking at the sample message, and I also tried modifying the sample to 
remove the mailman parts.  I'm curious about what you expect to see, vs what you 
are seeing.  Working with a TB trunk build, without Enigmail.

With the message *with* the Mailman part, I see:
  message body
  inline 'mailman' footer (whether or not Display Attachments Inline is set)
  attachment panel containing 'signature.asc' and 'Part1.2'

With the message stripped of the Mailman part, I see:
  message body
  no attachment panel

I don't see a 'message signed' icon for either, which is arguably a problem;
and I would say that if 'signature.asc' doesn't appear in an attachment panel 
for the pre-mailman version of the message, it shouldn't appear for the post-
mailman version either.

Comment 4

[Patrick Brunschwig]

It's not about what I want to see, but about how it should be done.

I have implemented a workaround (i.e. a hack) in Enigmail to find out if a
subpart is PGP/MIME (based on the type of the attachment), and then I decode
that particular MIME part. But it's not clean and error prone, e.g. it won't
work for PGP/MIME encrypted subparts.

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.