RE: [SAtalk] Exessive HTML Code

2003-10-30 Thread Larry Gilson
Hi Mark, > -Original Message- > From: Mark Ritchie [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 29, 2003 9:46 AM > To: [EMAIL PROTECTED] > Subject: RE: [SAtalk] Exessive HTML Code > > > > > Do you really think it would be a problem if we found m

RE: [SAtalk] Exessive HTML Code

2003-10-30 Thread Larry Gilson
Thanks Jennifer! I should have know you would be on top of this. --Larry > -Original Message- > From: Jennifer Wheeler > Sent: Wednesday, October 29, 2003 11:11 AM > To: 'Larry Gilson'; 'Mark Ritchie'; > [EMAIL PROTECTED] > Subject: RE: [SAtalk]

RE: [0.6] [SAtalk] Exessive HTML Code

2003-10-29 Thread Chris Santerre
> > On Wed, 29 Oct 2003, Mark Ritchie wrote: > > Now, as you can see the trick here to fool spamassassin is > the and > > tags. Would it be possible to make a rule or adjust > the rules so > > the scores high? There is nothing inbetween and I'd have to > > say anyone sending messages like

RE: [SAtalk] Exessive HTML Code

2003-10-29 Thread Jennifer Wheeler
Perhaps it's time for a new set. That would be an easy technique to stop them from using lest they get tagged. When I get some time, I'll play around. Jennifer > -Original Message- > From: Mark Ritchie [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 29, 2003 8:14 A

Re: [0.6] [SAtalk] Exessive HTML Code

2003-10-29 Thread Charles Gregory
On Wed, 29 Oct 2003, Mark Ritchie wrote: > Now, as you can see the trick here to fool spamassassin is the and > tags. Would it be possible to make a rule or adjust the rules so > the scores high? There is nothing inbetween and I'd have to > say anyone sending messages like this is obviously a

RE: [SAtalk] Exessive HTML Code

2003-10-29 Thread Bill
> > Do you really think it would be a problem if we found more > than 3 instances of in each email to mark it as spam? > Maybe I could just score it lower per instance, say .2 > > There were 58 instances of in this email and 63 > instances of . > A test that counted .1 per instance in a me

RE: [SAtalk] Exessive HTML Code

2003-10-29 Thread Yackley, Matt
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Ritchie Sent: Wednesday, October 29, 2003 7:14 AM To: [EMAIL PROTECTED] Subject: [SAtalk] Exessive HTML Code I've added the popcorn, blackhair, and weeds rules a while back, but

RE: [SAtalk] Exessive HTML Code

2003-10-29 Thread Scott Sprunger
I did find a single test in 20_head_tests.cf called TO_ADDRESS_EQ_REAL that uses backreferences in this way, so I'm presuming it works. -- Scott -Original Message- From: Mark Ritchie [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 29, 2003 8:14 AM To: [EMAIL PROTECTED] Subject:

RE: [SAtalk] Exessive HTML Code

2003-10-29 Thread Mark Ritchie
:[EMAIL PROTECTED] Sent: Wednesday, October 29, 2003 9:35 AM To: Mark Ritchie; [EMAIL PROTECTED] Subject: RE: [SAtalk] Exessive HTML Code Yes, this would be possible. describe MY_RBDY_EXSV_TAGMY: Excessive HTML Tags rawbody MY_RBDY_EXSV_TAG/<[bi]><\/[bi]>/i scoreMY_RBDY_EXS

RE: [SAtalk] Exessive HTML Code

2003-10-29 Thread Larry Gilson
IL PROTECTED] Subject: [SAtalk] Exessive HTML Code I've added the popcorn, blackhair, and weeds rules a while back, but I've noticed that I'm still getting quite a few spams messages per day. It always seems to be the most offensive porn and such that makes it through. Here is an

Re: [SAtalk] Exessive HTML Code

2003-10-29 Thread Keith C. Ivey
Mark Ritchie <[EMAIL PROTECTED]> wrote: > Now, as you can see the trick here to fool spamassassin is the > and tags. I don't think that's what's fooling SA. SA strips all that stuff out before looking for phrases. The problem is the lack of phrases to trigger on. > Would it be possible to

[SAtalk] Exessive HTML Code

2003-10-29 Thread Mark Ritchie
I've added the popcorn, blackhair, and weeds rules a while back, but I've noticed that I'm still getting quite a few spams messages per day.  It always seems to be the most offensive porn and such that makes it through.   Here is an example of the source that get's through   NOT mature,