https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6919
Steve Freegard <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #9 from Steve Freegard <[email protected]> --- Maybe the answer here is to try and separate dynamic .vs. generic in the RDNS_DYNAMIC rule into separate rules and mass-check them to see what effect it has. We might even find that RDNS_DYNAMIC can actually get a decent score afterwards. However I don't think we should do the same with HELO_DYNAMIC_IPADDR as this is a good spam sign and is scored accordingly (I'm frankly surprised the corpus doesn't contain more examples of this). A rename to HELO_GENERIC_IPADDR might be more appropriate. I can think of a few reasons why an admin wouldn't change the machine hostname (and therefore the EHLO/HELO used) to something that isn't generic and none of them are particularly good reasons. -- You are receiving this mail because: You are the assignee for the bug.
