Mail sent unsigned although "Digitally sign this message" ist selected!

RESOLVED INVALID

Status

MailNews Core
Security
RESOLVED INVALID
15 years ago
10 years ago

People

(Reporter: Frank, Assigned: (not reading, please use seth@sspitzer.org instead))

Tracking

Trunk
x86
Windows NT

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       
Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.5) Gecko/20031007

Mozilla will send the current eMail unsigned although the option "Digitally sign
this message" in implicitly and explicitely selected. This only seems to occur
when the send process is being cancelled by the user and later on restarted.

Reproducible: Always
Steps to Reproduce:
1. Open a new "Compose Mail" window
2. Input a recipient address
3. Input the subject/text and click on "Send"
4. Mozilla asks for the MasterDB password
5. Click on "Cancel" to abort the process
6. Revise the mail, e.g. change its text
7. Optional: Check the Security setting for this mail, the still seem to be
okay: "Digitally sign this message" is active
8. Click on "Send"
9. Voilà: The message will be sent, but UNSIGNED!!!

Actual Results:  
Mail was sent unsigned although otherwise selected. No Multipart-structure is
being created to hold the signature part. Mozilla behaves as if I have selected
not to sign the mail.

Expected Results:  
The mail should have been sent with a proper x509 signature!

Comment 1

15 years ago
I can't reproduce this with current versions. You should check this with a newer
build (recent nightly or 1.7a, maybe 1.6 is enough too).
(Reporter)

Comment 2

15 years ago
I have now testet it again with

   Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5) Gecko/20031007

but as you can see, under win98SE. Whether this makes the difference, I can't
tell. I will double check my NT install tomorrow at work and post here again.
As a matter of fact, my win98SE install of Mozilla 1.5 does not show this odd
behaviour.

Maybe others, like Patrick (Hi there! :)), could clarify which version they use
and whether they experience such "won't sign" behaviour as well. Strange... An
NT issue? Can't really believe that... Okay, I'll see tomorrow.
(Reporter)

Comment 3

15 years ago
I tried to reproduce this behaviour and it happened again.

As the two mozillas are the same on win98SE and winNT-SP5 I assume that it might
have something to do with the extensions I have installed on winNT.

In the MailNews area I use Enigmail version 0.82.6.0

Enigmail defaults to "Do not encrypt" and "Do not sign" because I use x509
signing primarily. The x509 defaults are "Do not encrypt" and "Digitally sign
the message". I deactivate x509 signing and select some enigmail actions in case
I want to use PGP stuff.

Maybe this causes the problem?

How do we go about it? Can I install a second moz1.5 without any extensions on
the same NT machine to check whether it's enigmail causing the odd behaviour?

Any help is appreciated. This thing should be resolved...

Comment 4

15 years ago
Yep, a clean install without any extensions would be good. If it doesn't happen
then, add Enigmail to this same install and try again.
Although I'm not sure if Enigmail is to blame if it fails when installed, they
should at least getting informed.
(Reporter)

Comment 5

15 years ago
Hi! - I made a clean install of moz1.5 on my winNT machine without installing
mozilla -> Everything works fine.
Then I installed Enigmail... Yes, we were right, it's Enigmail that causes the
bug. I filed a bug on the mozdev-bugzilla system (#5885). Maybe this bug can be
closed then? Maybe I should wait until the enigmail people have commented on
that. Cu!

Comment 6

15 years ago
Thanks for tracking down the cause of this. I'll mark this as INVALID for now.
Should the Enigma people want to add Moz related matters, please reopen this, ok?

Thanks again!
Status: UNCONFIRMED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → INVALID
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.