Closed Bug 305303 Opened 19 years ago Closed 16 years ago

Junk mail controls don't fire on all IMAP folders by default

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: craig, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

I have an IMAP mail account which puts confirmed mail in the inbox folder and
likely spam in the PENDING folder. Thunderbird starts up automatically when I
boot my PC and defaults to the INBOX. This means that the very full PENDING
folder with mostly spam (but one or two good messages) doesn't have the Junk
Mail Controls run on it until I open that folder. Once I do, the PC then has to
download the entire new contents before the filters run. This takes ages (even
on broadband) and impacts on the amount of time it takes to find non-spam. 

I would much rather that I could specify the default folder to open when I start
Thunderbird, or that all folder with new mail in them have the junk mail filters
run on them automatically when the application is started.


Reproducible: Always

Steps to Reproduce:
1. Open pending folder
2. Wait ages for junk mail filters to process the folder 
3. Eventually, review the non-junk mail



Expected Results:  
Run the junk mail filters as soon as the app was opened, without waiting for me
to open the folder. Or for this folder to be the default and for it to open
automatically, causing the filters to run.
Which version of Thundberid is this bug reported against?

Are the messages in the IMAP folders being placed there by server-side filtering or by filters in Thunderbird?
Using Thunderbird 1.5.0.9

The messages in the IMAP inbox are being placed there by server side rules. The messages are there, but the filtering by Thunderbird doesn't take place because the default folder does not open.

The normal operation in 1.5 with client-side filtering is that the junk controls aren't run until the folder is opened; that's changed for TB 2.0: messages are filtered first, then immediately processed for junk (bug 329569).

I don't know if this works the same with server-side filtering, and I'm not in a position to test.  You could try a beta release or nigntly build of TB 2 to check it yourself, or wait for 2.0.  If the newer version behaves as described for server-side filtering, this bug should be duped to that other one.
QA Contact: general
David, is it architected to work this way (comment 0)? (Note, reporter might be gone.)
Assignee: mscott → nobody
thanks for the update, the reporter isn't gone though.
Craig Cockburn
craig@siliconglen.com
http://www.siliconglen.com/news
yes, it's architected to work this way. But you can specify that a folder should be checked for new messages when we check the inbox for new mail, though folder properties, and that should cause us to run the junk mail controls on the folder (not sure if that'll happen on startup though)
By setting "Check for new mail on Startup" and marking the folder with "Check this folder for new messages", you should get what you want.

Marking this as WFM.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.