This would FP on messages that include ID's in the subject such as receipts, and also base64 encoded subjects, some of which are perfectly valid and Declude doesn't decode subjects at this time. I also tend to see receipts with more characters than I tend to see in spam that appends gibberish.
I don't think this could be made reliable without a good deal of error detection. GIBBERISHSUB actually would be a lot more reliable.
Matt
John Tolmachoff (Lists) wrote:
Test suggestion.
This would be like SUBJECTSPACES, instead would count consecutive characters other than spaces in the subject line.
CONSECUTIVECHAR consecutivechar 20 x 5 0
John Tolmachoff Engineer/Consultant/Owner eServices For You
--- [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.
