Open Bug 1848137 Opened 2 years ago Updated 1 year ago

Thunderbird ignores preferred e2e encryption method when switching accounts

Categories

(Thunderbird :: Message Compose Window, defect)

Thunderbird 115
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: Nic, Unassigned)

Details

Steps to reproduce:

(Background Info)
I have two accounts set up in my TB:
Account #1 has OpenPGP and S/MIME enabled. It is set to prefer S/MIME and to sign all outgoing e-mails.
Account #2 has no e2e encryption selected. I'm using this account only to receive e-mails.

(What did you do?)
I have received an e-mail in account #2. After clicking on reply, I'm changing the "From" account to account #1.

Actual results:

Sign with OpenPGP is selected.

Expected results:

S/MIME should be selected, as this is the account's preferred encryption method.

This was filed before as bug 1806328 which was duped to bug 1675737.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Duplicate of bug: 1675737
Resolution: --- → DUPLICATE
Status: RESOLVED → UNCONFIRMED
No longer duplicate of bug: 1675737
Resolution: DUPLICATE → ---

(In reply to Francesco from comment #1)

This was filed before as bug 1806328 which was duped to bug 1675737.

I agree that this a duplicate of bug 1806328, but I don't think it's actually a duplicate of bug 1675737.
Reason: Bug 1675737 is about the implementation of an automatic mechanism that chooses S/MIME or OpenPGP based on the recipient's capabilities ("select automatically based on available keys or certificates").

This bug as well as bug 1806328 is about the fixed method not being obeyed. No automatic choice mechanism is necessary, TB should just follow what is set.

(In reply to Nicolai [:Nic] from comment #3)

I agree that this a duplicate of bug 1806328, but I don't think it's actually a duplicate of bug 1675737.

The duplication of bug 1806328 was done by the triage owner. If you don't agree with that decision, you should ask him. In the end it's not important as long as the issue receives some attention.

You need to log in before you can comment on or make changes to this bug.