Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Thread

NOTICE: Your e-mail to briaust@bri.com.au triggered scanning rules

NOTICE: Your e-mail to briaust@bri.com.au triggered scanning rules

2004-05-04 by h.yun@bri.com.au

NOTIFICATION OF EMAIL SCANNING RULE TRIGGER

You recently sent an e-mail to briaust@... at 05 May 2004
08:35:06 am EST with the subject "Changes..". 

This e-mail was automatically examined by the NetBox and triggered a
content or virus scanning rule.

The e-mail has been blocked and will NOT be sent to the intended
recipients.

The following details apply for this rule trigger:
----------------------------------------------------------------------
This e-mail triggered content scanning rules because of 
the names of one or more of its attachments.

Toy.scr -> attachment names matching '*.scr'
----------------------------------------------------------------------

Contact h.yun@... for further information.

End of notification.

NOTICE: Your e-mail to briaust@bri.com.au triggered scanning rules

2004-05-05 by h.yun@bri.com.au

NOTIFICATION OF EMAIL SCANNING RULE TRIGGER

You recently sent an e-mail to briaust@... at 06 May 2004
08:35:00 am EST with the subject "Re: Hi". 

This e-mail was automatically examined by the NetBox and triggered a
content or virus scanning rule.

The e-mail has been blocked and will NOT be sent to the intended
recipients.

The following details apply for this rule trigger:
----------------------------------------------------------------------
This e-mail triggered content scanning rules because of 
the type of one or more of its attachments.

Document.com -> 'MS-DOS Executables'
----------------------------------------------------------------------

Contact h.yun@... for further information.

End of notification.

NOTICE: Your e-mail to briaust@bri.com.au triggered scanning rules

2004-05-06 by h.yun@bri.com.au

NOTIFICATION OF EMAIL SCANNING RULE TRIGGER

You recently sent an e-mail to briaust@... at 07 May 2004
08:29:34 am EST with the subject "Encrypted document". 

This e-mail was automatically examined by the NetBox and triggered a
content or virus scanning rule.

The e-mail has been blocked and will NOT be sent to the intended
recipients.

The following details apply for this rule trigger:
----------------------------------------------------------------------
This e-mail triggered content scanning rules because of 
the names of one or more of its attachments.

Counter_strike.scr -> attachment names matching '*.scr'
----------------------------------------------------------------------

Contact h.yun@... for further information.

End of notification.

Re: [lpc2000] NOTICE: Your e-mail to briaust@bri.com.au triggered scanning rules

2004-05-06 by Robert Adsett

Here's hoping briaust is reading their e-mail.  Will you please (pretty 
please) turn off the notification to sender on your virus detection 
SW.  Once is an accident, after three times I'm being tempted to consider 
it negligent.

I'd have sent a note privately but all thing duly considered I don't think 
I want to expose my e-mail address.

Robert


" 'Freedom' has no meaning of itself.  There are always restrictions,
be they legal, genetic, or physical.  If you don't believe me, try to
chew a radio signal. "

                         Kelvin Throop, III

Re: NOTICE: Your e-mail to briaust@bri.com.au triggered scanning rules

2004-05-06 by leon_heller

--- In lpc2000@yahoogroups.com, Robert Adsett <subscriptions@a...> 
wrote:
> Here's hoping briaust is reading their e-mail.  Will you please 
(pretty 
> please) turn off the notification to sender on your virus detection 
> SW.  Once is an accident, after three times I'm being tempted to 
consider 
> it negligent.
> 
> I'd have sent a note privately but all thing duly considered I 
don't think 
> I want to expose my e-mail address.

The recipient doesn't belong to this group. The email must have had a 
spoofed address.

Leon

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.