| Summary: | Messages mixed up after restoring an email from "Junk" folder in thunderbird-3.0 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Christophe <cjouny> |
| Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | mephinet |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Christophe
2010-01-04 18:06:55 UTC
3.0 is designed to move the message automatically from junk forlder minute is is marked as non junk. If this is an update from 2.0 thunderbird you will need to recreate the problem with a fresh profile. Let us know either way, I have not seen a problem at all, but is possible that the bug exists. If you would also check to ensure the message is correct on the providers server. Thanks for the idea - I went by the web interface and the message is fine on the server - which is good news for me. But this also would confirm the mixed up indexes in the thunderbird "database". Should there be (or is there) a way to force thunderbird to recheck emails on server and fix the local cache ? FYI on my account settings, Junk is set to be sent to a local trash folder. I tested marking a message Junk and then using the Not Junk button does not sent it back to the Inbox. It marks it as unread but stayed in the Junk folder. I am guessing the automatic move back only works if you keep the default settings of using the Junk folder on server (IMAP). I upgraded thunderbird to 3.0 so it is not a new profile. What version of dev-db/sqlite do you have installed, I noticed I did not update the dep to depend on 3.6.20 which is a mistake on my behalf. I have sqlite-3.6.20-r1 so unless it needs 3.6.21, it should be ok. Got a second incident. Same problem. Index got screwed up when dragging a "junk" email back to the inbox. However I found the "Rebuild Index" button on the Inbox folder properties and it fixed both error - restoring both emails. So not a critical error anymore. Still a bug. Can you still duplicate this with 3.1.1? 4+ months with no activity, reopen if new info is provided. |