> > This was an old, old feature request/bug fix from back in the > > Scott days, where it was desired not include encoded base64 > > I requested this as a change long ago for two reasons: > > 1) To avoid false positives where search text matches the MIME or UUENCODE > formatting > > 2) To provide an instant speed up in BODY and ANYWHERE processing because > Declude has less text to match, in particular when MIME encoding text is > being searched for, say, an encoded PDF, DOC or JPG. > > It may also have the additional benefit of being more accurate: > > 3) To provide for fewer false negatives, because the string size is more > complete with the body text.
Giving a third to what Andrew and Matt have said, I have a client that deals in electronic parts. Electronic part numbers take on all forms of sequences and not being able to limit body searches to non-base64 encoding which is primarily attachments has caused a lot of extra work on my part constantly having to make adjustments to counter this problem. Being able to have BODY not include attachments is coming to the point where it is no longer a feature but a requirement. John T --- 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.
