Current released version is 0.3.2

GlodaQuilla was prepared at the request of Andrew Sutherland of Mozilla Messaging to assist in the debugging of the gloda global database. It adds three columns to the Thunderbird message pane:

  • OnDisk indicates whether a particular message has been downloaded to the local message store, or is stored offline in an IMAP folder or newsgroup.
  • Gloda id is the identifier used by gloda to uniquely identify a particular message.
  • Gloda dirty indicates messages that gloda needs to process.

In addition, GlodaQuilla allows suppression or enabling of indexing. This is done using inherited folder properties, so it can be done at the account level, or for a tree of related folders. Indexing is changed in the Account Manager for individual accounts, or using “Folder Properties” dialog for individual folders. See this page for a description of how inherited folder properties are used.

GlodaQuilla is available here.

Post comments, questions, or bugs in the GlodaQuilla forum.

Revision 0.3.2

This version’s primary purpose is to provide compatibility with Thunderbird 3.1, and its new ability that partially duplicates GlodaQuilla’s ability to suppress indexing of folders. This page describes specific issues with migration for existing users of GlodaQuilla.

Two new features have been added:

Inherited indexing suppresion may be disabled

For many users of Thunderbird 3.1, the new core functionality to suppress indexing per folder will be sufficient. For that reason, GlodaQuilla’s inherited indexing suppression may be selectively enabled (in the GlodaQuilla options page from the addon manager.) For new users, inherited properties are disabled by default. For any existing users who have previously set inherited properties for indexing suppression, GlodaQuilla’s options will remain enabled.

Indexing suppression will now be reflected in Gloda’s database

Previously, if you suppressed indexing for a folder, that stopped future indexing but did not get reflected in the existing gloda database index. Now, when you enable or disable indexing for a folder, that will get reflected in the results that appear in message searches using gloda.

Revision 0.3.0

In addition to the gloda columns, this release adds an experimental feature to allow overriding of the default gloda configuration concerning which messages are indexed. This new inherited folder property is called “Index in Global Database”.  Access to inherited properties such as this are discussed in the post “Inherited Folder Properities (revisited)”

You can use this property to disable indexing of servers or folders that are normally allowed, or to enable indexing on folders that are normally disabled (such as trash or junk folders). In my system, for example, for testing purposes I download my email both as IMAP and as POP3, but i disable the indexing of IMAP to prevent double indexing of the same messages.

This new property does not make any attempt to fix existing indexing when this is changed. Minimal support for this hopefully will be added for the 1.0.0 release of GlodaQuilla.