Wrapper package for MailScanner

[Julian Field]

Scott Silva wrote:
> 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.
>
Why not just make it a setting in MailScanner.conf that by default is 
set to 'no'?
I can do a simple 'grep' to find what it's set to.

Jules

-- 
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.