Ah,. hmm.. I guess it would make sense to be able to lock them in a standard way
one thing you could do is manually set up these accounts by setting the initial default prefs in your .cfg file, and then locking specific prefs. The account keys are garanteed if _you_ create them. See http://www.mozilla.org/mailnews/arch/accountmanager.html for details on how they are stored in prefs.js Alec Stephen Meredith wrote: > >> Actually, the RDF does expose all preferences, automatically (i.e. >> there's no code which picks and chooses which prefs are/aren't >> supported) >> the RDF is translated into strings which are used by xpconnect to get >> to all the standard mail interfaces, like nsIMsgIncomingServer, >> nsIMsgIdentity, nsIImapIncomingServer and so forth. All per account >> mail prefs are done through that mechanism, so all per account mail >> prefs are exposed via the RDF file. >> > > > Excellent. I didn't pick up on that. > > Any suggestions on how to protect the mail prefs? For other prefs, we > are putting them into a hashed .cfg and locking them. I think it makes > sense for an IT admin to want to lock some of them. > >
