From: "jdow" <[EMAIL PROTECTED]>
> From: "Loren Wilton" <[EMAIL PROTECTED]>
>
> > > since the upgrade from spamassassin 2.61 to 3.01. i sometimes
experience
> > > a strange problem. the subject of some mails is not rewritten with
> > > *****SPAM**** even if the score is high enough and the report attached
> > > to the headers says its spam:
> > >
> > > X-Spam-Checker-Version: SpamAssassin on ianus
> > > X-Spam-Status: Yes, hits=8.0 required=5.0
> tests=BAYES_99,MISSING_HEADERS,
> > > MISSING_SUBJECT,NO_REAL_NAME,RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_XBL,
> > > SPF_SOFTFAIL autolearn=no
> >
> > This is a FAQ question, or at least should be.
> >
> > MISSING_SUBJECT - the original mail doesn't have a subject.
> >
> > SA *RE*writes headers. It doesn't *create* headers that weren't there.
> > So since there was no subject, there was no subject to rewrite, so there
> was
> > no place to put the tag.
> >
> > There is an enhancement open on this, and I had thought that it actually
> > made it in to 3.1.0 or so; but I could well be mistaken about that.
> >
> > Loren
>
> In the mean time a procmail/formail rule should be able to toss in a
> dummy subject. I'll see if I can think of what the procmail search
> string should look like. (I suspect a subject of all blanks, say 20 to
> 40 of them, would still trigger that behavior.)
>
> {^_^}
Actually it is already a ratware rule. (I just cleaned up 99_OBFU_drugs.cf
and ratware.cf. No more lint errors on 3.0.1! If the appropriate SARE
person emails me I'll send 'em in return email.)
{^_^}
