Wrapper package for MailScanner

[Scott Silva]

on 7-28-2008 8:49 AM Hugo van der Kooij spake the following:
> Scott Silva wrote:
> 
> | You would probably want some sort of flag file that a user could touch
> | to stop the automatic upgrade of those files. It doesn't bother me, but
> | I remember from list traffic that there are many people that have custom
> | comments or other content that they wish to preserve.
> |
> | Maybe a check like;
> |
> | if [ -f "/etc/MailScanner/no-upgrade" ]; then
> |   skip upgrade
> 
> How about the other way around? Then a new package will never hurt
> existing users. And once people believe they want the config  upgrade to
> be automated they can add a placeholder file to do so from that moment on.
> 
> This would be the failsafe way to it. Only if
> /etc/MailScanner/automate-config-updates is present this should be done
> automagically. (Or by whatever other name Jules likes to call the file.)
> 
> Hugo.
> 
> 
That does sound much safer. Must consciously choose to have updates done.
No accidents, no blame!
Jules might even agree to this.

-- 
MailScanner is like deodorant...
You hope everybody uses it, and
you notice quickly if they don't!!!!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 258 bytes
Desc: OpenPGP digital signature
Url : http://lists.mailscanner.info/pipermail/mailscanner/attachments/20080728/39cd4eb5/signature.bin