http://bugzilla.spamassassin.org/show_bug.cgi?id=4080
------- Additional Comments From [EMAIL PROTECTED] 2005-01-29 04:22 -------
Subject: Re: FORGED_YAHOO_RCVD triggers false positives.
I haven't seen the "mud" listings, but my original report (or one
of the attachments) notes the dependency of Yahoo!'s use of qmail. In the
best of circumstances, someone from the SA project could try to ask Yahoo!
if they would be wiling to notify the project when they add new server "classes"
(re. subdomains) or change the method of generating headers - It should be
relatively infrequent, but they could have many reasons for not wanting to
make their internal policies explicitly known. Still, Yahoo! has a strong
anti-spam reputation and anyone trying to prevent misuse of their trademarks
is probably someone they would consider working with (i.e SA).
Rather than create a new report, could you just add an attachment with
a modified regexp including a clause like... - oops, I see someone already has.
Longer term, an array of expressions, which are all checked is probably
a more maintainable solution than added lines of code for each case. Also, the
various subdomains in use should probably be checked with a single regexp using
alternation (e.g. 'mud|scd|') instead of multiple cases which all require
separate
return clauses (and multiple statements in the code) - I think otherwise there
is
the risk of the code becoming difficult to maintain as the "special" cases' code
grows larger and larger with each new subdomain added.
Thanks for the update,
Paul Shupak
[EMAIL PROTECTED]
P.S. The "\S+"'s in most of these expressions are probably better represented
as "\d+"'s since they always seem to be numbers (ex. "web767.mail.yahoo.com",
never "webxyz.mail.yahoo.com"), but I admit to having just copied the original
convention used by the other existing cases.
P.P.S. Sorry for "top-posting", but I often do for short messages.
>>From [EMAIL PROTECTED] Fri Jan 28 20:02:27 2005
>From: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>Subject: [Bug 4080] FORGED_YAHOO_RCVD triggers false positives.
>In-Reply-To: <[EMAIL PROTECTED]>
>References: <[EMAIL PROTECTED]>
>X-Bugzilla-Reason: Reporter
>Date: Fri, 28 Jan 2005 20:01:47 -0800 (PST)
>
>http://bugzilla.spamassassin.org/show_bug.cgi?id=4080
>
>
>
>
>
>------- Additional Comments From [EMAIL PROTECTED] 2005-01-28 20:01 -------
>Created an attachment (id=2633)
--> (http://bugzilla.spamassassin.org/attachment.cgi?id=2633&action=view)
> --> (http://bugzilla.spamassassin.org/attachment.cgi?id=2633&action=view)
>Fix for a different forged_yahoo FP
>
>This adds recognition for some new yahoo hostnames in the received header.
>Namely, the web*.mail.mud.yahoo.com ones. It's very much related to the
>original bug filed here. If you wish, I can create a new bug report, but I
>think this can be collapsed together in the "Yahoo mail hostname update".
>
>By the way, is there a formal process to revisit these sorts of "manual
>hotwired" checks periodically?
>
>
>
>
>------- You are receiving this mail because: -------
>You reported the bug, or are watching the reporter.
>
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
