Jari Fredriksson quoted himself (both on the 17th): >> I have not yet analysed what whitehats cause this, but this rule seems >> suspipicious to me at moment. > > Now I have. Legitimate bulk mailers. > > From: "NYTimes.com" <nytdir...@nytimes.com> > From: "Iltalehti.fi" <iltalehti-288-d690018e-1000350...@sp.iltalehti.fi> > > Newspapers. And others. Guestionable rule.
Ah. Interesting. I had been suspecting either an older bug regarding foreign characters in correct proper names had resurfaced or you had a lot of correspondence with people who don't capitalize their names or include a last name. I've updated the rule so that it won't fire on any mail claiming precedence of "bulk" or "list," which should solve that issue (and unfortunately fire less often on real spam too). Keep in mind that this rule is only worth 0.259. Also note my post on the 14th: > KHOP_NO_FULL_NAME might be mis-firing. It's supposed to detect a > properly formatted name, in the form (sans quotes): "A K" or "Adam K" > or "A Katz" ... maybe somebody can find a flaw in my regex or an example > FP or FN? Here it is, please be careful decoding the wrapping: > > # This matches foreign characters by process of elimination. > # From: must start w/ ~upper, ~letters, space/punctuation, then ~upper > header __FROM_FULL_NAME From:name =~ > /^[^a-z[:punct:][:cntrl:]\d\s][^[:punct:][:cntrl:]\d\s]*[[:punct:]\s]+[^a-z[:punct:][:cntrl:]\d\s]/ > meta KHOP_NO_FULL_NAME > !(__FROM_ENCODED_QP||__FROM_NEEDS_MIME||__FROM_FULL_NAME) > describe KHOP_NO_FULL_NAME Sender does not have both First and Last > names > score KHOP_NO_FULL_NAME 0.259 # keep low!
