Tracing An Email
|
|
Comments (1)
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
Sign up and post (it is free) or Log in and post

You also can't rely on the full Received: chain. I've seen plenty of spam with bogus Received: lines trailing the real Received: headers. You can analyze the chain for broken hops, where system-A seems not to have gotten the mail from system-B which is mentioned in the next lower Received: line, but that gets problematic unless you're willing to sit doing IP and reverse-IP lookups for everyone mentioned; not every server a message goes through will bother with such lookups, so the two mentions might resolve to the same machine after all.
The only sure way I've found to deal with those is to trust no one beyond my known chain of servers, at my ISP's outer edge and inwards to the server I fetch my mail from. If an AOL server is the next source beyond that, and the chain appears to extend for a few more AOL relays beyond before claiming to be from another domain entirely, it's still an AOL problem, because the spam got into their servers somehow, so they get the bitchmail because they need to know (assuming they care).