972807 - Mail filter rules are not always triggered since 24.3.0

Status: RESOLVED INCOMPLETE

(Thunderbird :: Filters, defect)

Description

[Walter van Holst]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:26.0) Gecko/20100101 Firefox/26.0 (Beta/Release)
Build ID: 20131205075310

Steps to reproduce:

I have an extensive set of mail filters to shift mails from mailinglists to designated folders


Actual results:

The filters no longer run autmatically when new mail is fetched and have to be invoked manually.


Expected results:

Filters should work automatically.

Comment 1

[WADA:World Anti-bad-Duping Agency]

Same problem as bug 931303?
If not same nor "pretty similar" , what is difference of your problem from that bug?
When did your problem start to occur? (after upgrade of Tb/add-on/OS/AV software, after hardware change, after some your actions, after specific day, and so on.)
IMAP? POP3?

Comment 2

[WADA:World Anti-bad-Duping Agency]

Bug summary is following.
> Mail filter rules are not always triggered since 24.3.0

"Upgrade to 4.3.0" from which version of Tb?

Comment #0 sounds "no mail is moved by filter in your environment". But bug summary sounds "some mails are successfully mved by filter".
Which?

Comment 3

[Walter van Holst]

It sometimes is, it sometimes isn't. Sometimes the filters get triggered automatically, sometimes even manual invocation doesn't work.

Comment 4

[Walter van Holst]

