When receiving a signed email, if the email adress does not match the certificate content, a question mark will be shown over the security icon. The Message Security will display a warning text about the non-matching email, and a button to see the cert details. The change request is : - add a button to enable to manually trust this cert with this email from now : This would create an entry in the cert db associating the cert with the email, even if the email does not appear in he cert. As a result : - in the future, email coming from this adress with this cert would be trusted and not display the question mark anymore. - it would be possible to send encrypted messages to this email using this cert. This would implement a request that can be found in the comments of bug 30883.

Mass reassign ssaux bugs to nobody

This would be usefull feature. Here we have support@ourdomain that forwards to all IT department. When someone from us replies not personally (from: support@...) and signs the message this will cause warning. We can use a new certificate for support@.., but I prefer everyone using his own - you can see who replayed (we have signatures for this purpose, but), sharing a certificate between users is bad for me. PS: If this is implemented at some point, there should be UI to remove such "valid email <-> certificate" pairs.