No problems here with 3.81 - one thing I wish it did do was to scan
attachments blocked by extention blocking - we've had loads of bugbears
quarantined for being .exe's , but it doesn't seem to actually scan them as
well.

regards,
Paul
--
Paul Hutchings
Network Administrator, MIRA Ltd.
Tel: 024 7635 5378, Fax: 024 7635 8378
mailto:[EMAIL PROTECTED]

> -----Original Message-----
> From: Roger Seielstad [mailto:[EMAIL PROTECTED]
> Sent: 06 June 2003 15:46
> To: Exchange Discussions
> Subject: RE: ScanMail missing tricks?
> 
> 
> You might want to consider upgrading to Scanmail 3.81. I believe it
> functions a LOT better.
> 
> --------------------------------------------------------------
> Roger D. Seielstad - MTS MCSE MS-MVP
> Sr. Systems Administrator
> Inovis Inc.
> 
> 
> > -----Original Message-----
> > From: Tim Gowen [mailto:[EMAIL PROTECTED] 
> > Sent: Friday, June 06, 2003 10:25 AM
> > To: Exchange Discussions
> > Subject: ScanMail missing tricks?
> > 
> > 
> > 
> > A user got an infected attachment right to her Inbox, which 
> > doesn't ever happen here since we started using ScanMail.  I 
> > have ScanMail 3.52 (Exch 5.5
> > SP4) blocking all the attachments on the List of Danger, and 
> > yet this BUGBEAR.B file - QABACKUP.EXE.SCR - got through to 
> > the Inbox.  A Manual scan showed up six other virus-infected 
> > attachments which had apparently got through.  But the manual 
> > scan does not pick up the file I just mentioned, which is now 
> > in my Deleted Items.  A copy is on my hard drive and Sophos 
> > AntiVirus also doesn't detect it.
> > 
> > Is it possible that ScanMail misses out on some messages if 
> > several arrive at once, or is there another more likely 
> > solution?  I have sent the file to Trend and Sophos to see 
> > what they say, but the attachment blocking was, I thought, 
> > non-negotiable and always works.  Luckily I badger my users 
> > about the danger of attachments on a fairly regular basis.
> > 
> > 
> >     Tim
> > 
> > -- 
> > Tim Gowen  
> > RAF Museum
> > IT Dept.
> >  
> > 
> > Confidentiality: This e-mail and its attachments are intended 
> > for the above named only and may be confidential. If they 
> > have come to you in error you must take no action based on 
> > them, nor must you copy or show them to anyone; please reply 
> > to this e-mail and highlight the error.
> > 
> > Security Warning: Please note that this e-mail has been 
> > created in the knowledge that Internet e-mail is not a 100% 
> > secure communications medium. We advise that you understand 
> > and observe this lack of security when e-mailing us.
> > 
> > Viruses: Although we have taken steps to ensure that this 
> > e-mail and attachments are free from any virus, we advise 
> > that in keeping with good computing practice the recipient 
> > should take steps to confirm that they are actually virus free.
> > 
> > 
> > 
> > _________________________________________________________________
> > List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
> > Web Interface: 
> > http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&t
> ext_mode=&lang=english
> To unsubscribe:         mailto:[EMAIL PROTECTED]
> Exchange List admin:    [EMAIL PROTECTED]
> 
> _________________________________________________________________
> List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
> Web Interface: 
> http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&t
ext_mode=&lang=english
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface: 
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

Reply via email to