[OT] Why is *ro?d* bad?

[Michael Clark <mc...@cdtmail.org>]

I know this is off-topic, but I got an email message I sent blocked 
by  Symantec_AntiVirus_for_SMTP_Gateways because it matched this rule.

Matching Subject: *ro?d*

The Subject was:

Policy Post 10.04: CDT Urges FCC to Protect Internet In Defining DTV 
Broadcast Flag

What word are they trying to catch with this rule? They of course 
caught the word Broadcast. Thanks, Michael

-- 
Michael Clark, Webmaster
Center for Democracy and Technology
1634 Eye Street NW, Suite 1100
Washington, DC 20006
voice: 202-637-9800
http://www.cdt.org/

Join our Activist Network! Your participation can make a difference!
http://www.cdt.org/join/

Re: [OT] Why is *ro?d* bad?

[SRUJAN <sr...@iicindia.com>]

Its not at all a good way to write rules based on a single word.
Better have rules based on phrases.

Srujan
----- Original Message ----- 
From: "Michael Clark" <mc...@cdtmail.org>
To: <sp...@incubator.apache.org>
Sent: Friday, February 20, 2004 7:00 PM
Subject: [OT] Why is *ro?d* bad?


> I know this is off-topic, but I got an email message I sent blocked 
> by  Symantec_AntiVirus_for_SMTP_Gateways because it matched this rule.
> 
> Matching Subject: *ro?d*
> 
> The Subject was:
> 
> Policy Post 10.04: CDT Urges FCC to Protect Internet In Defining DTV 
> Broadcast Flag
> 
> What word are they trying to catch with this rule? They of course 
> caught the word Broadcast. Thanks, Michael
> 
> -- 
> Michael Clark, Webmaster
> Center for Democracy and Technology
> 1634 Eye Street NW, Suite 1100
> Washington, DC 20006
> voice: 202-637-9800
> http://www.cdt.org/
> 
> Join our Activist Network! Your participation can make a difference!
> http://www.cdt.org/join/
> 

Re: [OT] Why is *ro?d* bad?

[Bryan Britt <be...@beltane.com>]

I had to check.   I only got down to "adirondack mountains" in the first
10 of 764 hits.  This would be a good example of a poorly written rule.

Bryan Britt
Beltane Web Services


--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ICQ: 53037451
Bryan L. Britt                                        501-327-8558
Beltane Web Services, Conway, AR            http://www.beltane.com
~~~~~~~~~~Support Private Communications on the Internet~~~~~~~~~~



----------------------- Original Message -----------------------
On Fri, 20 Feb 2004 08:53:18 -0500, Matt Kettler <mk...@comcast.net> wrote:

> At 08:30 AM 2/20/04 -0500, Michael Clark wrote:
> >I know this is off-topic, but I got an email message I sent blocked 
> >by  Symantec_AntiVirus_for_SMTP_Gateways because it matched this rule.
> >
> >Matching Subject: *ro?d*
> 
> Sounds like something some foolish (albeit well intending) sysadmin added 
> without thinking about the wide range of strings that will match.
> 
> Then again, I've seen commercial scanners contain *anal* out of the box... 
> heaven forbid you should work with analog electronics or try to analyze 
> anything.

Re: [OT] Why is *ro?d* bad?

[Matt Kettler <mk...@comcast.net>]

At 08:30 AM 2/20/04 -0500, Michael Clark wrote:
>I know this is off-topic, but I got an email message I sent blocked 
>by  Symantec_AntiVirus_for_SMTP_Gateways because it matched this rule.
>
>Matching Subject: *ro?d*

Sounds like something some foolish (albeit well intending) sysadmin added 
without thinking about the wide range of strings that will match.

Then again, I've seen commercial scanners contain *anal* out of the box... 
heaven forbid you should work with analog electronics or try to analyze 
anything.