https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6080
--- Comment #3 from Karsten Bräckelmann <[email protected]> 2009-03-03 12:19:37 PST --- (In reply to comment #2) > Our system does try to figure out if an IP is dynamic, but if an IP hasn't > been sending any spam then we won't list it...so, that /should/ be safe. Right, that's how I understood the description. Indeed, that should be fine. I specifically asked to verify the bulk-sending constraint. Other lists do explicitly list IPs merely /because/ they are end-user IPs not intended to send mail directly -- which of course is not safe for deep-parsing. If dynamic / end-user IPs do not get listed in SSBL just for sending direct to MX mail, *unless* they are sending huge volumes (as per the description), this should be good for deep-parsing as opposed to last-external only. > > What about the access policy (bottom of the page) here: > > http://www.returnpath.net/internetserviceprovider/blacklist/ > That's primarily intended for sites large enough to need zone transfers; with > SA, we'd be happy to simply get some ad-hoc feedback every now and then. > > I can get a formal exception statement written up if you think it's > necessary.... Hmm, personally I don't think I'm in a position to demand such a statement, though I sure would like to have one. :) I guess comments in here by Return Path staff are already quite official... Alternatively it might be worth clarifying the quoted policy, to specifically talk about rsync users. Just trying to eliminate any confusion about allowed usage. I for one didn't understand "all users" as limited to rsync. ;) Thanks for clarifying this, J.D. Nice to see the effort and offer. :) -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
