It would be nice to be able to use my current config.xml in future
versions of James. I have been thinking about making a Swing app for
editing the James config file.
Regards,
Eric MacAdie
Pronounced: muh-KAY-dee
Norman Maurer wrote:
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.
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).
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.
WDYT ?
Bye,
Norman
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
