User-Agent: Build Identifier: Mozilla Thunderbird 0.4 (20031205) I have a setup on my IMAP server where messages in INBOX.Spam are automatically reported, and moved to INBOX.Spam.sent; when I move a junk message from INBOX to INBOX.Spam, weather marked automatically or manually, it remains marked as junk, but when the server moves it from INBOX.Spam to INBOX.Spam.sent thunderbird no longer shows those messages as marked as junk. Reproducible: Always Steps to Reproduce: see details Actual Results: see details Expected Results: I expected junk to stay junk
I believe I am experiencing the same issue, but it is under different circumstances. Let me know if this seems like a different issue and I will file a new bug. I have the bayesian Junk filter set up on a POP3 account to move junk to a folder on an IMAP account. After this move occurs, graphically, the junk indicator has returned to non-junk/unknown. When I run the Junk filter on said folder, it is still recognized as junk and the junk indicator reappears.
Note, I am using version 0.6 (20040506) compiled from source on a Gentoo linux system. However, the issue occurs with my Windows installation as well.
(In reply to comments #1 & 2: ) I expect that's a different issue; In my case, thunderbird is losing the junk mark when the server moves a message between folders - an action which thunderbird has no way to know about until it scans the folders again, - and in your case thunderbird is losing the junk mark when thunderbird itself moves a message between servers. They may be related, but that's beyond my knowledge.
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/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.