User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050421 Firefox/1.0.4 Build Identifier: Thunderbird version 1.0+ (20050503) The training.dat file is not updating when a message is flaged as junk, as the 1.0.2 and 1.0.4 versions. It will only update durning the shutdown. If Thunderbird crashes, the lastest junk info is not safed, hence any updates are lost. Is the operation opposite to the release for a reason or a by-product of the trunk testing? Reproducible: Always Steps to Reproduce: 1. Flag email as junk 2. Training.dat updates after flag 3. Actual Results: The training.dat is not updating after flaging an email as junk. Expected Results: Once an email is flagged as junk, training.dat should be updated at flaged time. If email is being flaged as junk and if Thunderbird crashes, all the new junk data is lost.
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.