> I want to put together a few standard configurations that can > be part of the office release. [...] > I have some ideas for 'configuration types' ... > > 1. SMTP/POP3 only (assembly/config) > 2. Full configuration (assembly/config) > 3. Single Domain (config) > 4. Multiple Domain (config) > 4. Full logging (environment) > > > Let me know what you guys have - you can reach me off line if > you'd prefer ... > > - Alan
I run four domains, each running independently for paying clients. Each client gets the full power of what James offers without worry of intersecting with the config of other domains. Each has unique setup with different AUTH and trust rules, and some with custom mailets, and one pretty plain setup altogether. I like that it simplifies management of the configs; you don't worry how it will affect another. Each domain is served by its own app which binds to its own domain's address on the box. Each is installed within a single phoenix JVM. The only downside is if I need to restart the container, all domains go down. But that would be the case even if it were a single app. (A container that could really "unload" a module/component would be cool.) I have rarely needed to restart the container in production, and it is not a big problem. Incoming mail gets retried, and outgoing mail simply fails while the server is down. -broc --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
