Do Not Notify doesn't work with Thunderbird 78

[sebmiq]

Hi,
Thanks for the work on this addon.

The Do Not Notify feature doesn't seem to work with the latest beta version and thunderbird 78.

There's already an issue about this feature here : #8

[RealRaven2000]

Hi,
Thanks for the work on this addon.

The Do Not Notify feature doesn't seem to work with the latest beta version and thunderbird 78.

There's already an issue about this feature here : #8

It looks like the workaround for the moment is to combine it with the "Move Later" action. That's all I can say for now; I will try to find out how Thunderbird triggers that message internally so we can properly suppress it. Most likely this won't be allowed when we switch to "mail extensions" unless they create an API for that (move silently).

[sebmiq]

I had read about this workaround, but it doesn't work either.

It's such a great feature, I hope you can fix it.

[ocyzl]

Not sure if my problem is the same as this bug, but it's related to Do Not Notify, at least.

I don't want to be notified when junk mail arrives. So I set up a filter to do that. But then I don't either get notified about any non-junk messages that happen to arrive at the same time as a junk message.

I think this used to work right on Thunderbird 68. I'm on 78.10 now.

[RealRaven2000]

Not sure if my problem is the same as this bug, but it's related to Do Not Notify, at least.

I don't want to be notified when junk mail arrives. So I set up a filter to do that. But then I don't either get notified about any non-junk messages that happen to arrive at the same time as a junk message.

I think this used to work right on Thunderbird 68. I'm on 78.10 now.

It could be - the thing with the disabling of notifications is that it happens asynchronously and one filter doesn't know when the other has finished if it does stuff that way. This is only going to get worse with the conversion to pure mail extensions as API calls usually are executed asynchronously, which means the main thread will execute them whenever it has time. Not sure if it can be fixed as the notification itself may be asynchronous by design for performance reasons.

[kbauer]

For reference, the issue still exists with

115.4.3 (64-bit)

run on OpenSuse Leap 15.3.