Closed Bug 1681678 Opened 5 years ago Closed 5 years ago

Move to inbox vs. pre-defined filters

Categories

(Thunderbird :: Untriaged, enhancement)

x86_64
All
enhancement

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: sexxxenator, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4215.0 Safari/537.36 Edg/86.0.597.0

Steps to reproduce:

  • Created automatic filters for mails coming from xxx@yyy.com to move them into a directory XXX/ under my Inbox
  • Received a very important email from xxx@yyy.com
  • Viewed it in Inbox/XXX/ , marked it as "Important" (red label)
  • However, I didn't wanted to miss it, because I don't visit Inbox/XXX very often, so I wanted to have it also in my Inbox, so I selected the email and clicked "Move to Inbox" (I've also tried with "Copy to Inbox")

Actual results:

The email stayed in Inbox/XXX (or disappeared for a few sec, then re-appeared in the Inbox/XXX <- this is indeed the behaviour that helped me understand what was happening)

Expected results:

The email should have stayed in the Inbox, like I asked it to do! Or a warning should have been displayed to help me understand why the message did not move when I asked it to do so.

I can understand what is happening (message is sent to Inbox, but filters are then re-applied, thus message ends up again in Inbox/XXX/), but that would be nice if one could indeed make the "Move/Copy to Inbox function" (definitively) work as expected (idea : mark a message as not susceptible to filters?)

Instead of moving the message where it will be filtered again, create a new folder named Important and move the message there.

Version 68 is also EOL and Thunderbird 78.x.x would allow you to color the folder red.

OS: Unspecified → All
Hardware: Unspecified → x86_64
Version: 68 → Trunk

You probably should tag the message with something special, then make sure the filter excluded messages tagged with that.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.