Deployment scenarios for indexing and autosync

SIG - Pédagogie sigpedag at
Fri May 28 06:02:31 PDT 2010

Le 27/05/2010 19:45, Wayne Mery (vn) a écrit :
> Related to Gloda Global Indexing and account auto-sync (message
> download), presumably there will be two scenarios of deploying:
> 1. indexing and auto-sync ENABLED
> 2. indexing and auto-sync DISABLED
> (a third less likely option, exists, with indexing enabled but autosync
> disabled - resulting in indexed searching that does not full text
> indexed on message bodies)
> It would be useful to hear what people (you all) plan to do, and the
> concerns you have.
> lays out some of
> the considerations for scenario 1.
> Please offer your perspective so your needs and concerns can be better
> understood.

I don't really see the point of synchronizing, I can see for laptop 
users but on a corporate scale? Imagine a company with all its 
Thuderbird clients configured in IMAP and where the %APPDATA% folder is 
on a network share.

What happens if all IMAP accounts are synchronized? The company will 
have to store all emails twice : once on the IMAP server storage + once 
the file server storage (where %APPDATA% is).

On workstations where %APPDATA% is stored locally and backuped from the 
workstation, the "ImapMail" directory can be excluded from the backup, 
but what happens if a computer is stolen? Every email will be readable 
on the hard drive (which is not the case with a "un-synchonized" IMAP 

At the moment my plans for TB2 => TB3.1 migration is to disable both 
autosync and indexing (using autoconfig).

All the best,


Ce message a ete verifie par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a ete trouve.

More information about the tb-enterprise mailing list