Closed Bug 383598 Opened 18 years ago Closed 15 years ago

new messages in subfolder not indicated by making the subfolder name bold (POP filters)

Categories

(Thunderbird :: Mail Window Front End, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: somol, Unassigned)

References

Details

(Whiteboard: fixed by bug 469448?)

Attachments

(3 files)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; cs; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4 Build Identifier: verze 2.0.0.0 (20070326) occassionally, about once in 14 days (I use Thunderbird daily and very often) new mail is stored to subfolders according to my rules, but the subfolder is not displayed in bold, thus I have no clue of the existence of new mail. Only if I click the subfolder name, it tells that some kind of re-organization must take place (and some process really is indicated by fast display of progress-bar in the bottom) and then everything becomes visible correctly, i.e., new mail in bold including the subfolder name. Reproducible: Sometimes Steps to Reproduce: 1. unfortunately, I can not see any way of direct reproduction of the effect apart from using Thunderbird frequently enough and receiving lots of mail, preferably with large attachments 2. 3. I have installed: Auto Zip attachments for Thunderbird 0.5.4 Confirm Folder Move 1.0 SmoothWheel 0.44.7.20050605 Talkback 2.0.0.0 no themes
see also bug 312610, bug 420260. I can confirm this behaviour on WinXP SP2, T'Bird 2.0.0.14 (20080421)
I can confirm this behaviour on win xp2 and win xp3 TB version 2.0.0.16 (20080708)and IMAP folders. Reproducible all the time. This is critical.
are these client-side rules/filters? And this only happens rarely?
"I can confirm this behaviour on win xp2 and win xp3 TB version 2.0.0.16 (20080708)and IMAP folders. Reproducible all the time. This is critical." These are client side filters on and we are using imap servers. As said this is reproducible 100% of the time.
This happens frequently and if it only happened once it would be unacceptable. This is a fatal program flaw, reason to abandon the program. You cannot lose incoming email in a folder-filter structure. If you won't follow Eudora's strategy of opening incoming mail in its folders, then the bolding or whatever strategy you have for identifying folders with unread mail (also newly arrived mail) needs to work perfectly every time.
along with bug 420260
current client, 2.0.0.16 (20080708) pop servers This just happened to me again, and yes, it is a show-stopper. Some of these messages that I have missed seeing are two weeks old and are SALES OPPORTUNITIES representing possible $$thousands. I think the act of compacting folders may have something to do with preventing the boldface updating (just a guess).
Let me be more specific: I'm pretty sure I compacted all folders a few weeks ago, before I took a week's vacation. Now I am back and taking a look at some folders for the first time since the compaction. There is a delay while the summary file is built -- and then, ta-da! a bunch of old messages and 41 new ones, boldfaced, and the folder name is also boldfaced. But not until the summary file is built. So I might suggest that the action of filtering a message into a folder is not properly refreshing the summary file?? Please fix this!!! thanks.
I am facing this problem quite often. I am filtering messages coming into Inbox and they go into different subfolders. WHen I click on subfolder, the cursor changes and then nothing is displayed. Sometimes, it says"Building Summary file" and the messages are displayed after sometime. But most of the times, nothing is displayed in the folder. THis has become very painful for me since I am unable to work now. Pl fix it immediately
Will someone please change this status to CONFIRMED and FIX THE BUG?!? It just happened again, and in the same way. 1. Create filters to sort new messages into folders other than Inbox. 2. Compact folders. 3. Wait for some period of time while new messages arrive. 4. Sit in blissful ignorance of IMPORTANT MESSAGES because the folders are not highlighted in bold. 5. Just by chance, open one of the folders. 6. Wait for summary file to be built. 7. Discover you've once again MISSED A SALES OPPORTUNITY because NEW MESSAGES WERE NOT HIGHLIGHTED. WILL SOMEONE PLEASE FIX THIS BUG!!!!!!!!!!!!!! TBird 2.0.0.22 (20090605) on WinXP Pro SP 2
I can confirm this problem with Windows Vista as well. The filtered messages go into different folders and no idea of which folder has new messages till I click on that folder & then summary is built. But sometimes it does not build summary also and no messages are displayed in that folder. I need to get out of Eudora, come in again, work on Inbox some time and then click that folder to get the summary built. It has been very difficult to use Eudora because of these issues since I use it very often. Will SOMEONE PL FIX THESE ISSUES OR SUGGEST ANY WORKAROUNDS !!
When the server does the filtering, the respective folders show up in Thunderbird, but local filters do not register. Is there a way that TB filters were invoked earlier, or maybe an option to export the filters so that they could easily be applied server side on a user basis. I'm not a programmer so I don't know if this is possible to even desirable in the big scheme of things - but I can confirm that all works well when it is server controlled.
Questions for all the shouting commenters: 1. What account type are the messages being retrieved from (RSS, IMAP, POP, Movemail)? 2. Are these messages being moved by server or client side filters? 3. What account type are the messages being sent to? Is it the same account?
(In reply to comment #13) > 1. What account type are the messages being retrieved from POP3 > 2. Are these messages being moved by server or client side filters? Client (Thunderbird's) > 3. What account type are the messages being sent to? Is it the same account? Same account. "Local Folders" in my case. I believe that Stuart has pinpointed the problem. It happens when I select a mailbox in the folder pane and do "File > Compact Folders". If I don't expand every level of the mailboxes and click on every mailbox (yes it is tedious) then it's fairly certain that newly received, filtered mail will not highlight its containing mailbox. TB3.0b2 / WinXP sp3 In addition to this bug, Shredder introduced a new layer to this problem. It often doesn't repaint the folder pane (newly highlighted mailboxes) until I force it to (e.g. by moving my mouse over the mailboxes or alt-tabbing away from and back to Thunderbird). Bug 483027.
(In reply to comment #13) Thank you for hearing our shouts! 1. What account type are the messages being retrieved from (RSS, IMAP, POP, Movemail)? POP3 2. Are these messages being moved by server or client side filters? Client (Thunderbird 2.0.0.22 and previous versions at least to .14 as in my comment #2) 3. What account type are the messages being sent to? Is it the same account? You mean "sent" as in being filtered/moved to? Same account (not Local Folders; not sure what the other category is called). Win XP SP2
Since there are already a few bugs on IMAP filters not marking new messages as read, I'll make this about the POP filters. In attempting to reproduce this myself, I failed to be able to setup the necessary circumstances. Some more fine-tooth questions: 4. Are the filters via the POP account or the target account, if different? E.g., if your POP account is named "Crap email", would the filters be under "Crap email" or a different label, like "Local Folders"? 5. What were the criteria and the actions of the filter? I don't think the criteria is all that important, but the more specific the steps, all the better. 6. How nested are the subfolders in question? 7. Does the problem only happen upon the automatic mail downloads at startup or the timers, or does it happen if you manually download it? 8. Do you have to restart between the compaction and receiving the message? Which folders have to be compacted to get the message to disappear, the subfolder, its parent folder, or both? I had another, but it escapes me right now...
Summary: new messages in subfolder not indicated by making the subfolder name bold → new messages in subfolder not indicated by making the subfolder name bold (POP filters)
> 4. if your POP account is named "**** email", would the filters be under > "**** email" or a different label, like "Local Folders"? POP account = "FastMail"; Filters = "Local Folders" > 5. What were the criteria and the actions of the filter? "If From is <emailAddress>", "Move to their mailbox" > 6. How nested are the subfolders in question? e.g. "Local Folders > Companies > Mozilla" > 7. Does the problem only happen upon the automatic mail downloads Definitely during automatic downloads, not sure about manual because I rarely do that. > 8. Do you have to restart between the compaction and receiving the message? As far as I can tell, restarting doesn't matter, the problem seems to be that the summary files are not being properly or completely rebuilt after compaction. Somehow manually clicking on each mailbox/folder after compaction does something that the "File > Compact Folders" does not do. > Which folders have to be compacted to get the message to disappear, the > subfolder, its parent folder, or both? I never compact individual mailboxes or folders. It's always by manually compacting everything in Local Folders via "File > Compact Folders". In "Tools > Options > Advanced > Network & Disk Space", "Compact Folder When It Will Save Over" is unchecked and the value is 1 KB. I manually run compaction like that once per week. I don't know if it's related but sometimes it doesn't compact some mailboxes even though they have well over 1 KB of space to compact.
(In reply to comment #16) > 4. Are the filters via the POP account or the target account, if different? > E.g., if your POP account is named "**** email", would the filters be under > "**** email" or a different label, like "Local Folders"? > > 5. What were the criteria and the actions of the filter? I don't think the > criteria is all that important, but the more specific the steps, all the > better. > > 6. How nested are the subfolders in question? 4,5,6: see attached screenshots. > > 7. Does the problem only happen upon the automatic mail downloads at startup or > the timers, or does it happen if you manually download it? > I would say probably all three, since I have very likely closed and reopened TBird, and issued Ctrl+t Get Mail commands, and had my timer download messages more than once in the several days between compacting folders and discovering the hidden messages. > 8. Do you have to restart between the compaction and receiving the message? > Which folders have to be compacted to get the message to disappear, the > subfolder, its parent folder, or both? Before compacting, I select my pop account name at the top of the Folders pane, then use File > Compact Folders. I seldom compact individual folders.
(In reply to comment #16) > 4. Are the filters via the POP account or the target account, if different? > E.g., if your POP account is named "**** email", would the filters be under > "**** email" or a different label, like "Local Folders"? > > 5. What were the criteria and the actions of the filter? I don't think the > criteria is all that important, but the more specific the steps, all the > better. > > 6. How nested are the subfolders in question? 4,5,6: see attached screenshots. > > 7. Does the problem only happen upon the automatic mail downloads at startup or > the timers, or does it happen if you manually download it? > I would say probably all three, since I have very likely closed and reopened TBird, and issued Ctrl+t Get Mail commands, and had my timer download messages more than once in the several days between compacting folders and discovering the hidden messages. > 8. Do you have to restart between the compaction and receiving the message? > Which folders have to be compacted to get the message to disappear, the > subfolder, its parent folder, or both? Before compacting, I select my pop account name at the top of the Folders pane, then use File > Compact Folders. I seldom compact individual folders. I can't remember if I rebooted the PC, but I did very likely close and reopen TBird, as I try not to leave it running when I'm not at my desk.
Totally rigid that this developer group won't simply solve the problem by opening folders that receive mail. They've never offered a reasonable explanation for why they won't do that except that they won't. On the other hand, I can report that my problem which drove me to distraction and a search for another email client (which continues unsuccessfully) seems to have gone away. However, I rarely compact my folders. So possibly that's why. The problem is, if you don't open the folder immediately that receive mail, and folder with new mail or folders with still unread mail in them aren't bolded, YOU DON'T KNOW YOU HAVE NEW OR UNREAD MAIL IN THEM. It's only by accident sometimes months later that you discover that someone wanted to communicate with you - possibly an important personal or business someone - and all they know is that you didn't respond. FATAL. So I'm glad Cramner is actually putting some brain time into this issue but I'd say pretty late in the game for we "shouters" who had every right to be a lot more than just annoyed. It is simply unacceptable for an email program to lose incoming email. Email first grade stuff. My problem as far as I know has gone away. I have no idea why. But then again, maybe it hasn't. With at least 500 maybe double that number of folders, I'm clearly not going to open every folder to find out which one's indexes have been destroyed by something Thunderbird did. Popmail from several servers, multiple accounts, problem occurred earlier irrespective of account. I want to start a new "bug" that really isn't a bug. it makes no sense to list unread and recently received email folders alphabetically in a complex folder system spanning multiple accounts. None. The listings should in some manner follow the structure of the established folder system. Is there a bug or developer discussion group around this issue?
I was unfortunately unable to confirm this bug locally, so I'm now diving into the code to see what's going on. My best guess at this point is that the problem is related to database corruption, which I tend to have the misfortune (from a QA perspective) of not seeing. The code seems to allow a few possible points of failure: nsIMsgDatabase::CopyHdrFromExistingHdr The header having a junkscore of 50 or more (i.e., it's Junk) nsIMsgDatabase::AddToNewList nsIMsgDBFolder::SetHasNewMessages nsIMsgDatabase::UpdateDBFolderInfo I don't have time to examine these all in depth right now, but option #2 should be easy to rule out: if the filter that's causing the losing emails has the criteria [Set Junk Status to] [Not Junk] *before* the move one. There also seems to be a UI junkscore hole of 50 (the backend sometimes considers 50 to be junk and not junk); this could be verified by inspection of the msf files. The other methods are all of the non-trivial methods that are called after the message itself is copied to the folder database until the end of the move method.
Not to compound the situation, but this occurs on IMAP accounts as well, although I think I have isolated the cause. It occurs on an alias email that placed in a main email account by my isp. It is fetched from the POP server by fetchmail, procmail then filters it based on the original alias email address and places it into the IMAP sub folder. It is not being filtered by Thunderbird. Mail that is being filtered by Thunderbird register correctly on the computer on which the mail is first downloaded. This is fine, if all filters have been kept in sync. -- Not a seemless job in TB at this time. Unfortunately, it is so much easier to filter it using procmail, as I only have to set it up once instead of having to try to keep my four computers in sync.
While I appreciate very much that some of the knowledgeable developers have spent some time with this, it doesn't make sense to me that the problem is with POP/IMAP or filters or downloading. If I never use "File > Compact Folders" then there is no problem at all. Thus I believe that this bug is specifically about that menu command (or perhaps with compaction in general). It's either breaking something about mailboxes/.msf files or not doing everything it should with them. The mailboxes are magically fixed when we manually click on them, so why can't they be "fixed" during compaction instead?
> If I never use "File > Compact Folders" then there is no problem at all. Also, the problem is fixed by clicking on every mailbox after compaction but before downloading any new mail so that's why I think the problem is with compaction rather than with downloading.
(In reply to comment #22) > Not to compound the situation, but this occurs on IMAP accounts as well, > although I think I have isolated the cause. It occurs on an alias email that > placed in a main email account by my isp. It is fetched from the POP server by > fetchmail, procmail then filters it based on the original alias email address > and places it into the IMAP sub folder. It is not being filtered by > Thunderbird. That would be a separate issue from POP filter code; please search for IMAP filters. (In reply to comment #23) > While I appreciate very much that some of the knowledgeable developers have > spent some time with this, it doesn't make sense to me that the problem is with > POP/IMAP or filters or downloading. The problem is almost definitely at its core a database corruption issue, one that is caused by the compaction, that prevents new message alerts, and that is fixed by database rebuilding. Since I'm apparently being sufficiently unimaginative about the style of database corruption going on, I would like to request some more information for debugging purposes: Could those seeing this problem send me a copy of the msf file of the folder in question at two points, one immediately after compaction and one after opening the folder after compaction. They can be found (for windows users) at C:\Documents and Settings\<username>\Application Data\Thunderbird\Profiles\<should be only one folder here>\Mail\<account name>\<more path>\<foldername>.msf, e.g.: C:\Documents and Settings\jcranmer\Application Data\Thunderbird\Profiles\201w0zr4.default\Mail\Local Folders\Mailing Lists.sbd\IMAP.msf
Attached file 02 After clicking on the mailbox (deleted) —
I've attached two .msf files as requested. I used my Bugzilla mailbox for the test. It currently contains only one message. Hope it helps! Using TB3.0b2 on WinXP.
Thunderbird version 2.0.0.22 (20090605) I have just gone through all my accounts and folders, deleted loads of emails, then emptied the deleted folders then compacted each folder. 2 days later (ie today) I happen to be looking at all the folders and can see no new mail though I did get a new mail notification. I looked at each account and one of the accounts has a golden orange star next to it, and then clicking on the sub folder it suddenly goes bold with (2) next to it. Why did it not go bold with the (2) when the mail came in and got routed. It is POP mail.
Because a catastrophic flaw for an email program, one which has existed now for at least three years, doesn't rate the all hands on deck fix=it priority it should with a Mozilla Thunderbird development team whose collective head is somewhere else. I recently contributed a comment here that said my problem had gone away. Wrong. Showed up again recently, with the predictably devastating consequences when an important note from a business colleague was not identified as having been received. This is open source software. You can complain until you're blue in the face but these guys are not going to devote the resources to fixing the problem ...... because they really do not understand, won't admit that this kind of problem makes it a risk to use this program as a communication tool in any relationship that matters. Incredible to me that this wasn't fixed not weeks ago, not months ago, but years ago.
(In reply to comment #29) > You can > complain until you're blue in the face but these guys are not going to devote > the resources to fixing the problem ... I hope that you learned a lesson from that, that complaining until you are blue in the face to get a problem fixed is not the path to improving open source software. What DOES help is to write a simple, clear, reproducible set of steps to demonstrate the problem. There are 3-4 people who might be able to solve this issue, and all but one are volunteers like you. I'm one of them (as is Joshua), and currently in the middle of a patch (bug 127250) to imap filters that indirectly addresses similar problems. I'm also planning to work soon on bug 495666 which deals with db issues during compaction, which could very well be the root cause of this bug. But I'm not sure that this bug has a set of STR that I can rely on yet. Comment 10 is close, but I'm still seeing "by chance" there. (I'll admit though that I have not tried these steps yet. Jcranmer, if these steps work for you please confirm this bug. Comment 21 though says that you cannot.) This bug has come a long way from the original report, which was an error that happens about every 14 days (which is the worse kind, impossible to fix but too serious to ignore.) Let's get a clear STR so that we can get this solved.
(In reply to comment #30) > What DOES help is to write a simple, clear, reproducible set of steps to > demonstrate the problem. There are 3-4 people who might be able to solve this > issue, and all but one are volunteers like you. I'm one of them (as is Joshua), > and currently in the middle of a patch (bug 127250) to imap filters that > indirectly addresses similar problems. I'm also planning to work soon on bug > 495666 which deals with db issues during compaction, which could very well be > the root cause of this bug. I've been generally operating under the assumption that the DB is corrupt somehow, yet the msfs provided do not lead to that assertion: the only changes are LastPurgeTime and MRUTime. > But I'm not sure that this bug has a set of STR that I can rely on yet. Comment > 10 is close, but I'm still seeing "by chance" there. (I'll admit though that I > have not tried these steps yet. Jcranmer, if these steps work for you please > confirm this bug. Comment 21 though says that you cannot.) These steps alone failed to reproduce for me, but I'm now suspecting that we're getting invalid databases after compaction. I think we would return the data from the folder cache while somehow the DB folder info just vanishes into thin air. *pause* Wait, folders don't add themselves as listeners on invalid DB in TB 2, do they? I'm going to tentatively suggest that a key part of the STR is to ensure that the DB is invalid--touch should help here.
(In reply to comment #31) > I'm going to tentatively suggest that a key part of the STR is to ensure that > the DB is invalid--touch should help here. Well, what do you know? I compacted the folder, touch'd the time on the mbox to January 1, sent the mail to myself, filtered it... and the UI did not indicate the existence. I verified this with TB 2, and the code in TB 3 looks like it may fix this problem, either by changeset 1859 (bug 469948) or changeset 1697 (bug 471130). Complete STR: 1. Compact a local folder [may not be necessary]. 2. Change the timestamp of the mbox to some time that is not near now (a few months is safe). 3. Send a message to yourself, and have it moved via a filter to the folder. You don't have to wait for biff to fire, it happens on manual get. 4. Observer that the folder does not indicate a new message.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: x86 → All
Version: unspecified → 2.0
(In reply to comment #32) > [...] the code in TB 3 looks like it > may fix this problem, either by changeset 1859 (bug 469948) or changeset 1697 > (bug 471130). FWIW, I had the problem with TB 2. I'm not sure if it exists in TB 3 because I stopped using "File > Compact Folders" while still using TB 2 and haven't dared to try it since I've been using the TB 3 betas. I'll restart using "File > Compact Folders" every few days and report if the problem remains for me with the TB 3 betas.
Bug 471682 was routinely causing the database to become "corrupt" (actually just had the wrong date), so in TB2 it would be quite common to see out-of-date local databases for people using any functionality that involved moving messages to a local folder. So if this bug is somehow connected with reparsing a corrupt local database, then it would be much more prevalent in TB2 than TB3.
I have no idea what is producing or reproducing this problem, which just today left me with a broken or at least damaged business relationship because I didn't see an incoming message until after a deadline. Typically, you only discover the lost incoming email problem has occurred way later in the game when you discover the new email in an unbolded folder, typically by accident. You have no idea when or why the folder wasn't bolded until you look at the date stamp on the email. Moreover, it is not invariably the case from what I can tell that it's an index problem. Sometimes, the folder appears immediately without any obvious rebuilding. But maybe it's a fast rebuild. Who knows. I don't compact folders knowingly, unless I've got some switch set that I'm not aware of. Frankly, if I didn't complain until I was blue in the face, I'd pursue legal remedies for the damages this has caused. Just because Thunderbird is free doesn't mean its developers are immune from some kind of redress for obvious tort. Putting a product in the public sphere that has such a lethal flaw isn't free to the person suffering the consequences. We're talking years that this problem has been ignored. Years, not weeks or months. So kindly stop lecturing me about open source etiquette and fix the problem. Obviously, if I had the slightest clue what was going on I'd share it with you. I have no idea. I don't write code. I send and receive emails. I'm a user.
(In reply to comment #32) > Well, what do you know? I compacted the folder, touch'd the time on the mbox to > January 1, sent the mail to myself, filtered it... and the UI did not indicate > the existence. I verified this with TB 2, and the code in TB 3 looks like it > may fix this problem, either by changeset 1859 (bug 469948) or changeset 1697 > (bug 471130). Joshua, thank you for your continuing efforts to solve this problem. Your comments about the timestamp tweaked my memory about a possibly related circumstance: I have noticed that sometimes when rebuilding a summary file for a subfolder containing saved messages, TB will boldface several messages that are NOT new -- they are months or even years old. I can't give you STR this, but offer it only as a possible clue to help solve the current riddle. Do you still need more examples of pre-compact post-compact .msf files?
(In reply to comment #35 and comment #29) > I have no idea what is producing or reproducing this problem, which just today > left me with a broken or at least damaged business relationship because I > didn't see an incoming message until after a deadline. ... Frankly, if I didn't complain until I was blue in the face, I'd > pursue legal remedies for the damages this has caused. I think it has been established that the problem exists and that several people are trying to solve it. It has already been pointed out to you that yelling at a group of volunteers is not the best way to encourage co-operative responsiveness. Threatening lawsuits à la Stella Liebeck is likely also to be ineffectual if not counterproductive. You claim in comment #29 to have "contributed," but in fact, your last two postings add nothing useful whatever; you're now just repeating your previous complaints in a petulant rant. The rest of us who are also suffering the same serious consequences of the bug are trying to assist the developers by adding information, not noise. Your impatient and discourteous remarks cannot be helpful; probably quite the contrary. For everyone's benefit (including your own), please stop.
This problems was ignored for years not months or weeks. Nobody's going to sue anybody if there's a concerted effort to fix the problem. Keep calling being fed up with years of indifference to a serious flaw a "rant," though, and I'll think differently about it, especially because I think Mozilla dropping Thunderbird borders on malfeasance. Does open source mean some kind of slavish silence to "volunteerism." I've been in these discussion since the problem first occurred years ago and I have told you everything I knew for that amount of time. The unbolded folders (with unread, sometimes new, sometimes not so new emails in them ...... because you didn't know the unread email was buried in the unbolded folder) happen with or without compacting and don't abide by any logic that I can discern, largely because the problem is not apparent until you discover the email, by accident, when you find it. That could be the next hour, next day, next week, next month - or not until months later. You've never know exactly what was happening when it happened. I've also found unread emails bolded out of the blue for no reason I could discern. Typically, people start talking about some kind of redress of a grievance when they don't think they've been heard. How long have you been complaining about this problem? For me, it's a couple of years. I'm fed up. Fix the problem. Keep calling me names for complaining or threatening or whatever gets someone's attention and I'll take it from there. Stop lecturing me or I'll act on what was only a device to get the Mozilla developer group's attention.
A little follow up from myself. Thunderbird version 2.0.0.22 (20090605) had been running all night, this morning I looked through and view mail in the bolded folders however once all bolded folders had reverted back to a non bolded state I notice that 2 accounts (A normal pop account and a Gmail pop account) had the yellow sun icon next to the account name but no folders were bolded. I looked and make a copy of the files in the C:\Users\Sean\AppData\Roaming\Thunderbird\Profiles\r3tc0r65.default\Mail\ Account name then proceeded to click through the folder names under this account until I found a folder with 2 unread newly delivered mail and once clicking on this folder it went bold. I checked the files again but there was no difference between doing these two steps. However I did notice that in the mail folder there was numerous folders which had duplicate sets of data in including files of folders that should of been deleted a few weeks ago when I went through and did a clear out, so what are these accounts/data still there? Maybe this is currption
(In reply to comment #33) > FWIW, I had the problem with TB 2. I'm not sure if it exists in TB 3 I started using "File > Compact Folders" again starting with TB3.0b2 and then with TB3.0b3. I've been running this command every three days for the last three weeks and have not seen this bug at all. In TB2.x the problem was consistent and reproducible, but not any more. I'm glad to say that I think this bug has been fixed, at least on my computer. However, I still see bug 483027, which can also cause one to not be aware of new mail. To alleviate this I've created a Saved Search mailbox called Unread that allows me to quickly find new mail without having to scroll through all my folders.
This problem may have been caused, among other things, by a "compact folders" problem. But in TB2, at least, I never compacted folders by command - not sure if a shut down automatically compacted them - and the problem is still occurring in TB2, as recently as 2 days ago. And only on some folders, not all. Naturally, it occurred on the folder with the most critical email in it, an ongoing important business relationship. Whether TB3 will have solved the problem when it's released, I'll find out when it's released.
(In reply to comment #40) > (In reply to comment #33) > > FWIW, I had the problem with TB 2. I'm not sure if it exists in TB 3 > > I started using "File > Compact Folders" again starting with TB3.0b2 and then > with TB3.0b3. I've been running this command every three days for the last > three weeks and have not seen this bug at all. In TB2.x the problem was > consistent and reproducible, but not any more. I'm glad to say that I think > this bug has been fixed, at least on my computer. I'd like to think that it was bug 469448 that fixed this issue by proxy, but I am currently unable to confirm. In any case, there is ample evidence that the problem fails to exist in TB 3. Unless anyone can contradict that, it is then WFM.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Whiteboard: fixed by bug 469448?
TB3 is not a released product. If you read my comments above, I do not compact my folders knowingly and I still have the problem (I just checked both Account Settings and Options and can't see any place that I've checked to automatically compact folders. As far as I can tell, there must be other factors involved in losing the bold in a folder with new (or unread) email in it than just compacting. Again, I don't knowingly compact folders. It may happen without my knowing I'm doing it. But I don't choose to compact and then lose the bold on these folders. Doesn't work that way in my case.
Is this bug really fixed? Status has it as being fixed however my TB2.0.0.23 (20090812) is still not showing the Folder names in BOLD when new messages get put in there, in fact it is getting worse as the majority of all my folders now exhibit this behaviour and I am having to manually visit each folder everytime I poll for emails just to see it there is anything in the folder and usually there is. Any Feedback from people with advice
(In reply to comment #45) > Is this bug really fixed? Status has it as being fixed however my TB2.0.0.23 > (20090812) is still not showing the Folder names in BOLD when new messages get It's fixed in 3.0b2 so It's fixed in 3.0. The 2.x series only get security fixes these days.
Downloaded TB3 with great anticipation. Not one of my have-to-fix-this-or-I'm out-of-here was fixed. Absolutely incredible. Within days of installing TB3 and I suppose the upgrade to 3.0b2 I found two VERY IMPORTANT emails which had arrived in the last week in folders that weren't bolded. Also, this miserable program continues to open and therefor force backups on every last file associated with it, every time you back it up. Incredible. My backups run well over 1,000 files and 30 minutes every night and 90 percent of those, an even higher percentage possibly, are Thunderbird files. Enough is enough. The last thing I wanted to do was return to Outlook which has its own problems. I loathe Microsoft as a company and its software keeps getting worse not better. But I'm spending these days configuring Outlook again. And it's the Thunderbird programmers in all their wisdom who drove me back to Outlook. I'll say it again after three years or more of saying it. YOU CAN'T LOSE INCOMING EMAILS. Period. End of discussion. And they call the form of capitalism we've got competition!! What's your poison. An indifferent monopoly or incompetent, equally indifferent, clueless open source software. Truly depressing.
(In reply to comment #46) > (In reply to comment #45) > > Is this bug really fixed? Status has it as being fixed however my TB2.0.0.23 > > (20090812) is still not showing the Folder names in BOLD when new messages get > > It's fixed in 3.0b2 so It's fixed in 3.0. The 2.x series only get security > fixes these days. Thank you, though did not know TB3 was out as final as my TB2 has not prompted me to update to TB3 yet.
(In reply to comment #47) > I found two VERY IMPORTANT emails which had > arrived in the last week in folders that weren't bolded. After you upgrade to the official release of TB 3.0, you'll probably have to visit each mailbox again to find ones that should be bolded but aren't. From then on, it's been my experience during several months that I can compact mailboxes whenever I want (or let TB do it automatically) and this bug is fixed. However, there remains bug 483027 ("Closed parent folder not highlighted when subfolder receives new mail until TB repaints itself") which I hope they also fix.
it seems to be fixed for me using TB 3.0. The only problem now is the folders are "bolded", but actually show up a very faint grey. I have not been able to figure out how to change this. I also use QuickFolders and they show the new mails, as well.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: