Thunderbird/Enterprise/Migration

Migration From Thunderbird 2.0 To Thunderbird 3.0

Warning: This Is Draft

• This is draft of Migration Guide for corporate users.
• Migration Guide is being tried to create, as we knew this kind of documentation is needed in Bug 562589. This draft is a brief summary(as of 2010/05/06) of knowledge about auto-sync/offline-use settings obtained in the Bug 562589.

Background

Upon release of Thunderbird 3.0, next big changes were made.

• Gloda(Global Search and Indexer) is enabled by default.
• Auto-sync of IMAP folders is enabled by default for all IMAP accounts.
• Per folder "offline use" setting of all IMAP folders is set to "offline use=ON" by default upon migration(first use of Tb 3.0.x).
• View of folder pane is forced to "Smart Folders" view even though "All Folders" is Tb 2 user's ordinal choice in his daily use.
• Tb 2's "Account Wizard" and Tb3.0beta's "Account Wizard for Gmail IMAP" is removed before official release of Tb 3.0.0.

But spec of above changes, required settings for above changes is not so well documented yet. This Migration Guide is to avoid confusions by sysem management people upon upgrade from Tb 2.0.x to Tb 3.0.x due to above big/important/drastic changes by Tb 3.0.x.

Disable Migration Wizard

lockPref("mailnews.ui.show.migration.on.upgrade",false);

Disable Gloda(Global Search and Indexer)

Gloda is new feature of Thunderbird 3.0 and is enabled by default. Corporate users usually doesn't won't different behaviour from Thunderbird 2. Disable Gloda before migration.

Disable Auto-sync, Keep per folder "offline use" setting

Auto-sync of IMAP folders is enabled by default for all IMAP accounts. And per folder "offline use" setting of all IMAP folders is set to "offline use=ON" by default upon first use of Tb 3.

1. Disable auto-sync (one of next two, or both for fail safe)
   • lockPref("mail.server.default.autosync_offline_stores", false);
   • lockPref("mail.server." + serverFromAccount + ".autosync_offline_stores", false);
2. Disable per folder "offline use" setting change upon migration
   • lockPref("mail.server." + serverFromAccount + ".offline_download", false);

Hints&Tips

• mail.server.serverX.offline_download (default=true)
  • When an IMAP folder is created or subscribed, set offline use=off if false, set offline use=on if true. i.e. This setting is for default of offline use=on/off of an IMAP folder.
  • It's enhanced by bug 562589, and next meaning is added.
    • Upon first use of Tb 3, if serverX.offline_download=false is set before upgrade, IMAP folder's "offline use" is not touched by Migration code of Tb 3.
• Current behaviour of UI for auto-sync setting:
  • Unchecked->Checked
    1. Set mail.server.serverX.offline_download=true
    2. Set offline use=on of all folders of the IMAP account
  • Checked->Unchecked
    1. Set mail.server.serverX.offline_download=false
    2. Set offline use=off of all folders of the IMAP account
• Gloda and auto-sync/offline-use are possibly independent, althoug relevant.
  • "Download Now" button downloads mail to offline-use regardless of offline-use=On/Off.
  • "Download Now" button seems to be intercepted and discarded if auto-sync is enabled and offline-use=On. It looks due to already started schedule based automatic downloading.
  • Auto-sync automatically downloads mail data to offline-use if auto-sync is enabled and if offline-use=On is set in an IMAP folder.
  • "Work Offline" automatcally downloads mail data to offline-use automatically, if per folder offline-use=On is set in an IMAP folder.
  • Gloda indexes mail data in offline-store, if mail data is saved in offline-store, perhaps regardless of auto-sync is enabled/disabled and offline-use=On/Off and Working Online/Working Offline.

"Smart Folders" view at folder pane

View of folder pane is changed to "Smart Folders" by default. As ordinal use is "All Folders", change to "All Folders" should be recommended to users, in order to avoid unwanted questions to Help Center.

Account definition by autoconfig

As only "autoconfig" is availabe for account definition, setups for autoconfig should be carefully done, in order to avoid user's confusions due to unexpected behaior of autoconfig or failure during autoconfig, if account definition by user himself is permitted.