[cobalt-users] Bassi Mailscanner 3.21-1 & RAQ3 <Quick Question>

["Lab Mail" <mbeaudry@xxxxxxxxxxxxxxx>]

I have Bassi's Mailscanner 3.21-1 for the RAQ3 installed (thank you very
much Steve) and other than the initial time during installation, the
"autoupdate" feature has never functioned (I only recieved a single email
that one time after the update). *Please note that I assume the package is
still functioning as I get "X-MailScanner: Found to be clean" in my email
headers*

I know this has been covered in the archive (and I have read as much as I
can digest from said archive) and I know that Bassi is working on an update
to said pakage (or so I gleaned from the archive). However beeing a newb and
all to both Linux AND Cobalt, I like to see things dumbed down a little so I
was looking for an archive meesage that states:

"Hey, newbie, if you're RAQ3-Bassi-MailScannerRelease 3.21-1 is not
auto-updating (or your not getting the email that says so anyways), you MUST
manually update until a new package comes out. To do so, you do this:  blah
blah blah"

However, I never found it. So I wish to ask:

Is the correct methodology for ensuring that the
"RAQ3-Bassi-MailScannerRelease 3.21-1" package is using the latest "updates"
from F-Prot as follows:

1. Telnet/ssh into Raq3 as root

2. Type in "/usr/local/f-prot/autoupdate" (minus the quotes) to execute the
update to F-Prot from the f-prot directory itself assuming you left
everything as default during installation.

3. The following responses fill the terminal display if everything is
actually fucntioning regarding F-Prot:

FTP address for retrieving files is ftp://eu-2.updates.f-prot.com/pub//
F-Prot signature file update script
There is a new version of SIGN.DEF, starting download.
Download completed.
Updated SIGN.DEF.
There is a new version of SIGN2.DEF, starting download.
Updated SIGN2.DEF.
There is a new version of MACRO.DEF, starting download.
Download completed.
Updated MACRO.DEF.
Update completed.

At this stage would it be safe to say that the RAQ3-Bassi-MailScannerRelease
3.21-1 package is now using the latest virus definitions from F-Prot, or is
there another step to go yet?


Thanks for you patience...

Marcel