Well, a short circuit rule kind of breaks things in the middle so I do not
think you should really spend too much time on rules that hit/didn't hit.

I like validity but I don't think it justifies a short circuit, FYI.

Regards,
KAM
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Sun, Nov 27, 2022 at 8:19 PM Alex <mysqlstud...@gmail.com> wrote:

> Hi,
>
> > I have emails from wayfair and Dell that hit many of the MISSING_*
>>> > rules
>>> > but these headers are clearly displayed.
>>> >
>>> >  *  0.5 MISSING_MID Missing Message-Id: header
>>> >  *  1.0 MISSING_FROM Missing From: header
>>> >  *  1.8 MISSING_SUBJECT Missing Subject: header
>>> >  *  1.4 MISSING_DATE Missing Date: header
>>> >  *  2.3 EMPTY_MESSAGE Message appears to have no textual parts and no
>>> >  *      Subject: text
>>> >
>>> > This also consequently causes DMARC/DKIM to fail.
>>> >
>>> > https://pastebin.com/yFCRx76x
>>> >
>>> > $ spamassassin --version
>>> > SpamAssassin version 4.0.0-r1904221
>>> >   running on Perl version 5.36.0
>>>
>>> Cannot reproduce. Pasting a copy of that from the 'raw' view and feeding
>>> it to 'spamassassin  -t' doesn't result in hits on any of those rules.
>>>
>>> How are you calling SA?
>>>
>>> I have a theory about what might be happening, but it would require
>>> using report_safe=1 and a flow that passes twice through SA...
>>>
>>
>> I'm calling SA through amavis, but it happens even when running SA from
>> the command-line:
>>
>> $ spamassassin -t < email.eml
>>
>> I do actually notice it does print the rules that are triggered twice,
>> but I don't think the scores are duplicated.
>>
>> report_safe=1 is set in 10_defaults.pref in the updates.spamassassin.org
>> ruleset.
>>
>
> It has something to do with this shortcircuit rule I added to my local.cf
> some time ago:
>
> shortcircuit RCVD_IN_VALIDITY_SAFE on
>
> Commenting this out results in normal operation. Any idea how that could
> possibly happen?!
>
>
>

Reply via email to