User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:33.0) Gecko/20100101 Firefox/33.0 Build ID: 20141023194920 Steps to reproduce: I deleted global-messages-db.sqlite and launched TB in order to force TB to rebuild the Global Search index. I also disabled "Keep messages for this account on this computer" and deleted the entire IMAP mail store from the TB profile directory. (For details, see bug 1095988). Actual results: Each time I click on a mailbox in the mailbox list, the respective mailbox is re-indexed, however, the Activity Manager does not always indicate that re-indexing is taking place (it is silent). It appears that any time the re-indexing goes very quickly (perhaps less than one second), no Activity Manger message is displayed at all, however, I've also witnessed no Activity Manager message presentation with re-indexing that takes several seconds, although this is much more rare. Sometimes when I click on an IMAP email box and it subsequently indicates that 250 headers are being downloaded, the Activity Monitor message that is generated states that, say, 200 (email) messages are being indexed. Additionally, if, say, 1000 (email) message headers are downloaded such that 1000 (email) messages are indexed, several different Activity Manager messages may be displayed, each indicating that a different number of (email) messages are be re-indexed for said box, and the total of the counts across the three Activity Manager messages will not add up to the number of (email) message headers downloaded. Despite all this, the re-indexing does appear to be taking place (as is explained further in bug 1095988). Expected results: I assume that a single Account Manager message should be displayed for each mailbox that is re-indexed, and that the re-indexed (email) message count indicated in the Account Manger message should match the number of (email) message headers downloaded when the IMAP mailbox was selected. I did find some previous discussion regarding quieting down the Activity Monitor when re-indexing is taking place, however, the re-indexing I'm describing is simply one email box at a time as I click them (although I should not have to be doing this per bug report 1095988). This is a slow human iterative process, so there is no flurry of activity that would cause multiple Activity Monitor messages over a very short period of time. The number of messages it claims are being indexed does not match the number of messages headers downloaded, as explained previously, which seems like a bug in any case.
(In reply to Ken Alker from comment #0) > Steps to reproduce: > (a) I deleted global-messages-db.sqlite and launched TB in order to force TB to rebuild the Global Search index. > (b) I also disabled "Keep messages for this account on this computer" > and deleted the entire IMAP mail store from the TB profile directory. > Actual results: > Each time I click on a mailbox in the mailbox list, the respective mailbox is re-indexed, however, > the Activity Manager does not always indicate that re-indexing is taking place (it is silent). First of all: When imap, re-indexing is not done upon mail folder click after deletion of .msf file. All data is held at imap server, and message header of all mails is fetched from server again and saved in .msf file. If XXX.msf file is deleted by you, already fetched mail data to Offline-Store file(file named XXX) is discarded, because you deleted XXX.msf file. Mail data is not automatically fetched, unless auto-sync of imap folder is effective. If auto-sync is not effective, mail data is fetched upon mail viewing. Thiese are different from pop3 folder. When pop3, mail data of folder named XXX is already held in file nameed XXX, and content of XXX is reparsed and XXX.msf is re-created upon first folder click after deletion of XXX.msf by you. This in pop3 is called "re-indexing" sometimes. Because you did (b) too, it's pretty normal and proper phenomenon. - "Global Search and Indexer" is for "Full Text Search of message body text", so indexing is done on (i) mails in local mail folder(pop3 account, Locl Folders), and (ii) mails in imap folder whose entire message data is fetched to Offline-Store file by auto-sync. - When you unchecked "Keep messages for this account on this computer", auto-sync feature itself is not disabled by Tb, but Offline-Use=On property(Fiolder Properties/Synchronization) of all folders of the imap account is reset by Tb according to your request. auto-sync of an imap folder = "auto-sync feature is enabled for the imap account" + "Offline-Use=On of the imap folder". So, auto-sync of any folder of the imap account was killed by you. If you need "auto-sync of mail folder of the imap account" and "indexing for Global Search", do one of next. - Via. "Advanced" button at "Keep messages for this account on this computer" option, set Offline-Use=On for each IMAP folder. (This can be done via Folder Properties/Synchronization of ech imap folder) Once "Keep messages for this account on this computer" is changed from "Checked" to "Unchecked". "Unchecked status" == default of "Offline-Use=Off" for newly created or renamed folder under this imap account. - Change "Keep messages for this account on this computer" from "Unchecked" to "Checked". Offline-Use=On property of all folders of the imap account is set again by Tb. Once "Keep messages for this account on this computer" is changed from "Uncchecked" to "Checked". "Checked status" == default of "Offline-Use=On" for newly created or renamed folder under this imap account. Read documents which can be found by Google srach for "Thunderbird auto-sync imap" or "Thunderbird gloda", please. https://support.mozilla.org/en-US/kb/imap-synchronization http://kb.mozillazine.org/Offline_folders#AutoSync https://developer.mozilla.org/en-US/docs/Mozilla/Thunderbird/Gloda_indexing#What_Folders_get_Indexed.3F FYI. GlodaQuilla add-on is a good way to know "a mail is indexed by Global Indexer or not".
1. Did you use Thunderbird prior to vesion 31 and have the same difficiulty? 2. what is your thinking after reading comment 1?
See Also: → bug 1095988
You need to log in before you can comment on or make changes to this bug.