292812 - unable to view signing and encryption information and the attachment when opening signed and encrypted eml file

Status: RESOLVED INCOMPLETE

(Thunderbird :: General, defect)

Description

[Max FUNG]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; en) Opera 8.0
Build Identifier: 20050503

When opening signed and encrypted eml file in Tbird, the signed and encrypted 
information are missing, the email only show the attachment file name but unable 
to extract the corresponding attachedment. However, before saving the email as 
eml in Tbird, the signed and encrypted information (key and lock icon) are 
available, and so is the attachment.

This problem does not occur in Netscape 4.x. The problem occur since the early 
development of mozilla (since 0.8 according to my memory)

Reproducible: Always

Steps to Reproduce:
1. Download a signed and encrypted email in Tbird, enter password for security 
device to decrpt the email
2. Save it as eml file
3. Open the eml file in Tbird under "open save message"
4. The email show.

Actual Results:  
Signed and encrypted information are missing. The attachment panel at the bottom 
is missing too. It only show the attachment filename at the bottom of the email 
but it doesn't allow to extract the attachment.

Expected Results:  
Signed and encrypted information show and so is the attachment. The behaviour and 
"LOOK" should be consistent when opening a signed and encrypted email in Tbird.

Note that the eml file can be opened in Netscape 4.7, the corresponding signed 
and encrypted information are all available, and so is the attachment.

Comment 1

[David :Bienvenu]

imap or local msg?

Comment 2

[Max FUNG]

(In reply to comment #1)
> imap or local msg?

Should be local msg because the message was downloaded through pop3. Pls 
correct me if I misunstand your question.

Comment 3

[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 4

[Max FUNG]

I try the latest version of tbird 1.5 beta and it work. I also try the same 
case in seamonkey (build id 2005091013) email portion to open the eml file and 
it work as well. However, if I try to open the eml file in the seamonkey 
browser, the same problem occured again.

Comment 5

[Max FUNG]

Further to my comment on 28.9.2005, I tried one of my old eml file (created by 
Netscape 4.7 messenger) using tbird 1.5 beta and seamonkey (build id 
2005091013) email client. The eml file is signed and encrypted with an 
attachment named "IO&AOBVE-SIO.zip". I try to right click and "open" it, it 
fail to lauch any application with no response on the screen. I try to right 
click and "save" it. When I press the save button in the popup dailog box, it 
return with an error "Unable to save the attachment. Pls check your file name 
and try again later". This problem doesn't occur in Netscape 4.7. Although I 
understand that special character like "&" is likely to cause the problem. 
However, we cannot order the sender which email client to use or which 
character you can't use in the filename of the email attachment.

Comment 6

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Reporter, does the issue still occur in the latest supported 2.0.0.x / trunk nightlies?

(1.5.0.x is now end-of-life and the latest supported 2.0.0.x is 2.0.0.16)

Comment 7

[Joshua Cranmer [:jcranmer]]

RESO INCO per lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.