> > The big issue I've run into in this scenario is how to install a > > single instance of SM and have it connect to multiple servers and > > store the preferences on a per post office basis- the multilogin > > plugin doesn't change the way preferences are stored (i.e., if my > > login is 'bobsmith' on one particular post office and someone else > > owns 'bobsmith' on another post office, the preferences aren't > > unique), so unless I find a better alternative, I will create a > > separate instance of SM on the DMZ webmail host for -each- post > > office, with a separate database for each post office.. since SM is > > roughly 10MB, this isn't an issue (and I could make hard links to > > save space if needed).
This has been requested before. The attached patch is something experimental that I put together (but have only done minimal testing) to alleviate this problem. It tacks the IMAP server address to the end of all preferences storage (both file-based and db-based). The problem is that there are any number of plugins that could screw this whole thing up. I patched it with just the stock plugins, plus shared calendar instead of calendar..... I would be willing to help if you are interested in making this a permanent solution and it isn't up to spec...
prefs_stored_with_imap_addr.squirrelmail.tar.gz
Description: Binary data
