2010/1/27 Norman Maurer <[email protected]>: > Hi all, > > I would like to split the current configuration file > (james-config.xml) of james in a more logical way. I think keeping > everything in one file is just confusing. I would like to split the > config file to one file per service/component. I think this would make > it even easier for us to reload config per service etc later.
I'm fine with this change. Ideally I'd like to extract some basic variable to a property file, so that hostname, servernames, dns servers and other *MUST CHANGE* configuration are in the property files so that for a basic setup you don't have to touch the xml (maybe spring can help us here?) > This would give us something like: > > > pop3server.xml > imapserver.xml > smtpserver.xml > remotemanager.xml > james.xml > spoolmanager.xml > dnsserver.xml > domainlist.xml > management.xml > mailstore.xml > users-store.xml > virtualusertable-store.xml > spoolrepository.xml > > (maybe using one config for all the stores + repostory). +1 > I would also like to remove all the commented mailets and just keep > the "important" ones. If users / devs really want to add an extra > mailet then they should read up on them on the docs. This will end up in spoolmanager.xml .. maybe we could have a spoolmanager.xml.example with the commented stuff? Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
