"Martin G. Diehl" <[email protected]> wrote: > Greetings, > > I see a lot of SPAM with garbage Subject and/or > garbage in the From and/or Reply-To name fields. > > Here are some recent examples that were NOT flagged > as ***SPAM*** ... > > -1- > > From: "±è³ÝºÏ" <[email protected]> > Reply-To: "±è³ÝºÏ" <[email protected]> > Subject: ¹«·á¹Ì´Ï³ëÆ®ºÏÀÌ µµÂøÇß½À´Ï´Ù! > > -2- > > From: "ÇÖÀ̽´" <[email protected]> > Reply-To: "ÇÖÀ̽´" <[email protected]> > Subject: ¿ä±ÝÀý¾àÇÏ°í Çö±Ýµµ ¹ÞÀÚ!! > > -3- > > From: "ÇÖÀ̽´" <[email protected]> > Reply-To: "ÇÖÀ̽´" <[email protected]> > Subject: Çö±Ý 5¸¸¿ø ¹Þ¾Æ°¡¼¼¿ä~~ > > -4- > > From: "Èñ¸ÁÀüµµ»ç" <[email protected]> > Reply-To: "Èñ¸ÁÀüµµ»ç" <[email protected]> > Subject: °³ÀÎ, ±â¾÷ ȸ»ýÆÄ»ê µµ¿Íµå¸³´Ï´Ù. > > Looks like the SPAMers are using buggy software ... > but I doubt that we could get them to upgrade. > > I realize that something that my eye can easily identify > as bogus may not be as easy for software to identify ... > > OTOH, it might be as simple as identifying the number of > characters that are not in [a..z, A..Z] versus the number > that are in [a..z, A..Z] ... > > Comments, please ...
Are not they covered by SUBJECT_NEEDS_ENCODING test? 20_head_tests.cf: header __SUBJECT_NEEDS_MIME Subject =~ /[\x00-\x08\x0b\x0c\x0e-\x1f\x7f-\xff]/ 72_active.cf: meta SUBJECT_NEEDS_ENCODING (!__SUBJECT_ENCODED_B64 && !__SUBJECT_ENCODED_QP) && __SUBJECT_NEEDS_MIME -- [pl>en: Andrew] Andrzej Adam Filip : [email protected] A banker is a fellow who lends you his umbrella when the sun is shining and wants it back the minute it begins to rain. -- Mark Twain
