User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

Steps to reproduce:

No setting available

Actual results:

No setting available

Expected results:

Different e-mail recipients have different requirements. For example, some e-mail providers block e-mails that are digitally signed, or quarantine such e-mails. (I realise that this behaviour is ridiculous, but it happens not infrequently; I know of several mailing lists and also some ISPs and corporate e-mail filters that behave in this way.)

There should be way to set TB so that the default is to sign e-mails, but then be able to over-ride that default on a per-user basis; and this should be sticky, so that it needs to be set only once for each user.

Similarly, there may be some users to whom e-mails MUST be encrypted, whereas one might reasonably want the default to be not to encrypt e-mails, even if the recipient's public key is available. Or vice versa.

[Enigmail, of course, could do all this. At this point, I have effectively turned E2EE off because it is too inflexible for practical use principally because there seems to be no way to set up a list of per-recipient settings.]

Sounds like a duplicate of bug 1644085.

bug 1644085 is very confusing to me. It seems to be reporting the lack of two different features, one of which I agree appears to be the same as the one I reported in this bug. But 1644085 includes a proof-of-concept fix for the /other/ bug (the lack of groups), but I don't immediately see that that would help with problem in this bug. Maybe I'm not understanding properly and these two features are somehow identical.

To try to be a tad clearer: bug 1644085 seems to reporting a lack of groups AND a lack of per-recipient rules. I have never used groups. Presumably, these two things are not identical to each other, otherwise why would enigmail have had two features to do the same thing? Ultimately, what I do know is that enigmail had per-recipient rules, and now TB does not have them... and that renders the current version(s) of TB useless for me insofar as trying to send signed e-mail is concerned: if I configure TB to attach a signature, I am bound to forget to remove the signature when I send an e-mail to an addresses that can't handle it (typically by silently discarding the e-mail; sometimes by sending it silently and idiotically to some kind of quarantine that may or may not be checked by the recipient; sometimes by sending me a message that the e-mail violates [brain-dead] policy on the receiving server and won't be delivered). So I have configured TB not to sign my e-mails, which makes the feature in its current state rather pointless :-(

(In reply to Christian Riechers from comment #1)

Sounds like a duplicate of bug 1644085.

No. Bug 1644085 and this bug request different aspects.

Bug 1644085 is for changing the encryption keys that are used for a given recipient address.

This bug requests to define automatic disabling or enabling of signing/encryption.