The problem with all in one file is that many scripts, STAMP included weren't designed for this, and you have to think with an extra level of nesting in the configuration stage. It's a good idea if you think about it first.

However, imaging the situtuation where you're trying to replace Selena Sol or MSA scripts on a hosting companies server. Now you have the problem that each user has to edit the global file, which I don't think is smart, unless you build a process for editing such a file (really should be a DB I suppose on this scale), so that they can change their own bits.

If you have multiple files, more sophisticated than my first stab, you can let users own and configure them on their own. Though now you have to be careful when you parse them....!

My case is a bit simpler, it's just a bunch of web sites for the same company, but in differnt domains on the same box (.de .co.uk etc), but I was wondering how you go about remplacing formmail et al on an under staffed hosting companies server.

As ever thanks in advance