>>I just don't care when when backscatter is directed to nonexistent >>addresses, that's not a problem. Problem is when a user start getting >>thousand bounces per hour, with all kind of exotic messages. And I'm >>trying >>to keep his mailbox readable. > > >Fine, its not a problem for you. But obviously others did not >implement user validation at the front end (ASSP). So I was talking >here to these "others". > >I also running my own backscatter prevention system, so we both have >our nice systems.
Ok, I thought that was obvious, it's quite easy not to generate backscatter and filter mail directed to not-existent users. What I find a little more complex is to filter backscatter when it's directed to valid mailboxes. My plain strategy is : - Always Filter mail with forged message-id in body (often ndn etc quote original headers, and I know what my real message-id look like) - create a list with most of MTAs my clients use (hundreds different hosts) and use for ISPIP - regex/spambomb NOT for ispip - block (mostly per subject) backscatter/ndn/etc. Right now the first step can't be done per all mail, but is subject to ispip whitelisting. Will you share your magic BackscatterPreventionSystem with us fritz ? ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
