Open Bug 1626890 Opened 5 years ago Updated 4 years ago

Auto-forwarding incoming Messages (with Filter Rules) fail if incoming Message has been signed/encrypted by Sender

Categories

(Thunderbird :: Filters, defect)

defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: scrap, Unassigned)

References

Details

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

Steps to reproduce:

On a standalone computer with Thunderbird we have set up a filter rule that automatically forwards all incoming messages to a variety of recipients.

Hereby we have observed two problems:

1.) If the initial sender of the email has signed/encrypted his message, the filter rule won't get applied, so in consequence nobody will receive the incoming message.

2.) If the default mode of Thunderbird/Enigmail is set to automatically sign all outgoing messages, the mentioned filter rule won't get applied as well.

Actual results:

Observed behavior:

1.) Filter rule (forwarding message to recipients) won't get applied if sender has signed/encrypted his message. Even all PGP-keys are accepted correctly.

2.) Filter rule (forwarding message to recipients) won't get applied if Thunderbirds default behavior is set to automatically sign outgoing messages with PGP-key of the account identity.

Expected results:

Expected behavior:

Filter rule (forwarding message to recipients) will be applied, even if sender has signed/encrypted his message.

AND

Filter rule (forwarding message to recipients) will be applied, even if Thunderbird is configured to auto-sign all outgoing messages with PGP-key of the sending identity.

Do you know in which version this broke?

Flags: needinfo?(scrap)

(In reply to Wayne Mery (:wsmwk) from comment #1)

Do you know in which version this broke?

We have experienced this issue in Thunderbird version 68.6.0.

Flags: needinfo?(scrap)

So it worked in version 68.5.0? If it did, what was the first version you noticed it wasn't working, or the last version you remember it was working.

(In reply to Wayne Mery (:wsmwk) from comment #3)

So it worked in version 68.5.0? If it did, what was the first version you noticed it wasn't working, or the last version you remember it was working.

Unfortunately we didn't try this in previous versions... :-(

For 68 PGP is still through Enigmail.

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Severity: normal → --
See Also: → 1662408
You need to log in before you can comment on or make changes to this bug.