Closed Bug 48374 Opened 24 years ago Closed 1 years ago

PGP Attachment not shown when reading mail

Categories

(MailNews Core :: MIME, defect)

Product:
MailNews Core
Component:
MIME
Platform:
x86
Windows 2000
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: bugzilla, Unassigned)

References

(
URL
)

Details

Attachments

(3 files)

Mail that generates no attachment in Mozilla!
(deleted), patch
Details | Diff | Splinter Review
screenshot showing mail in build 20010213
(deleted), image/gif
Details
Email msg containing an attachment that does not show up in Thunderbird
(deleted), text/plain
Details
Attached is a mail that dont give me any attachment in Mozilla, but do in all other mail programs. The headers has this: Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="Hf61M2y+wYpnELGG" perhaps this is causing Mozilla some problems...?
another recent attachment bug is bug 48224
*** Bug 48408 has been marked as a duplicate of this bug. ***
*** Bug 48459 has been marked as a duplicate of this bug. ***
Can you describe this problem a little more, please?
QA Contact: lchiang → pmock
If you take the attached mail and send it to yourself or go to the URL, there isn't any attachment paperclip icon shown to the right in the header of the mailpane. The paperclip icon dont appear doing a resize. I'm using Mozilla on a IMAP client and both Netscape 4.74 and Outlook Express shows the attachment icon.
Summary: Attachment not shown → Attachment not shown when reading mail
Will try to look at if I have time. - rhp
Status: NEW → ASSIGNED
Target Milestone: --- → M20
Target Milestone: M20 → Future
Rich, I can reproduce this problem on all platforms using the commercial builds: win32 commercial seamonkey build 2000-091309-m18 installed on P500 Win98 linux commercial seamonkey build 2000-091308-m18 installed on P200 RedHat 6.2 macos commercial seamonkey build 2000-091308-m18 installed on G3/400 OS 9.04 It appears that seamonkey has trouble with the Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="Hf61M2y+wYpnELGG"
As Henrik said, Communicator 4.74 and Outlook Express 5.5 display the attachment icon.
reassigning to ducarroz
Assignee: rhp → ducarroz
Status: ASSIGNED → NEW
Assign it to myself.
QA Contact: pmock → fenella
There is two potential problems here: 1) Mozilla doesn't support yet encription (PGP) 2) The attachment part doesn't have a name, therefore we don't display it as a valid attachment Question: Does the signature appears inline?
Status: NEW → ASSIGNED
We are not showing pgp signature part in Mozilla, neither as inline or as attachment, it's by design.
Summary: Attachment not shown when reading mail → PGP Attachment not shown when reading mail
How can it be by design to hide attachments? If we dont support pgp signature, we should at least just show the pgp signature as a orinary attachment.
you are probably right. I need to find why we decide to not do that. In any case it won't be a simple fix as I would need to review the architecture. Just for your information, pgp support is coming, see bug 22687
QA Contact: fenella → esther
To Esther ..
As the name says, the attachment in question is a PGP signature. Just as an S/MIME signature, it's not a real attachment and has absolutely no value without a PGP-supporting mailer. Showing it as attachment would only cause confusion. What we could do is showing some text like "This message is possibly signed.", like we do for S/MIME, but considering the state of bug 22687, this would only be a waste of time.
QA Contact: esther → trix
This is bad!!! I have been sent e-mails which were pgp signed by Evolution (the Gnome standard mail application). Until today, when I did a view source, I did not even notice that it was signed in some way, as there is *NO* visual indication. Had I seen the signature, I could have verified the text with a press of a key. As long as we do not know what to do with pgp, let the user see the attachments. That is the least we can do... Sorry for this bugzilla spam. But futuring this bug is IMHO not a good a idea...
I just got very confused by this bug (still present in 1.5a) and would like to second the opinion that Mozilla really should show some indication that there is a part of the mail it cannot process or display. IMHO, no part of the message body ought to be silently ignored.
Product: MailNews → Core
The issue still seems to exist in late 2005. I use Thunderbird. I got an email that should contain just an attachment (the sender somehow encrypted a word doc). But Thunderbird does not show any sign of an attachment. I just see that the mail is rather large for an empty message. So I check the source and there is something. I'm going to attach the saved message to this bug
forgot to mention: when I open this .eml in Outlook Express I get the attachment correctly listed. My TB Version is version 1.5 Beta 2 (20051007)
Assignee: ducarroz → nobody
Status: ASSIGNED → NEW
QA Contact: stephend → mime
Product: Core → MailNews Core
Priority: P3 → --
Target Milestone: Future → ---

(In reply to Ben Bucksch (:BenB) from comment #18)

As the name says, the attachment in question is a PGP signature. Just as an
S/MIME signature, it's not a real attachment and has absolutely no value
without a PGP-supporting mailer. Showing it as attachment would only cause confusion.

currently it does show as an attachment

What we could do is showing some text like "This message is possibly
signed.", like we do for S/MIME, but considering the state of bug 22687, this would
only be a waste of time.

What is the path forward? Do we fold this in with another issue? (I'd be surprised if this is the only report)

Flags: needinfo?(kaie)
See Also: → https://bugzilla.mozilla.org/show_bug.cgi?id=22687

(In reply to Wayne Mery (:wsmwk) from comment #24)

currently it does show as an attachment

If the attachment is shown, the original complaint no longer applies, and this bug should be resolved WORKSFORME.

What we could do is showing some text like "This message is possibly
signed.", like we do for S/MIME, but considering the state of bug 22687, this would
only be a waste of time.

What is the path forward? Do we fold this in with another issue? (I'd be surprised if this is the only report)

Wait for bug 22687.

Flags: needinfo?(kaie)
Severity: normal → S3

It shows as an attachment. I guess it's a pgp signed .doc file.

Status: NEW → RESOLVED
Closed: 1 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: