On Wed, 29 Mar 2006 [EMAIL PROTECTED] wrote:
Received: from EXCHG01-DUB.Europe.Search.Corpsys.P4pnet.net
(cluster01-dub.europe.search.corpsys.p4pnet.net [172.30.132.19])
by mrout3.yahoo.com (8.13.4/8.13.4/y.out) with ESMTP id k2FIupeH049008;
Wed, 15 Mar 2006 10:56:52 -0800 (PST)
Hey, what do you know... if you trust both uksolutions.net and yahoo.com's
Received: lines, it didn't originate at Yahoo - it came from p4pnet.net. ;)
(A fine demonstration of the difference between being truthful and being
helpful :)
Only problem with that is 172.30.132.19 is part of
NetRange: 172.16.0.0 - 172.31.255.255
CIDR: 172.16.0.0/12
NetName: IANA-BBLK-RESERVED
So even if you did trust that Received line, it still had to come from
inside yahoo.com (unless someone briefly announced some of 172.16.0.0/12
and yahoo both accepted the route and relayed for it).
AFAIK, from other lists, Yahoo is aware of this screwup (disclaiming
responsibility for 216.145.48.0/20) and is working on it.
----------------------------------------------------------------------
Jon Lewis | I route
Senior Network Engineer | therefore you are
Atlantic Net |
_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
