http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5666
------- Additional Comments From [EMAIL PROTECTED] 2008-01-12 09:40 -------
After some more looking and thinking and discussing, I've come to a different
viewpoint. Looking at the comment in 20_ratware.cf for __UNUSABLE_MSGID, I see
> # Dec 17 2002 jm: this means "message ID is either too old or has been
> # rewritten by a gateway". Made into an eval test since meta tests cannot
> # (yet) chain from other meta tests.
> header __UNUSABLE_MSGID eval:check_messageid_not_usable()"
It looks like this is meant to be a meta rule that collects the Message-ID
formats that are allowed to be exceptions to any Message-ID based forgery rule.
Since meta tests _can_ now be chained from other meta tests (such as meta
__FORGED_OE being part of the definition of meta FORGED_MUA_OUTLOOK) shouldn't
we be able to now make __UNUSABLE_MSGID a meta rule? And then it could encompass
the tests we now have in __OE_MSGID_3 and __OE_MSGID_4.
Where I went wrong in comment #15 is that I was assuming that FORGED_MUA_OUTLOOK
is just testing for the Message-ID being of a format that is produced by OE/OL,
and therefore should not hit when the Message-ID is added later by the MTA.
That's wrong. We are using whitelist filtering, in which FORGED_MUA_OUTLOOK hits
whenever there is an unrecognized Message-ID for any reason except for the known
good cases.
So how about we replace the eval rule __UNUSABLE_MSGID with a meta of a few
header rules including the tests of __OE_MSGID_3 and __OE_MSGID_4? Am I wrong in
my assumption that we now can chain meta rules and the restriction in the
comment no longer applies?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
