Tag applied by filter is automatically removed after replying to an email or changing folders
Categories
(Thunderbird :: Filters, defect)
Tracking
(thunderbird_esr153 unaffected)
| Tracking | Status | |
|---|---|---|
| thunderbird_esr153 | --- | unaffected |
People
(Reporter: 9mbetv23t, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:154.0) Gecko/20100101 Firefox/154.0
Steps to reproduce:
I received a new email from an email address that is included in a filter that applies a specific tag to the message.
Actual results:
At first the tag was applied automatically when the email arrived, but later when I replied to the email or changed folders (for example, from Inbox to Sent), the tag was removed from the message. When I tried to apply another random tag by selecting it from the drop-down menu, the tag was applied but then automatically removed.
Expected results:
The filter should have worked as expected, applying the tag to both the incoming message and its replies.
|
||
Comment 1•1 month ago
|
||
What version please?
|
|
||
Updated•1 month ago
|
(In reply to Wayne Mery (:wsmwk) from comment #1)
What version please?
Version 154.0 | Released August 18, 2026
|
|
||
Comment 3•1 month ago
|
||
Thanks. Am assuming then that this doesn't happen in v513
|
||
Comment 4•15 days ago
|
||
Maybe this is the length issue from bug 2073409. Can you provide the exact tag that failed?
(In reply to Hartmut Welpmann [:welpy-cw] from comment #4)
Maybe this is the length issue from bug 2073409. Can you provide the exact tag that failed?
A tag example is χρυσικοπουλος-σπυρος, another is ροκος-στεφανος.
The problem does not occur in version 156.0, which I'm currently using.
|
|
||
Comment 6•15 days ago
•
|
||
(In reply to 9mbetv23t from comment #5)
(In reply to Hartmut Welpmann [:welpy-cw] from comment #4)
Maybe this is the length issue from bug 2073409. Can you provide the exact tag that failed?
A tag example is χρυσικοπουλος-σπυρος, another is ροκος-στεφανος.
The problem does not occur in version 156.0, which I'm currently using.
Thanks for the quick response. So this is very likely a duplicate of bug 2057187.
Description
•