Wrapper package for MailScanner

[Hugo van der Kooij]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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.


- --
hvdkooij at vanderkooij.org               http://hugo.vanderkooij.org/
PGP/GPG? Use: http://hugo.vanderkooij.org/0x58F19981.asc

	A: Yes.
	>Q: Are you sure?
	>>A: Because it reverses the logical flow of conversation.
	>>>Q: Why is top posting frowned upon?

Bored? Click on http://spamornot.org/ and rate those images.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFIjeqJBvzDRVjxmYERAqfPAKC1oepghYL/9QtVPAljnooEox5MpgCfY479
Onq4J9SS6pQiEFGiZTG+kLw=
=UnpY
-----END PGP SIGNATURE-----