On Wed, 21 Mar 2012, Axb wrote:
the MSGID_MULTIPLE_AT hits mostly ham using newish MS MUAs and seems like
pointless bloat.
Hits every other message and give a recipient a fuzzy feeling when rcpt see
this hit so often
(sic: all my messages are spam because of MSGID_MULTIPLE_AT !!)
http://ruleqa.spamassassin.org/20120320-r1302798-n/MSGID_MULTIPLE_AT/detail
The few spam hits from the axb corpus don't warrant this to be kept.
Many moons ago it was a usefull spam trait, but that was way before Microsoft
started using it in their MUAs
Could we remove this rule?
Comments?
+1 for removal?
-1 for removal?
Part of me says "the corpus über alles" and +1 for removal.
Another part of me says "it violates the standards" and -1 for removal.
But most of me says "+1 for driving down to Redmond and beating the
ignorance out of the MSFT mail dev group using bronzed copies of RFC5322".
Seriously, I think we've agreed long since that SA is not a
standards-compliance audit tool regardless of how much some of us wish it
to be, so if the corpus says it's performing poorly then +1 for removal as
a scored rule.
We may want to convert it to a subrule. I'd have to perform a combination
analysis to see whether it's useful with other rules.
My final vote: +1 for converting it to a subrule.
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
[email protected] FALaholic #11174 pgpk -a [email protected]
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
North Korea: the only country in the world where people would risk
execution to flee to communist China. -- Ride Fast
-----------------------------------------------------------------------
468 days since the first successful private orbital launch (SpaceX)
