Provide feedback that mozilla can't deal with encrypted mail

VERIFIED FIXED in M13

Status

MailNews Core
MIME
P3
normal
VERIFIED FIXED
18 years ago
9 years ago

People

(Reporter: Phil Peterson, Assigned: Jean-Francois Ducarroz)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
Transferred this issue out of bug 18200

It would be nice for mozilla to detect when a message won't be able to be
rendered, and give some appropriate feedback. Or maybe even try to render it
using text/plain. But blank body is probably not good.

Updated

18 years ago
Status: NEW → ASSIGNED
Target Milestone: M14

Comment 1

18 years ago
I'll see what I can do...I'd like to think I could output something saying that
we can't deal with encrypted email, blah, blah, blah...

- rhp

Updated

18 years ago
QA Contact: lchiang → pmock

Updated

18 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED

Comment 2

18 years ago
You should now get a nice message saying that the email is not able to be
displayed. I'll be checking in the Mac script change today, but this is fixed
on Windows and Unix.

Updated

18 years ago
Status: RESOLVED → REOPENED

Updated

18 years ago
Resolution: FIXED → ---

Comment 3

18 years ago
Verified on Mac using the following M12 build:
ftp://sweetlou/products/client/seamonkey/macos/8.x/ppc/1999-12-17-10-M12/NSMacInstaller-M12.sea.bin
It displays in the message pane the following:
 "This is an ENCRYPTED nessage. Mozilla mail does not support encrypted mail".
It displays the attachment paperclip to show the smime attachment.  I tested
using messages that were signed, encrypted, and signed&encrypted.  I sent plain
text and html message.  I sent test message from 4.7 from win32, macos, and
linux.

Problem: On win32 and Linux, it does not provide any feedback.  The message pane
is blank.  It shows the attachment clip and the smime attachment name.  I viewed
encrypted message sent from win32, macos, and linux.  In each case, the message
pane was blank.

Re-open bug.

I was testing win32 and linux with the following builds:
ftp://sweetlou/products/client/seamonkey/windows/32bit/x86/1999-12-17-13-M12/seamonkey32e.exe
ftp://sweetlou/products/client/seamonkey/unix/linux_glibc/2.2/x86/1999-12-17-10-M12/netscape-i686-pc-linux-gnu.tar.gz

Comment 4

18 years ago
clearing resolution.

Updated

18 years ago
Status: REOPENED → ASSIGNED
Target Milestone: M14 → M13

Comment 5

18 years ago
Ok, I have the Linux/Unix side of this fixed. It was a simple problem of not
building the SMIME component on Linux (a makefile fix). This will be any build
of the tip after today (12/21/99).

What I don't understand is Win32. Can you check your distribution and see if
there is an SMIME.DLL in your components directory? If there is, this should
work. Can you retry it with Win32?

- rhp

Comment 6

18 years ago
Sure Rich.  I will re-test win32 and update this bug.  I want to test with the
new M12 build.

Comment 7

18 years ago
I installed today win32 commercial seamonkey build 1999-12-21-00-m12 and
1999-12-21-09-m13.  I can't find smime.dll in the component directory or any
other seamonkey subdirectory.  I feedback message does not come up in M12.  I
didn't test M13 since I couldn't find the smime.dll after installing.

Comment 8

18 years ago
Hmmm, this is weird. I have a feeling this may be an installer problem because
I know this is part of the Win32 build system.

I should reassign this to the installer team and see if they have to do
something special to add this to the build process. Who is doing the release
builds?

- rhp

Comment 9

18 years ago
Rich,

I believe this is an installer issue because, in my tests, I have been running
the seamonkey installer 'seamonkey32.exe'.

If I use installer.exe from the backup directory then the smime.dll is
installed.  The backup directory is not the real release installer.  It used as
a build check.  To use it, you need to download all the files in the backup (see
below for location) directory into a temp directory then run the installer.exe.

ftp://sweetlou/products/client/seamonkey/windows/32bit/x86/1999-12-21-00-M12/backup/install.exe

When I had the smime.dll installed, the win32 platform correctly displays the
feedback message in the message pane when an encrypted mail message was
selected.

Comment 10

18 years ago
check with leaf for the release builds.

Updated

18 years ago
Assignee: rhp → leaf
Status: ASSIGNED → NEW

Comment 11

18 years ago
Hi Leaf,
We need to add the file SMIME.DLL to the release build installer process. This
goes in the components directory. Also, there will soon be a file called
SIGNED.DLL that will also have to be added to the install. These are just stub
files to let people know that they can't read this with Mozilla mail.

- rhp

Updated

18 years ago
Assignee: leaf → rhp

Comment 12

18 years ago
where is this dll produced? in the mozilla tree? If not, i'm not packaging it.
If so, you can add it to the component of your choice (mail, is my guess), with
the mozilla/xpinstall/packager/packages-[win,mac,unix] file. Reassigning back to
rhp.

Comment 13

18 years ago
where is this dll produced? in the mozilla tree? If not, i'm not packaging it.
If so, you can add it to the component of your choice (mail, is my guess), with
the mozilla/xpinstall/packager/packages-[win,mac,unix] file. Reassigning back to
rhp.

Updated

18 years ago
Assignee: rhp → ducarroz

Comment 14

18 years ago
Hi JF,
This is the bug to track adding SMIME.DLL and SIGNED.DLL to the builds. After
we add the builds to the process, we also have to update the file:

             mozilla/xpinstall/packager/packages-mac

and make sure that these new DLLs are part of the installer.

Thanks for the help!

- rhp
(Assignee)

Updated

18 years ago
Status: NEW → ASSIGNED
(Assignee)

Updated

18 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago18 years ago
Resolution: --- → FIXED
(Assignee)

Comment 15

18 years ago
Fixed and checked in. Now the next release package should include both
smime.shld and signed.shlb

Comment 16

18 years ago
Thanks Jeff.  I will check it on the Mac on the next commercial build. :)

I re-tested on Win32 and Linux using the following builds:
ftp://sweetlou/products/client/seamonkey/windows/32bit/x86/2000-01-03-09-M13/sea
monkey32e.exe
ftp://sweetlou/products/client/seamonkey/unix/linux_glibc/2.2/x86/2000-01-02-09-
M13/netscape-i686-pc-linux-gnu.tar.gz

On Win and Linux, it now displays the the proper feedback.
On encrypted messages, it displays "This is an ENCRYPTED message. Mozilla Mail
does not support encrypted mail."
On signed messages, it displays "This messages is possibly SIGNED. Mozilla does
not support signed mail."

Verified on win and linux.  Need to verify on Mac on next release build.

Updated

18 years ago
Status: RESOLVED → VERIFIED

Comment 17

18 years ago
Verified on Mac commercial build using the following build found at:
ftp://sweetlou/products/client/seamonkey/macos/8.x/ppc/2000-01-04-09-M13/NSMacIn
staller-M13.sea.bin

Verifying bug as fixed.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.