McAfee Autoupdate

[Professional Investments Investor Services]

Ok thanks, for that.

I simply renamed mcafee-autoupdate.gnu, which was place there from the
upgrade? And ran the script. All seems ok.

Thanks,

Mark
-----Original Message-----
From: MailScanner mailing list [mailto:MAILSCANNER at JISCMAIL.AC.UK]On Behalf
Of Remco Barendse
Sent: Wednesday, May 28, 2003 10:53 AM
To: MAILSCANNER at JISCMAIL.AC.UK
Subject: Re: McAfee Autoupdate

Why my setup didn't upgrade is because I deleted the cron scipt that comes
with MailScanner, it's entirely my fault.

I use a selfmade script instead that fetches the more experimental but
usually very up2date dailydat.zip file. mcafee is too slow for my taste when
it
comes to releasing updated dat files. I simply forgot to restore my own
script to cron.

On Wed, 28 May 2003, Professional Investments Investor Services wrote:

> After reading the discussion on the support at microsoft trappings, I became
> curious with regards to the McAfee update. I believe we are running MS
> 4.20-3 on an upgrade from previous versions as early as November. This
list
> moves rather quickly so I apologize if this has been covered but what
should
> be the "new" correct method for running the autoupdate? Previously we had
a
> cron job running daily that would call
> /usr/lib/MailScanner/mcafee-autoupdate , however like Remco Barendse our
dat
> files had not been updated since May 7th.
>
> Secondly, for what it's worth all of our support at microsoft mailings were
> stopped for extension only as listed by MS
>
> "The following e-mail messages were found to have viruses in them:
>
>     Sender: support at microsoft.com
> IP Address: 216.168.107.137
>  Recipient: keithn at pro-invest.ca
>    Subject: Screensaver
>  MessageID: h4SBI8o29055
>     Report: Shortcuts to MS-Dos programs are very dangerous in email
> (screen_doc.pif)
>
> Full headers are:
>
>
> Thanks,
>
> >>>>>>>>>>>>>>>>>>>>>
> Mark Tavares
> IS Tech Support
> Professional Investments Inc.
> 1-888-548-8868
> <<<<<<<<<<<<<<<<<<<<<
>