MailScanner v5.0.0-8 beta

[Mark Sapiro]

On 05/10/2016 10:09 PM, Jerry Benton wrote:
> 
> Debian
> https://s3.amazonaws.com/msv5/beta/MailScanner-5.0.0-8.deb.tar.gz



I finally got around to testing this one on Ubuntu 16.04. I ran
install.sh as an upgrade to 5.0.0-2.

Everything seems OK, but I had a few anomalies. the output and log tell me

> Upgrading /etc/MailScanner/MailScanner.conf
> 
> Your old configuration file will be saved as:
> /etc/MailScanner/MailScanner.conf.old.8026


In fact, it was saved as
~/ms_upgrade/saved.8026/etc/MailScanner/MailScanner.conf.old.8026

later, it says

> I would advise you to check on any parameters which are different between
> the default new conf file and the conf file you just created, so that you
> find any parameters whose default values have changed.
> 
>   diff -w MailScanner.conf.rpmnew MailScanner.new
> 
> to check for any differences in values you have not changed yourself.

As far as I can tell, neither MailScanner.conf.rpmnew nor
MailScanner.new was created anywhere. I only have the 'new files

/etc/MailScanner/MailScanner.conf and
~/ms_upgrade/saved.8026/etc/MailScanner/MailScanner.conf.8026

and the old

~/ms_upgrade/saved.8026/etc/MailScanner/MailScanner.conf.old.8026

It also says

> NOTE! If this was an upgrade, edit /etc/MailScanner/defaults

I know the script tells me

>   WARNING - Make a backup of any custom configuration files if
upgrading - WARNING"

but it would be good if an upgrade either didn't just replace
/etc/MailScanner/defaults. It would be better to either just create
/etc/MailScanner/defaults.new or backup /etc/MailScanner/defaults to
/etc/MailScanner/defaults.old before replacing it.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan