Debian 4.86.1 beta
jerry.benton at mailborder.com
Thu Jan 28 06:59:32 UTC 2016
Yeah. I just tested it. Works fine.
> On Jan 28, 2016, at 1:54 AM, Mark Sapiro <mark at msapiro.net> wrote:
> On 01/27/2016 10:28 PM, Jerry Benton wrote:
>> Ok, looking at the source …
>> Look for /etc/default/MailScanner
> Correct, but the older /etc/cron.daily/mailscanner and
> /etc/cron.hourly/mailscanner are not remove which is a problem as they
> will run too, and they reference /etc/default/mailscanner which also is
> not removed.
>> There is no cron jobs named update_* in 4.86.1 - Old files?
>> As a side note, there was not in the last version either. Did you create them?
> I believe they were in versions as recent as 4.84.x, and if
> update_phishing_sites and update_spamassassin aren't installed in the
> current version. what runs /usr/sbin/update_phishing_sites and
> /usr/sbin/update_spamassassin (actually, for the latter, I use the
> debian/Ubuntu /etc/cron.daily/spamassassin job and disable
>> Should we:
>> - Remove those if found?
>> - Remove and replace?
> I definitely think they shouldn't be just removed. Remove and replace
> seems correct, but this assumes that they would be installed if not
> there. Also, I just noticed, apparently no cron runs
> /usr/sbin/update_bad_phishing_emails. Perhaps this is OK as it is really
> ScamNailer and probably requires other config as well.
> Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
> San Francisco Bay Area, California better use your sense - B. Dylan
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
More information about the MailScanner