Closed Bug 19064 Opened 26 years ago Closed 26 years ago

Provide feedback that mozilla can't deal with encrypted mail

Categories

(MailNews Core :: MIME, defect, P3)

Product:
MailNews Core
Component:
MIME
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: phil, Assigned: bugzilla)

Details

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.
Status: NEW → ASSIGNED
Target Milestone: M14
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
QA Contact: lchiang → pmock
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
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.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
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
clearing resolution.
Status: REOPENED → ASSIGNED
Target Milestone: M14 → M13
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
Sure Rich. I will re-test win32 and update this bug. I want to test with the new M12 build.
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.
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
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.
check with leaf for the release builds.
Assignee: rhp → leaf
Status: ASSIGNED → NEW
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
Assignee: leaf → rhp
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.
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.
Assignee: rhp → ducarroz
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
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 26 years ago → 26 years ago
Resolution: --- → FIXED
Fixed and checked in. Now the next release package should include both smime.shld and signed.shlb
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.
Status: RESOLVED → VERIFIED
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.