or get a score of 0. It's
1.72 SUBJECT_ENCODED_TWICE Subject: MIME encoded twice
From grepping the rules it does what it says: it checks if there are two
B/Q encoding identifiers in the subject. Why is this scoring with 1.72 or
at all? This is absolutely valid Q/B encoding and actually
On Donnerstag, 13. April 2006 13:35 Mark Martinec wrote:
Agreed, this rule is completely inappropriate, it penalizes valid
encoding according to RFC 2047 and fires on any lengthier Subject
line in non-English language. It should disappear or have a
much reduced default score.
The problem
On Thu, Apr 13, 2006 at 01:35:19PM +0200, Mark Martinec wrote:
Agreed, this rule is completely inappropriate, it penalizes valid
encoding according to RFC 2047 and fires on any lengthier Subject
line in non-English language. It should disappear or have a
much reduced default score.
Says you.
I just saw that a normal Ebay outbid notice hit two high-score rules. One
is from sare-spoof and I already contacted the maintainer. But one is in
the default 3.1.1 ruleset and I think this rule should get completely
removed or get a score of 0. It's
1.72 SUBJECT_ENCODED_TWICE Subject: MIME
SUBJECT_ENCODED_TWICE Subject: MIME encoded twice
From grepping the rules it does what it says: it checks if there are two
B/Q encoding identifiers in the subject. Why is this scoring with 1.72 or
at all? This is absolutely valid Q/B encoding and actually *required* by
RFC if your subject line is longer than 80
