this makes sense - with the segregation one would also try to isolate the parameters that can get changed or modified by SMTP server administrators in the normal course of business.
one of the things that come to mind are - port address delay time-spans modifications to the CIDR ranges all of which are adjusted to either fine tune or restict access. when the con fig file needs to be modified often, if one could isolate these 'user configurable's, we could minimize the changes of corruption. > ----- Original Message ----- > Another alternate idea may be to have James expose > configuration settings in 2 levels. > > - External configuration - config.xml > and > - Internal configuration - say config-defaults.xml. This > is for advanced users. End users would not be expected to > change this, but if they really do, then there is no need > to recompile code. smtp* properties, authoritative tag in > dns server(has generated a lot of traffic and should > really not be changed), all hardcoded defaults could go in > this. _______________________ thanks, alan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
