RE: [Declude.JunkMail] Cryptic URL in source

2005-11-11 Thread Dave Beckstrom
David, Could I suggest that you consider adding something along those lines or perhaps adding support for regular expressions? It would make the filters much more flexible and powerful. Sometimes spammers will vary only 1 or 2 characters in a URL and this would enable us to block their

Re: [Declude.JunkMail] Cryptic URL in source

2005-11-11 Thread Bill Landry
Take a look at SpamAssassin or the SA plug-in for Declude. Bill - Original Message - From: Dave Beckstrom [EMAIL PROTECTED] To: Declude.JunkMail@declude.com Sent: Friday, November 11, 2005 8:56 AM Subject: RE: [Declude.JunkMail] Cryptic URL in source David, Could I suggest that you

Re: [Declude.JunkMail] Cryptic URL in source

2005-11-11 Thread Darin Cox
I believe when this was broached last year, I believe Scott P. stated regexp parsing consume too much CPU for Declude. However, we added a regexp filter very easily using the built-in command line regexp parsing in Windows, thanks to Sandy pointing it out. It doesn't have all of the

Re: [Declude.JunkMail] Cryptic URL in source

2005-11-11 Thread Darrell \([EMAIL PROTECTED])
We also have a free reg-ex plug in for Declude at our site invRegex (http://www.invariantsystems.com) as said below be careful cause regex processing can get expensive depending on the regex. Darrell Check out

Re: [Declude.JunkMail] Cryptic URL in source

2005-11-11 Thread Matt
Dave, The issue here is that not only would the entire filtering mechanism need to be rewritten, but also the entire parsing mechanism. Right now Declude does minimal parsing of messages, and for instance, filters will do plain text matching on both encoded base64 as well as the unencoded

[Declude.JunkMail] yahoo and subjectchars test

2005-11-11 Thread Travis Sullivan
yahoo email and subject chars Subject: bowling To: Travis Sullivan [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=0-853569865-1131749189=:26372 Content-Transfer-Encoding: 8bit X-RBL-Warning: SUBJECTCHARS: Subject with at least 50 characters found. As

Re: [Declude.JunkMail] yahoo and subjectchars test

2005-11-11 Thread Matt
This bug was fixed in the 2.x releases. You should upgrade to 2.0.16 or higher if you wish to avoid this, or otherwise credit Yahoo E-mails for the score that you get from this test. Matt Travis Sullivan wrote: yahoo email and subject chars Subject: bowling To: Travis Sullivan

RE: [Declude.JunkMail] Looking for a mxrate contact

2005-11-11 Thread Chris Kuske
Hi Darrell, You can email me off list to address this issue. My email is chris at solidoak.com Chris Solid Oak Software, Inc. www.alligate.com www.winlocate.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darrell ([EMAIL PROTECTED]) Sent: Friday,