Jump to content


Recommended Posts

As the usual "notice" of this forgery is a bounce message and the rules are that one cannot report bounces, you're kind of on your own here. You can use the parser and attempt to find the real source of the stuff, but those results are pretty dependent on your knowledge of what a header should look like, what kinds of data are included in the bounce (as not all ISPs handle this in the same fashion) and send your complaint to the source ISP complaining of the forgery.

In reality, this is probably wasted effort as you're going to run up against the same old open proxy of some clueless user for the injection point or the infamous ISP that doesn't give a hoot to begin with. The legal side of it is that you could track the spammer down and press numerous charges, but ... at what cost of expense and time on your part? You could take it up with the owner/upstream/etc. of the website, but ... results probably won't happen unless there are others joining in .. and even then ...

Generally, past experience is that you're the unlucky one for a week/month/whatever, then the lowlife moves on to another poor victim.

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...