At 16:17 21-02-2007, Jo Rhett wrote:
The point of sending a note about this to the mailing list is that
this problem will effect *EVERYONE* who gets crackberry messages, and
thus it could probably use a real fix instead of forcing everyone to
fix it locally.
SM wrote:
The problem affects people using the LW_STOCK_SPAM4 rule with a low
reject score when they receive blackberry messages. As mentioned
previously, LW_STOCK_SPAM4 is not a rule distributed with SpamAssassin.
And? Where oh where is the LW_STOCK_SPAM4 rule going to get fixed?
I'm really not sure what you are talking about. We could always fix
the ruleset instead of ride-em-cowboy hacking the local config on
every server...
A fix for blackberry messages opens the way for abuse. That is why
site-specific rules to reduce the score were suggested earlier in the
discussion.
No it absolutely does not. That statement has no meaning except some
emotional context you're trying to throw at it.
*EVERY* crackberry message scores on these three rulesets. Fixing the
rulesets to not MIS-FIRE on crackberry messages will only normalize mail
flow.
However, an site-custom rule to lower the score of messages with a
falsified blackberry server in the header (which is what was proposed)
will absolutely open the door to abuse.
The appropriate fix is where it is broken. 0000 is a valid timezone.
The rule is broken.
--
Jo Rhett
Network/Software Engineer
Net Consonance
