I updated to Courier 0.60.0 yesterday, and I noticed a couple of things afterward:
1) esmtpd and esmtpd.dist contain a line that reads: # [EMAIL PROTECTED]@ Is this left over from the 2001 "SSL simplification project"? 2) The TLS_TRUSTCERTS setting isn't present in esmtpd-ssl or imapd-ssl, though it is in courierd and esmtpd. All of those files mention the default from the .dist in a comment. I'm not sure how sysconftool decides whether or not to insert a new setting from .dist when it does upgrades, but this reminds me of something that I've been thinking for quite a while. sysconftool seems well conceived, but overly complex. It seems like the same problems could be solved instead by distributing <config>.dist, and keeping <config> empty of all settings other than non-defaults. In that case, the init script would need to be modified so that it sourced the <config>.dist file first, and then <config>. Settings in <config> would simply override the <config>.dist settings. As an admin, I prefer keeping the configuration files that I maintain as concise as possible, as it makes it much easier for me to set up a new host based on the configuration of another working host. Is there an advantage to sysconftool that I'm missing? ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
