Request: Disable update.bad.phishing.sites job when phishing
checks are disabled
ms-list at alexb.ch
Thu Apr 10 12:23:56 IST 2008
On 4/10/2008 12:51 PM, Julian Field wrote:
> Glenn Steen wrote:
>> On 10/04/2008, Alex Broens <ms-list at alexb.ch> wrote:
>>> I've disabled all MailScanner phishing checks yet:
>>> Apr 10 12:01:01 cobox-1 update.bad.phishing.sites: Delaying cron job
>>> up to
>>> 600 seconds
>>> It would be very elegant if these are not enabled, the cron job is
>>> as well.
>>> same with AV signatures update hourly job.
>> I'm not sure I agree, and I'm pretty sure Jules doesn't... You are not
>> the first to ask:-).
>> The thinking here is that the update jobs for functionality you
>> *might* enable later should still be active, so that when you _do_
>> activate them, all updates are already in place. The correct way to
>> avoid this for AV is to deinstall any unused AV product. For the
>> phishing thing... there simply is no such thing.
> I'm with Glenn on this one, sorry.
> If you decide to enable a feature, it should be ready and waiting for
> you. It hardly adds a significant load to your system, and you can
> always disable the cron job yourself if you want to, just chmod -x the
> file in /etc/cron.hourly.
so its not possible to check *if* feature enabled and *if* not enabled,
the moment you enable the feature, the check will see *if* enabled and
run the update.
More information about the MailScanner