382116 - Thunderbird should allow to use external Database for message storage

Status: UNCONFIRMED

(Thunderbird :: General, enhancement)

Description

[Ralf Hagen]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; de; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Build Identifier: all prior to at least Version 2.0.0.0 (20070326)

The Thunderbird DB seems to get unreliable and slow with great numbers of messages (> at most 10,000). A parallel installation of multiple database Systems (eg, PostgreSQL, DB system for Thunderbird, DB system for Office files and items...) is not desirable, when an existing DB system like Postgres, Firebird or DB2 is already installed.

I request the in-built database of Thunderbird to get encapsulated in an optional module that can be deselected at installation time and the possibility to connect to an existing SQL or LDAP server. Migration should be made possible from one DB to another, as well as crucial backup options for eMails.

This approach would greatly enhance the attractiveness of Thunderbird for Business and Gouvernemental purposes, where stable management of great numbers of messages as well as easy and secure backup of sent/received communications are of major importance.

Reproducible: Always

Steps to Reproduce:
1. Thunderbird DB should be made an optional modular component
2. Thunderbird should be able to connect to an external DB system (SQL, maybe LDAP) like Postgres
3. Thunderbird should be able to migrate an existing message stock from one DB system to another when DB components are changed on the system
4. An extended export feature should be made possible to archieve messages
Actual Results:  
1. Thunderbird's DB system seems to be monolithically in-built
2. Thunderbird cannot use an external DB system that may exist already, making the ressources of the Thunderbird DB system redundant, and that could handle Thunderbird's data more efficiently
3. Thunderbird cannot migrate to other DB systems, only migration of data stock to subsequent versions of Thunderbird is possible.
4. No export of accounts is possible.

Expected Results:  
1. Thunderbird should be modularised into two modular components, one the message and managing frontend, another the Database that stores the messages and at least also the filter configuration. On custom installation, the DB component should be made optional.
2. Thunderbird should be able to connect to external DB servers using the SQL  standard installed on the system, making redundant installation of multiple DB systems unnecessary.
3. Thunderbird should be able to migrate its data stock between DB servers installed on a system, eg, migrate from its own DB system to Postgres/Firebird/DB2/Oracle and vice versa or between external DB systems.
4. Thunderbird should be able to export messages and filter rules to a documented format for archieving purposes.

I deem this feature request valid as it is not possible to offer the desired functionality in a custom-programmed add-on. At least the modularisation of the internal DB system of Thunderbird and the definition of communication messages between the Thunderbird Messenger and the Database require a coordinated adjustment of the core programs.

I see this as a request of above-average priority, as this issue should i.m.o. be addressed medium-term so that further developement of database connectivity can be made possible.

Comment 1

[zug_treno]

Related to/duplicate of Core bug 361807, bug 399548 or Core bug 402392?

Comment 2

[WADA:World Anti-bad-Duping Agency]

Bug 402392 is meta bug. Setting relation(put 402392 in Blocks: field).