> I'll add these to the list that I maintain as well for both the > ANTIGIBBERISHSUB and ANTIGIBBERISH filters. You shouldn't need to add > these to the base filters though since the two letter string will trip > it without any assistance.
I did not want to loose the QS, so I added the legit use of it. > I took note of your "parts" suggestion as well, but haven't yet > determined how I would like to integrate this. I've got about a month > of hits archived though for easy searching, and I have seen some FP's on > this, but only from one place if I recall correctly. I wonder how > consistent the exception would be. I have done this by putting the following line in both files: BODY 0 CONTAINS parts This way, any message with parts in it will fail both but have zero weight, and that way not be penalized for have those letters in the part numbers. Part numbers can take on many different forms, from all letters to all numbers to a varied mix. I have a client that deals in electronic parts, and both above items are actually seen in messages they receive. > I'm going to put up a new file that contains these changes as well as > exceptions for "qos", "qmail" and a few updates for mail clients that > might send out such a string that isn't marked as base64. Thanks for maintaining this. Looking forward to it. John Tolmachoff MCSE CSSA Engineer/Consultant eServices For You www.eservicesforyou.com --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
