On Mon, 2007-01-29 at 14:10 -0700, Philip Prindeville wrote: > But that's exactly the point, isn't it? > > That I'm pointing out to the ISP conclusively that the message > came to me, via them... in the logs showing that the connection's > remote end-point was X.X.X.X. They are saying "That's not > enough, we need headers [and/or the complete message]." > > If they want to know where it originated, then they will have to > go through *their* logs and follow the bread-crumb trail > back to the point of origin. > > Having to present all of the headers (or, really, just the Received: > headers) isn't reliable for the very reason that you point out: > they can be forged. > > Logs can't.
Why can't logs be forged?
signature.asc
Description: This is a digitally signed message part
_______________________________________________ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list [email protected] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
