Have your considered placing the users mail store on a Coda Files System (http://www.coda.cs.cmu.edu/) or similar? CODA supports disconnected operation and multiple write masters. I used it for a distributed CVS archive. The only problem we had was that during network outages between sites it was possible to have the same file modified in both write servers thus requiring an administrator to resolve the conflict (see Coda manual for details on this) when synchronizing. Considering that Courier uses unique file names for mail storage you shouldn't have this problem. Also, since each unique file will most likely only be accessed by one user at a single site, the chances are very slim that the file could be modified on both sites while the link was down.
You might want to check out Coda. I have thought about it a little in the case where we end up locating our servers at multiple data centers. Since that is still a ways out I haven't tested this in a lab environment yet with Courier. -- Jacob S. Barrett [EMAIL PROTECTED] www.amduat.net "I don't suffer from insanity, I enjoy every minute of it." ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
