Dirk Munk wrote:
meagain wrote:
-------- Original Message --------
Dirk Munk wrote:
When you want to send a message, you have the option to encrypt the
message with "Security", assuming you and the other party have set
up Digital Signing.
It would be a nice feature if you could have an option "always send
encrypted" with every address book entry.
An alternative would be a general setting "always send encrypted if
possible", which means the mail program has to look if a
certificate has been stored, and then send encrypted if a
certificate has been found.
...
For legal reasons, certain email traffic must be encrypted, from end
point to end point. For instance emails between me and my doctor.
Assuming we have both set up digital signing, any email traffic
between us should *always* be encrypted, automatically. I should not
have to choose Security > Encrypt This Message to get encryption.
You want this feature setup on a per-recipient basis just like
"prefers to receive mail as " <html/plaintext/any>.
Yes, that would be an option.
However, I also have an alternative option.
When you want to send each other encrypted emails, you have to exchange
the certificates first. So I have to send the recipient a signed email
message, and he has to send me a signed email message as well. As soon
as I receive his signed email message, its certificate will be stored on
my computer. My certificate will have been stored on his computer.
From that moment on we can send each other encrypted email messages.
For various reasons, it's not recommended to use the same keypair for
both encryption and signing.
Now suppose I want to send this recipient an email message. Then mail
could look in the stored certificates for his certificate. When found,
mail could automatically send the message encrypted.
That is an even cleaner way of setting it up. No need to add an entry to
the address book, everything is done automatically.
With this scheme, what happens when the public key / certificate you
hold for the recipient expires, or is somehow deleted for any reason?
From that point on, you no longer hold a key for that recipient, so
future emails would be sent UNencrypted without any warning.
It probably would be better to set a flag in the address book indicating
that all messages to that recipient should be encrypted, and get an
error or warning if that's not possible for any reason. I'm not entirely
sure if that would be 100% reliable either, for example if you enter the
email address directly rather than selecting the address book entry, or
if you end up with two entries for that recipient (e.g. one you've set
up and one in "Collected Addresses") but only one is flagged for
encryption. For a HTML/text preference, it's not so critical if the
occasional message if sent with the wrong setting, but for encryption
you'd want to be sure it's always used.
While it's useful to discuss ideas on this list, the best place to
submit feature requests is on SeaMonkey's bug tracker at
<https://bugzilla.mozilla.org/> (please search for similar existing
requests before submitting a new one). At the moment, the SeaMonkey
developers are struggling just to keep up with changes being made by
Mozilla to the Firefox code SeaMonkey is based on, so I wouldn't expect
requests for new features to be implemented very quickly, but putting it
on the bug tracker means it's less likely to be completely forgotten.
--
Mark.
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
