>...
>
>Sorry, it still.
>
>---
>Received: from mail.indorama.com (blowfish [127.0.0.1])
> by localhost.localdomain (Postfix) with ESMTP id 30451E7933
> for <[EMAIL PROTECTED]>; Wed, 31 Aug 2005 13:08:51 +0700 (WIT)
>X-Greylist: domain auto-whitelisted by SQLgrey-1.6.5
>Received: from n3.bulk.dcn.yahoo.com (n3.bulk.dcn.yahoo.com
>[216.155.201.68])
> by mail.indorama.com (Postfix) with SMTP id D69B4E7932
> for <[EMAIL PROTECTED]>; Wed, 31 Aug 2005 13:08:43 +0700 (WIT)
>...
>X-Spam-Status: Yes, score=9.0 required=5.2 tests=BAYES_99,FORGED_YAHOO_RCVD,
> HTML_80_90,HTML_FONT_BIG,HTML_MESSAGE,HTML_NONELEMENT_00_10,
> MANY_EXCLAMATIONS,MSGID_FROM_MTA_ID,NO_REAL_NAME,WHY_WAIT
> autolearn=disabled version=3.0.4
>X-Spam-Report:
> * 0.0 NO_REAL_NAME From: does not include a real name
> * 1.7 MSGID_FROM_MTA_ID Message-Id for external message added
>locally
> * 2.7 FORGED_YAHOO_RCVD 'From' yahoo.com does not match
>'Received' headers
>
>
>--
>
>--beast
>
>
I think the cases of "scd" and "mud" were handled in 3.0.4. It
looks like you got a new Yahoo! server group here, "dcn" - another case
needs to be added to the alternation on line 517 of EvalTests.pm; The case
of 'mailer.bulk.scd' is covered, but you got 'n3.bulk.dcn' - the test should
probably be expanded to "(mailer|n\d+)\.bulk\.(dcn|mud|scd)" from the current
"mailer\d+\.bulk\.scd". At least that will cover your case. It sure would
be nice if someone had a connection at Yahoo! to find out the naming rules
they use/intend to use (or at least be notified if they add servers). BTW.
I've seen at least one FP on a "mud" server, but I probaly deleted the
message already (FP on the rule, not the entire message, which scored as
ham and was delivered to the user).
Note: some uses of "dcn" are already handled - just not this one.
File a Bugzilla and hope for 3.1.1 or maybe 3.1.0rc3. Possibly
some of the other alternations need expanding to include "dcn" and/or
"n\d+" also!?
Paul Shupak
[EMAIL PROTECTED]
