https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6535
--- Comment #10 from Steve Freegard <[email protected]> 2011-01-19 15:45:21 UTC --- (In reply to comment #9) > Unfortunately, the only things that come to mind are to a) File a complaint > with Yahoo! abuse and b) focus on content filtering. a) Is going to be totally fruitless due to lack of clue on Yahoo's abuse desk. All complaints now have to be in ARF format and the amoeba's that look at the report will simply claim that the message didn't originate from Yahoo (despite headers to the contrary). b) Hmmm; other than score on the tripod URL (which BTW has a meta refresh to redirect to a porn site) - there's very little to content filter on. The problem here is that multiple services with poor filtering and controls are being abused to inject this stuff. One of the only tools available to us is the IP address that originated the message. Sure - it might be a host on a dial-up pool; but it's one of the only bits of useful information we have (and possibly the username of the authenticated user). The one good thing about Yahoo and the other freemailers is that you know for sure that you can 'trust' the Received headers haven't been forged. > I hope you read what I wrote a comment ago that your patch sparked an issue > that is much larger than just your patch. Sure - no problemo. Totally understand; it's a useful discussion to be having. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
