Open Bug 1820748 Opened 3 years ago Updated 4 months ago

Filters are applied to autosaved draft emails

Categories

(MailNews Core :: Filters, defect)

Thunderbird 102
x86_64
Windows 10
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: massimob88, Unassigned, NeedInfo)

References

Details

+++ This bug was initially created as a clone of Bug #681474 +++

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.854.0 Safari/535.2

I have the same problem with all users thunderbird updated to 102.8.0 (64 bit) version.

Steps to reproduce:

I have an IMAP account with several folders. Also I have for almost each of these folders a filter that moves incoming mail to the folders depending on e.g. whether the subject contains a certain term. I also set the preference to store answers to an email in the email's folder.
When I reply to an email in one of those imap folder for which I have a filter, the following happens

Actual results:

When the autosave functionality for the draft email reply kicks in, it stores the draft in the "Drafts" folder. Then my filter is apparently applied to the draft email in the Drafts folder and the draft is stored in my IMAP folder - I see a log event like "Moved 1 email from Drafts to <FOLDER>. This happens for each of the autosaved drafts. If composing the reply email takes some time, my IMAP folder is cluttered with draft replies, which are also not automatically deleted after I send the reply mail.
This also happens in save mode with all extensions disabled.
Deleting and re-implementing all filters also did not change anything in the behaviour described above.

Expected results:

Filters should not be applied to the Drafts folder. Drafts should stay in the Drafts folder and be deleted after the final mail has been sent.

See Also: → 1857900
See Also: → 1867313
See Also: → 1799293

Max, do you still experience this issue?

Flags: needinfo?(massimob88)

Other reports https://mzl.la/3KGD9dc

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