User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:92.0) Gecko/20100101 Firefox/92.0

Steps to reproduce:

I run "Move message to" filters on getting new mail to move mail into subfolders.

Since updating to version 91 tray icon notifications and alerts for new mail do not work anymore.

Disabling the filters (or using copy instread of move) solves the issue.

Actual results:

Tray icon and alerts notification don't work, sound notifications do.

Expected results:

All notifications should work.

Using the "Move later" action that comes with the addon FiltaQuilla (https://quickfilters.quickfolders.org/filtaquilla.html) solves the issue too.

To me this feels like the mail is moved away from the inbox faster than notifications are triggered.

Same problem happens in Thunderbird 91.1 and 91.2.

When filters are applied before Junk classification, notified by sound only. When filters are applied after Junk classification, notification are appeared but content is completely blank in the notification.

And latter case, click the notification mis-navigate to mail folder (Same problem as Bug 1728728)

This is still problem in 91.3.1.

If message filter moves new incoming messages to subfolder, icon badge and alert display are not working as expected.
This issue remains unresolved and affects Thunderbird 91, Beta 95, and Daily 96.
The result of this issue depends on when message filter works, that is, before or after junk classification.

I've tested several Thunderbird versions. The tests were done on two IMAP servers and one POP server.
Please see the attached image table.

I'm on TB 91.3.2, and it behaves differently from the table.

I have a couple of POP3 accounts with several providers. Junk classification is disabled everywhere, so I can only pick "before junk" when building filters. On all accounts, only the sound plays, no badges, no popups.

Thunderbird 78 was a single process. Since Thunderbird 91 is multi-process, it is possible that the message filter and the timing of notifying new messages are out of sync.
If so, it's understandable that delaying the timing of moving messages will change the outcome.
Is this my guess correct?

Unlikely. We are mostly multi-process compatible, but don't utilize it much yet.

I can't comment on wheter multi processing might be the issue here, but (as I wrote 2 month ago): mail seems to be moved away from the inbox faster than notifications are triggered.

Supporting this are two facts/possible conclusions:

1. Using a "copy to" filter instead of a "move to" filter solves the issue since it leaves mail in the inbox to be detected by the notification
2. Delayed moving by using an addon solves the issue too since this allows notifications to catch up

(In reply to micha.lohr from comment #10)

2. Delayed moving by using an addon solves the issue too since this allows notifications to catch up

I tried FiltaQuilla.
Simply installing FiltaQuilla does not change the results of previous tests.
After I add "Move Later" action and use it to create a filter rule, alerts don't popup in IMAP account.
And if message filter call "Move Later", sound, badge, and alert will work, but alert will be linked to inbox.

Same here, I probably wasn't clear enough.

You'll have to change your filters to "Move later". That will solve the notification issues (at least for POP, haven't tried IMAP). The popup will point to the inbox, and mail is moved away from there a second later, so clicking it will not find the mail.

(In reply to EarlgreyTea from comment #5)

..
I've tested several Thunderbird versions. The tests were done on two IMAP servers and one POP server.
Please see the attached image table.

EarlgreyTea, thanks for the great chart!

Multiprocess is definitely not related.

Someone may be able to find more duplicate bugs in this list https://mzl.la/3cJiXD0. Perhaps there is helpful info that can be copied to this bug.

Someone may be able to find more duplicate bugs in this list https://mzl.la/3cJiXD0

Two years after the report, it still doesn't work on my Thunderbird v102.10 on Windows 7.

Does it work for other configurations ? Or does Mozilla not want/can to solve this problem ?