https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7058

Bill Cole <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |INVALID

--- Comment #5 from Bill Cole <[email protected]> ---
(In reply to Pascal from comment #4)
> can you reopen the ticket please ? I don't know how to do that.
> Thank you.

I'm sorry, but no.  

Rules that are part of the dynamically managed default ruleset are activated
and deactivated based on our "RuleQA" process, whose operational details can be
found at https://ruleqa.spamassassin.org. FORGED_RELAY_MUA_TO_MX appears to be
intermittently useful enough based on the submitted scoring logs to get
promoted to the active list. I see no reason to override the automated process
in this case. 

The attached header is not usable as evidence of any problem because:

1. It is very old. We would need to see a current example. However, see #3
below

2. Attached to a dummy body, it does not score over 5.0 or anywhere near it. SA
is NOT designed with the goal of every rule only hitting spam, it is BY DESIGN
that sometimes a rule with a significant score hits non-spam. 

3. It is unclear what the actual transit path of the message was, but it
clearly was delivered AT yahoo, a circumstance that is not anticipated by the
default ruleset. The weirdness that is being caught by that rule is this:

 Received: from 127.0.0.1  (EHLO mta-meet218.mail.meetic.com) (62.23.1.218)
   by mta1403.mail.gq1.yahoo.com with SMTP; Wed, 18 Jun 2014 18:05:52 +0000

That is not a sane Received header. It is written by Yahoo, which follows its
own undocumented format. A message with that sort of header (asserting a
loopback source and a remote client simultaneously) should never be seen
anywhere except inside Yahoo or in mail forwarded out of Yahoo using SMTP
(which should not hit the active rule.) If you are going to attempt to use SA
on mail that has been delivered inside Yahoo like this one, you will need to
customize your rules to deal with that usage, as you would need to do for any
final delivery point. 

If you need assistance with how you could do that sort of customization, the
best source of help is the SpamAssassin-Users mailing list.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to