633835 - Messages filters aren't started , sometimes yes and sometimes no !!!!!

Status: RESOLVED INCOMPLETE

(MailNews Core :: Filters, defect)

Description

[chris38]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.9.1.16) Gecko/20110107 Iceweasel/3.5.16 (like Firefox/3.5.16)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101213 Icedove/3.1.7 ThunderBrowse/3.3.4

I've one messages filters started, if the sender are in my personal adress book, then I tag message with 'tags perso' but each time that i start Icedove the filter isn't started, I need to start manually if I want to tag all messages, I tried the same settings with MIRAMAR ( Mozilla/5.0 (X11; Linux i686; rv:2.0b10pre) Gecko/20110114 Thunderbird/3.3a2) and I've the same results .
In the filter log I've nothing, what I mean : One clearly sees that the filter is not being asked.And right clic on e message, follow "TAG" there is nothing. 

Reproducible: Sometimes

Actual Results:  
No filters tag on the messages 

Expected Results:  
Applicated the filters

Comment 1

[chris38]

I'd like to precise that I use Gmail on three account, and I've this issues on these, then not tags do not works properly like that !!!

Comment 2

[chris38]

With mailer "Evolution" I don't have those problems.

Comment 3

[:aceman]

What about TB7/8? Do you have the filter set to run 'when checking mail and run manually' ?

Comment 4

[chris38]

As I written on my first mail : 
TB 3.0 ======== & ======== MIRAMAR ( Mozilla/5.0 (X11; Linux i686; rv:2.0b10pre) Gecko/20110114 Thunderbird/3.3a2)

Yes I do, I'm running : 'when checking mail and run manually'

Best Regards

Comment 5

[:aceman]

Yes, but are you able to upgrade to 7?

Comment 6

[chris38]

Yes I'm, I'm going to try with TB 8.0b3 & I'm coming back to tell something.Let me sometimes to do that ( 1 week or 2 weeks ).
Thx for your help

Comment 7

[:aceman]

What about TB9?

Comment 8

[Joshua Cranmer [:jcranmer]]

RESOLVED INCOMPLETE due to lack of response to previous comment. If you feel this change was made in error, please respond to this bug with your reasons why.