I was reading another thread that digressed into the topic about the difficulty of keeping up with the latest .cfg file while maintaining the mail administrator s customized .cfg
I would like to suggest that perhaps a different approach to managing the .cfg files could be implemented. It would be really nifty to have a base .cfg file and a separate .cfg file that holds an admin s changes. This method works well in BSD style configuration files.
That way the good folks at declude could keep the base .cfg files updated and the admin s could conviently replace their base cfg file. The diff file for lack of a better word would store the admin s tweeks, which would include addtions and subtractions from the base.
That actually sounds like a good idea. That would also work well for people who have Declude running on multiple servers, and want to have one source for the config file, but have different activation codes on each server (the activation code could go into the config file that is manually updated).
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000.
Declude Virus: Ultra reliable virus detection and the leader in mailserver vulnerability detection.
Find out what you've been missing: Ask for a free 30-day evaluation.
--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
--- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
