https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6535
--- Comment #8 from Steve Freegard <[email protected]> 2011-01-19 15:13:11 UTC --- (In reply to comment #5) > > This is not necessarily a good thing. > > For example, in my area of the country, I use my android-phone a lot and I'm > issued a DHCP address. > > If that IP was to be scanned such as by your patch above, they often come up > as > blacklisted because people have used the IPs so send Spam. > > The whole reason to authenticate, IMO, is so that the last-received relay IP > is > the only one that is checked and the other IPs would be ignored. > > Make sense? Yeah - I hadn't thought about it that way. However - this is how those particular DNSBLs (and SA) was designed; it needs to be able to parse the relevant Received headers and add the necessary metadata for rules to match on. Without SA parsing this header; I *can't* write a rule or plug-in to get this IP address out of the X-Spam-Relays-* metadata. The other problem here is how to handle these then? They're likely phished or compromised accounts. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
