Bug Tracker item #3392092, was opened at 2011-08-15 20:22 Message generated for change (Tracker Item Submitted) made by whyscream You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1126467&aid=3392092&group_id=250683
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Tom Hendrikx (whyscream) Assigned to: Nobody/Anonymous (nobody) Summary: Move group configuration to dspam.conf Initial Comment: Since the group administration (DSPAM_HOME/group) is configuration data, and no application data, the contents of this file should be in dspam.conf. The reason for not doing this in the first place is not clear to me, but I'd guess that the file can be updated by external tools when new users are added to the system, and updating the central config file is too risky. This is now a moot point since the group config can easily be kept in a separate file when using split configuration files. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1126467&aid=3392092&group_id=250683 ------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Dspam-devel mailing list Dspam-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-devel