User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2 Building a filter on sentbox it doesn't work. Created a filter 'bout to move to a specificied sub-folder (ie Goofy_out) when I send a mail to goofy, the mail remains in the main folder ''sent''. (FYG all 200 inbox filters work perfectly).I nedda move it by hand. If i go to ''message filter'' the ''run selected filters on'' box is changed by default from ''sent'' to ''inbox''. Reproducible: Always Steps to Reproduce: 1. Create a filter rule into designed account (i.e. yhaoo.com) 2. Match any of the flw ''to''/contains (or is)/ email@example.com 3. Flagged: Move to folder..goofy_out on yahoo.com 4. Run selected filter(s) on: Sent 5. Applied ''run now'' button and.. 6. from tools menu applied also ''run filters on folder'' 7. Even sent an e-mail to firstname.lastname@example.org the msg remains into sentbox 8. Go to tool menu -> ''message filters'' and see the rule created. into the box ''Run selected filter(s) on:''.. Sent chnged into ''inbox'' Actual Results: The sent msg remains into yahoo.com sent folder. So I have to move with mouse to yahoo.com subfolder ''goofy_out''. Expected Results: Move the msg sent to the box defined as it does with all incoming msgs (if goofy send me an e-mail it goes directly into ''goofy_in''). ps. i bef yr pardon if it's too long but this is my first bug report.
is this imap or pop3? If IMAP, could you attach a protocol log? replace "protocol" with IMAP in the following instructions. http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap
No, David. It is a pop3 protocol. nedda still create a protocol log as per your linked instruction page ?
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Well, I tried with Thunderbird 107 an nothing changed. The 1.5beta1 release, instead, works quite good. I'd not the chance to test it for so much time to say that all rules are accepted but the way is traced.
This is an issue that I'm having, too. I would expect that the "Run selected filter(s) on:" dropdown would set whichever filter that you have selected to always run on that folder. However, it seems like that dropdown is only for the "Run Now" button, and is gets reset after the Filters dialog is closed. I have mail delivered to more than one IMAP mailbox (due to server-side spam filters). I would really like to be able to set message filters to automatically run on _any_ folder that I want...not just the Inbox.
If I undestand right it seems WFM here Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168pre) Gecko/20090729 Lightning/1.0pre Shredder/3.0b4pre ID:20090729051958 Could you try to see if it still happens with http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-1.9.1/ ?
Closing Incomplete for lack of answers. Feel free to reopen if you can provide more information.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.