Tony Finch wrote: > On Tue, 4 Jul 2006, W B Hacker wrote: > >>Tony Finch wrote: > > >>>I suppose we could do so with a much more complicated database >>>infrastructure, but why bother when Exim can resolve it at run time? >> >>It is not only 'possible' to do this in a 'flat' model, it is >>simple and quite easy to provide to diverse managers, groups, >>and users. [...] >> >>- One or more DB (SQL or other) with 'n' domains, each of which >>has 'nd' departments, 'nds' sub-departments, etc. as far down as >>you need to go (3 to 5 levels?). > > > You make my point for me. Our infrastructure for this is just a load of > aliases files and a simple user interface for editing them. The fewer > programs we have to manage the better - hence no SQL database. > > Tony.
?? When you said: > (PS. I've sketched over the fact that users can independently control > redirection of their @cam and @hermes addresses, which is indeed a bug > because they have two ways to control the same functionality without any > protections against getting in a mess. We avoid most of the problems > because the @cam redirection is much more obscure than the @hermes > redirection. The point is that you minimise support costs by minimising > the number of ways of doing something.) I thought you were making *my* point for me... (we use ONE DB, replicate it even to servers that use only a portion of it) Either way, we've outlined examples and the pros and cons of the extremes, so folks can do whatever (else) best suits their own environment. ;-) Regards, Bill -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
