Closed Bug 127364 Opened 23 years ago Closed 22 years ago

Unable to send signed messages

Categories

(MailNews Core :: Security: S/MIME, defect, P2)

Product:
MailNews Core
Component:
Security: S/MIME
Version:
1.0 Branch
Platform:
x86
Windows 2000
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME
Milestone:
psm2.2

People

(Reporter: mscott, Assigned: KaiE)

Details

(Keywords: regression) 

I just downloaded todays bits: 2002022203. When I try to send a signed message I
get an alert dialog while we are assembling the message saying: 

"Sending of message failed. Please verify that your account settings are correct."

I can send encrypted messages just fine. The problem is only with signed messages. 

I think this bug has two issues we should look at:

1) figure out why signed messages aren't working
2) figure out a way to have a security specific warning here instead of the
generic check your account settings.
I wonder if we should nominate this for .9.9 unless I'm the only one whose
having trouble...
Keywords: nsbeta1, regression
S/MIME
Assignee: kaie → ssaux
Component: Security: General → S/MIME
Product: MailNews → PSM
QA Contact: junruh → alam
Version: other → 2.2
It worked fine for me using 2002022203 build on WinNT.
Trying to test that with my own build (a couple of days old), it worked.

I fetched today's sources and made a depend build.

On first attempt, I saw your problem.
On second attempt I crashed.

After a full clobber rebuild, everything worked.

Either this is meanwhile fixed, or the build you used was a broken depend build.
Ian Mcgreer told me, he believes NSS is not doing depend builds correctly.

Scott, are you still seeing the problem?

Using a release build from: 2002022503 (yesterday), I still see this problem.
Encrypted is working fine still. Just signed messages. Very strange. They are
both using the same cert.
That could be a problem local to your certificate database.

Maybe the crypto engine is refusing to use your cert for signing. You could try
to use certificate manager and look at the details of your own cert, whether it
is listed as verified/valid etc. for both signing and encrypting.

Obviously the status feedback to the user on crypto failure is not good enough
yet. See also bug 121287 for another example of this.

I think this bug might be a duplicate for the one I just
sent in, 129936.  Sorry about that.

This must be fixed.
kai.
Assignee: ssaux → kaie
Priority: -- → P2
Target Milestone: --- → 2.2
Marking fixed. Sending signed mail works for me.
Status: NEW → RESOLVED
Closed: 22 years ago
QA Contact: alam → junruh
Resolution: --- → FIXED
re-opening.

there is no patch attached to this bug. Why do you think it's fixed? 

Using 2002030908, I still have the same problem I described before. Encrypted
works great, signing is still failing. Both use the same cert. I used this cert
before to send signed messages.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
John just came by my cube to help me figure out what's going on. Some how my
cert manager lost the trusted state for GTE Corporation. This caused my cert to
no longer be verified. Putting the trusts back on this cert fixed the problem.

This is the same profile I've used since netscape 6.0 so I'm not sure how it
lost the trust information, but I won't complain. Thanks John!
Status: REOPENED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → WORKSFORME
Filed bug 131087
Verified worksforme.
Status: RESOLVED → VERIFIED
Product: PSM → Core
Version: psm2.2 → 1.0 Branch
Product: Core → MailNews Core
QA Contact: junruh → s.mime
You need to log in before you can comment on or make changes to this bug.