On Mon, Dec 22, 2003 at 01:57:13PM -0700, Bryan Scott wrote: > Gavin Carr wrote: > >Just to throw another approach into the pot for discussion, I've been > >thinking about approaching this by adding subdirectories to the 'config' > >directory by RCPT domain, and having per-domain config files in these > >subdirectories that override (or perhaps are merged with) the system-wide > >qpsmtpd/config versions. i.e. > [..snip..] > > >Thoughts/flames? > > Looks like a neat solution to me, but then we have the potential of having > 15 million files in the config directory... (Ok, I have 2000+ mailboxes, so > it wouldn't be *that* many).
Sure, but if you're wanting to store per-user configs for 2000+ users then you're going to be dealing with a fair amount of data no matter what. I'd rather have that in 2000 directories (probably multi-level directories, I guess) than one big file with 2000 entries in it. Anyhow, as we keep coming back to, the actual config formats are probably less important than defining an api to access the data. The thing I like about going this way is that it reuses the current config api, rather than requiring changes, and looks like it can be implemented just using a config hook. I'll try and post some proof-of-concept code to the list tomorrow, but I'm offline for a couple of weeks after that, so won't be able to follow it up for a while. Cheers, Gavin
