>>Received: from houseoffusion.com ([64.118.64.245]) by field.videotron.net
>>.............
>>Received: from announced_name ([true_ip]) by receiving_computer
.............
As your computer network is the receiving computer and the HoF server is the
sending computer, they should not be the same.
Sure, but since my ISP declares that he received the message FROM houseoffusion.com
I expect the previous server, if there is one, to be houseoffusion.com, not LOCALHOST.
Then the following line (actually the previous server should contain "by houseoffusion.com", no?
>>The second received line is due to internal processing and can be ignored.
Ok, but if the processing generates a received line, it means that it is a server who received the message, and it should identify itself properly. In other words, it should add a line compliant with RFC 821.
Anyway, I just gave up with the idea of checking the headers: it appears that many networks, like yahoo for instance, generate completely erroneous headers anyway. Headers forged by spammers look more natural!
When ISP are not even able to comply to RFCs, what can we do?
>>When I do spam scanning, I only look at the first received line.
Since this line is generated by my ISP, I know it is correct.
The other lines are important.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
