Communicator did not require to manually configure a certificate for S/Mime. It simply automatically used the latest certificate available that was issued for the used email account. I suggest the S/Mime security preferences could be optional. By default, the preferences could be set to "automatically choose the encryption certificate". A separate option could allow the user to empower the user to explicitly select the cert, as it is currently required to be done.
Severity: normal → enhancement
Target Milestone: --- → Future
Mass reassign ssaux bugs to nobody
Assignee: ssaux → nobody
Mass change "Future" target milestone to "--" on bugs that now are assigned to nobody. Those targets reflected the prioritization of past PSM management. Many of these should be marked invalid or wontfix, I think.
Target Milestone: Future → ---
Component: Security: S/MIME → Security: S/MIME
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.