BTW thanks for the detailed feedback and suggestions. (In reply to vv01f from comment #45) > aliases could configure several other things as well. we had PGPMime, sign, encrypt and negateRule in Enigmail. This is a different kind of rules, not aliases. You're suggesting to automatically influence the way an email will be sent, depending on the recipients. That's a separate kind of complexity, and with more room for potential conflicts between rooms. If we need that class of rules, it's a separate task, more like an automation feature. It seems out of scope for this recipient-alias bug.
Bug 1644085 Comment 47 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
BTW thanks for the detailed feedback and suggestions. (In reply to vv01f from comment #45) > aliases could configure several other things as well. we had PGPMime, sign, encrypt and negateRule in Enigmail. This is a different kind of rules, not aliases. You're suggesting to automatically influence the way an email will be sent, depending on the recipients. That's a separate kind of complexity, and with more room for potential conflicts between rules. If we need that class of rules, it's a separate task, more like an automation feature. It seems out of scope for this recipient-alias bug.