Open LittleAlf opened 1 year ago
Ultimately this is a Thunderbird bug. All Filter actions are executed by Thunderbird automatically. FiltaQuilla only adds new methods, but Thunderbird decides when these filters are supposed to run - if it decides it can run filters on emails where the body needs to be investigated, but it isn't fully downloaded at that stage, there is nothing the filter can do to recover from this.
I think the timing (especially for IMAP accounts) of filter execution on startup is buggy. If you check your filter log, it will show which filters are applied (that means their condition was met when the filter was run) - you could check the Javascript error console after startup whether you see any exceptions, then we would have something to work with...
Since several months now I have the following problem:
The FiltaQuilla conditions and actions at which the execution fails are:
It is definitely a problem related to the start of Thunderbird. Any other execution of the filters work. All these filters worked perfectly for months before. I do not know at which version of FiltaQuilla/Thunderbird the bag occurred the first time. My current versions are:
Any hint and help would be very much appreciated.