Build 2002102008. When trying to send a mail sigend by default, I get <<sending of message failed. Unable to sign message. Please check that the certificates specified in Mail & Newsgroup Account Settings for this mail account are valid and trusted.>> 1) I am confused, because there is no certificate option there. I only find them under "Preferences - Privacy & Security - Certificates - Manage Certificates". And there my certificates look fine. 2) What can I do to be able to send signed mail out again?
With the Mail window open, Edit>Mail/News Preferences. Click on Security, and choose your signing and encrypting certificates.
Assignee: mstoltz → ssaux
Component: Security: General → S/MIME
Product: MailNews → PSM
QA Contact: junruh → carosendahl
Version: other → 2.4
sorry, in my mail window under "Edit", I have either i) Mail & Newsgroups Account Settings or ii) Preferences but not the "Mail/News Preferences" you mention. And neither has a clickable "Security" item. The only thing I can imagine is that once I downloaded enigmail that may have made the menu options you are talking about disappear?
Under Mail & Newsgroups Account Settings, each mail account should have a security entry in its tree listing. From the panel you can select your signing and encrypting cert. If you do not see it, then something munged during the installation. You might need to remove the mozilla directory and reinstall the build.
We are seeing other bugs at the moment related to trust issues in the CA chains. If you find that your certs are already configured for smime, then most likely you are experiencing this other problem.
Created attachment 103702 [details] menus available in mail account settings Carl, Thanks for the info. Two questions: 1) Could you please cross-reference/hyperling the bug you are mentioning? 2) Removing the Mozilla directory and reinstall sounds awkward - will I not lose all my cookie settings, stored passwords etc.? Rgds r.
Cc Kai on this. I am not sure what happened to your installation, but the fact that the security element is not displaying for each account is a sign that something went wrong in the installation (the security item is an RDF overlay that somehow did not overlay). Don't delete your documents&settings->hauser->application data->... directories. Just delete the Program Files->Mozilla.org-><browser binaries> directory. This won't affect any of your personal settings stored in the profile directories mentioned above. The new installation will still use your existing personal info. The bugs I am referring to are: bug 171331 and bug 173939. At this point I don't think that they are your problem.
Charles, I did this, and the good news is that the security tab is now back for my mail accounts and I can see my key. When trying to send a message, however, the error message still appears.
Well, at least there is a little progress. The next thing to check is Under edit->preferences->provacy&security->certificates->Manage Certificates First, under your certificates, verify under 'purposes' that sign and encrypt are displayed. If not, Second, under authorities, select the siging CA certificate and choose edit. Verify that the checkbox for email is still ticked. Third, try to send yourself a signed/encrypted message and see if it works. Verify that you are being prompted for your master password (Also if you are in FIPS mode, turn off FIPS mode and restart the browser) when you attempt to send the message. If everything looks as described above, then let me know who the CA is that issued your certs so I can add it to the list in the bugs I mentioned above.
Carl, My certificate said <Issuer not Trusted>. Then, I went in under Authorities and 2 out of the 4 Thawte certificates had the e-mail not checked, including my "Personal Freemail RSA 2000 8.30". Now it works with the following limitations: 1) No password was asked for signed messages 2) Only one e-mail address usable for encryption out of multiple addresses in a certificate (I reported that in http://bugzilla.mozilla.org/show_bug.cgi?id=176451) 3) While messages arrive perfectly in MS Outlook, they still look broken in the Mozilla's sent folder (see http://bugzilla.mozilla.org/show_bug.cgi?id=152865) 4) What good does FIPS do to me (see http://bugzilla.mozilla.org/show_bug.cgi?id=176460)? Also, it is very kind of you to coach me individually through all of this. However, I fear this won't scale. Did your team ever consider to a) Have each error with a unique error identifier b) Have each error with a hyperlink into a knowledge base for self-help/or bugzilla reporting connection? Regards Ralf
We work on enhancing the error messages as we encounter code areas being changed/fixed that generate the current messages. I duped the bug related to multiple email address support - a feature we would like to support. I am going to close this as a dup of the bugs referenced in comment 6, as I have several users I am tracking through those bugs to get the CA cert chain verification code back on track. (Sorry to close this out, I just like to keep the bug lists nice and tidy) *** This bug has been marked as a duplicate of 171331 ***
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
Component: Security: S/MIME → Security: S/MIME
Product: Core → MailNews Core
QA Contact: carosendahl → s.mime
You need to log in before you can comment on or make changes to this bug.