479682 - Filters do not work on IMAP JUNK folder unless message is downloaded / synced in local message store

Status: RESOLVED DUPLICATE of bug 184490

(MailNews Core :: Filters, defect)

Description

[Niko Järvinen]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6
Build Identifier: 

I cannot get any filters working automatically on Junk folder. Most of them work when run manually. 
The biggest flaw is when I try to run filter which searches all mails containing X-Spam-Level field which starts with(or contains) ******* and then moving those to deleted. 

If I move any emails which match to that filter to inbox and run filters manually, it all works. If I run filters manually on Junk folder nothing happens. Tried with 2.0.0.19, TB3 beta 1 and TB shredder 21-Feb-2009 10:33 	7.8M. 

With TB3 beta 1 it works in Junk folder IF I select only one message and then "run filters for folder" and it acts correctly only on that one message. Does nothing to rest.

Reproducible: Always

Steps to Reproduce:
1. Make filter which should apply to mails which for example Spamassassin automatically moves to Junk folder on IMAP server.
2.After the filters hit none of the messages run the filters manually.
3. Now most of the filters should work correctly...
Actual Results:  
None of the incoming mails automatically get matched against filters. Most filters do work when run manually.

Expected Results:  
All mails should be matched against filters, and it shouldn't matter in which folder they are.

Comment 1

[Kent James (:rkent)]

I've read this several times, but I still can't figure out exactly what the steps to reproduce are. Just a few examples:

1) You jump from step 1 to 2, but don't say how any emails got received.
2) step 2 sounds more like an unexpected result than a step to reproduce
3) step 3 sounds like praise for a workaround rather than a step to reproduce.

I don't have the time right now to ask detailed questions to clarify this. Perhaps one of the triagers could work with the reporter to clarify this.

I suspect though that the issue is either associated with a well-known issue of custom headers, or misunderstanding about the conditions in which automatic filters are supposed to apply.

Comment 2

[Niko Järvinen]

Okay did some more testing now and tried with beta 2 too. 
Basically the problem is fixed if the message is downloaded before the filters are run. So either opening the message first or clicking the download for offline use button in folder settings. After that the filters work correctly. But otherwise the special header filter wont work. 

I hope this explanation is any better?

Comment 3

[Wayne Mery (:wsmwk)]

(In reply to comment #2)
> I hope this explanation is any better?

not for me.  You must have custom headers, as kent suggested.

the numbered steps should list your settings, and the actions you do to cause the bug. #2 and #3

Comment 4

[Wayne Mery (:wsmwk)]

needs more info.

Comment 5

[Ludovic Hirlimann [:Usul]]

(In reply to comment #4)
> needs more info.

Niko can you try to figure out if you have custom headers ? 
  It would help if you could save an email that had the issue and attach it here.
  Could you have a extension that plays with headers (look in the config editor for header and copy the results here)

Comment 6

[Niko Järvinen]

Yes, that's custom header set by SpamAssassin. Basically SpamAssasin puts it in all emails which are marked as spam.

Basically what I do is that I have all emails from my domain coming to single box. I have a filter which deletes emails which have the X-spam-level over x stars or to certain emails. If I open Junk folder normally and run the filter only the deletion by to email address takes place. If i click properties and download all emails and then run the filter also the deletion by x-spam-level gets done right...

Comment 7

[Kent James (:rkent)]

This is sounding more and more like bug 184490 and bug 363238.

Niko, what we are trying to figure out is if YOU have set a custom header in a filter. If you are filtering on X-Spam-Level then you probably did. There is a workaround for this, and I hope to get the workaround added automatically in bug 363238 before TB3 final.

Comment 8

[Niko Järvinen]

Yea it seems to be duplicate to those. And yes, I did set custom filter... No X-spam-level normally available...

Comment 9

[Wayne Mery (:wsmwk)]

(In reply to comment #8)
> Yea it seems to be duplicate to those. 

awesome. please dupe to whichever bug you feel is most appropriate