(In reply to WADA from comment #1)
> Same problem as bug 931303?
> If not same nor "pretty similar" , what is difference of your problem from
> that bug?
> When did your problem start to occur? (after upgrade of Tb/add-on/OS/AV
> software, after hardware change, after some your actions, after specific
> day, and so on.)
> IMAP? POP3?

Originally POP3, have changed the setup to IMAP now (including moving tying all the filters to the IMAP account and disabling the local folder filters), but doesn't change a thing.

As already reported: it was after upgrade to Tb, no changes to add-ons, OS/AV, hardware etc. JUST TB GOT UPGRADED AS REPORTED.

Zero similarities to Bug 931303 because I don't get an error message. Just that it fails to do what it used to do. UNTIL THE TB UPGRADE.

Comment 5

[WADA:World Anti-bad-Duping Agency]

(In reply to Walter van Holst from comment #4)
> Just that it fails to do what it used to do. UNTIL THE TB UPGRADE.

What phenomenon do you call by "Just that it fails to do what it used to do" in your responce and/or "Mail filter rules are not always triggered" in your bug summary?
(a) Message filter log says "filter was applied and mail was moved to move target folder" but the mail is not moved from Inbox to the move target folder.
(b) Message filter log was not written for the non-moved mails, and the mail was not moved from Inbox to the move target folder.
(c) Other than (a)/(b).

Comment 6

[Walter van Holst]

(In reply to Walter van Holst from comment #4)
> (In reply to WADA from comment #1)
> > Same problem as bug 931303?
> > If not same nor "pretty similar" , what is difference of your problem from
> > that bug?
> > When did your problem start to occur? (after upgrade of Tb/add-on/OS/AV
> > software, after hardware change, after some your actions, after specific
> > day, and so on.)
> > IMAP? POP3?
> 
> Originally POP3, have changed the setup to IMAP now (including moving tying
> all the filters to the IMAP account and disabling the local folder filters),
> but doesn't change a thing.
> 
> As already reported: it was after upgrade to Tb, no changes to add-ons,
> OS/AV, hardware etc. JUST TB GOT UPGRADED AS REPORTED.
> 
> Zero similarities to Bug 931303 because I don't get an error message. Just
> that it fails to do what it used to do. UNTIL THE TB UPGRADE.

Correction after wading through all the messages on that Bug: it is pretty similar in that it fails silently. It still is completely random. And frankly, I find it rather insulting to your users if you get so many people with very similar problems that you call such a bug 'unconfirmed'.

Comment 7

[Walter van Holst]

(In reply to Walter van Holst from comment #6)
> (In reply to Walter van Holst from comment #4)
> > (In reply to WADA from comment #1)
> > > Same problem as bug 931303?
> > > If not same nor "pretty similar" , what is difference of your problem from
> > > that bug?
> > > When did your problem start to occur? (after upgrade of Tb/add-on/OS/AV
> > > software, after hardware change, after some your actions, after specific
> > > day, and so on.)
> > > IMAP? POP3?
> > 
> > Originally POP3, have changed the setup to IMAP now (including moving tying
> > all the filters to the IMAP account and disabling the local folder filters),
> > but doesn't change a thing.
> > 
> > As already reported: it was after upgrade to Tb, no changes to add-ons,
> > OS/AV, hardware etc. JUST TB GOT UPGRADED AS REPORTED.
> > 
> > Zero similarities to Bug 931303 because I don't get an error message. Just
> > that it fails to do what it used to do. UNTIL THE TB UPGRADE.
> 
> Correction after wading through all the messages on that Bug: it is pretty
> similar in that it fails silently. It still is completely random. And
> frankly, I find it rather insulting to your users if you get so many people
> with very similar problems that you call such a bug 'unconfirmed'.

(In reply to WADA from comment #5)
> (In reply to Walter van Holst from comment #4)
> > Just that it fails to do what it used to do. UNTIL THE TB UPGRADE.
> 
> What phenomenon do you call by "Just that it fails to do what it used to do"
> in your responce and/or "Mail filter rules are not always triggered" in your
> bug summary?
> (a) Message filter log says "filter was applied and mail was moved to move
> target folder" but the mail is not moved from Inbox to the move target
> folder.
> (b) Message filter log was not written for the non-moved mails, and the mail
> was not moved from Inbox to the move target folder.
> (c) Other than (a)/(b).

Option b.

Comment 8

[WADA:World Anti-bad-Duping Agency]

(In reply to Walter van Holst from comment #7)
> (In reply to WADA from comment #5)
> > (In reply to Walter van Holst from comment #4)
> > > Just that it fails to do what it used to do. UNTIL THE TB UPGRADE.
> > 
> > What phenomenon do you call by "Just that it fails to do what it used to do"
> > in your responce and/or "Mail filter rules are not always triggered" in your
> > bug summary?
> > (a) Message filter log says "filter was applied and mail was moved to move
> > target folder" but the mail is not moved from Inbox to the move target
> > folder.
> > (b) Message filter log was not written for the non-moved mails, and the mail
> > was not moved from Inbox to the move target folder.
> > (c) Other than (a)/(b).
> 
> Option b.

If so, your problem is never "a messega filter rule is matched with a mail, then T tried to move the message to move target folder, but Tb failed to move the mail to move target folder", because Tb's action is "write filter log first if a rule is matched, then try to move the mail according to move request of the matched filter rule".
Your problem is "some messeae rules doesn't fire on some mails as you expect", and it's after (a) upgrade of Tb and (b) change from POP3 to IMAP.

Problem due to (b) istead of (a), isn't it?
Do you use "Body ..." in your message filter rule?
If "customized header" is used in your message filter rule, does your problem occur, on (i) new message detection and message filtering", and/or on (ii) manual "Run filter on Folder after new mail check/fetch"?

Can you attach mail data to this bug(never paste, please), which was not moved by one or several message filter rule as you expect, and the message filter rule(s) which should br applied to the mail?
(message filter rule is saved in messageFilterRules.dat file in Tb's mail directory for each account/server).

Comment 9

[Wayne Mery (:wsmwk)]

Hi Walter.
We still need more information from you ...

(In reply to WADA from comment #8)
> (In reply to Walter van Holst from comment #7)
> > (In reply to WADA from comment #5)
> > > (In reply to Walter van Holst from comment #4)
> > > > Just that it fails to do what it used to do. UNTIL THE TB UPGRADE.
> > > 
> > > What phenomenon do you call by "Just that it fails to do what it used to do"
> > > in your responce and/or "Mail filter rules are not always triggered" in your
> > > bug summary?
> > > (a) Message filter log says "filter was applied and mail was moved to move
> > > target folder" but the mail is not moved from Inbox to the move target
> > > folder.
> > > (b) Message filter log was not written for the non-moved mails, and the mail
> > > was not moved from Inbox to the move target folder.
> > > (c) Other than (a)/(b).
> > 
> > Option b.
> 
> If so, your problem is never "a messega filter rule is matched with a mail,
> then T tried to move the message to move target folder, but Tb failed to
> move the mail to move target folder", because Tb's action is "write filter
> log first if a rule is matched, then try to move the mail according to move
> request of the matched filter rule".
> Your problem is "some messeae rules doesn't fire on some mails as you
> expect", and it's after (a) upgrade of Tb and (b) change from POP3 to IMAP.
> 
> Problem due to (b) istead of (a), isn't it?
> Do you use "Body ..." in your message filter rule?
> If "customized header" is used in your message filter rule, does your
> problem occur, on (i) new message detection and message filtering", and/or
> on (ii) manual "Run filter on Folder after new mail check/fetch"?
> 
> Can you attach mail data to this bug(never paste, please), which was not
> moved by one or several message filter rule as you expect, and the message
> filter rule(s) which should br applied to the mail?
> (message filter rule is saved in messageFilterRules.dat file in Tb's mail
> directory for each account/server).