Hi
the "t-online" here is one of the major providers here. I would assume they can be trusted (at least to the point that they do not invent received lines) So the next hop is yahoo I do, however, believe that their abuse desk does not want to be bothered too much about emails Wolfgang Hamann >> >> [EMAIL PROTECTED] a écrit : >> > Hi, >> > >> > I recently received some mail from yahoo and complainedd about it, >> > on the assumption that "received with login" means one of their valid >> > customers >> > was using their mailserver. >> >> This assumption is invalid and useless. Focus on the hops in the >> received headers instead. >> >> [snip] >> >> >>>Received: from mailin14.aul.t-online.de (mailin14.aul.t-online.de >> >>>[172.20.26.71]) >> >>> by mhead22 with LMTP; Wed, 25 Jan 2006 16:09:06 +0100 >> >> Now it all depends on whether this header is "trusted" or not. said >> otherwise, do you trust 172.20.26.71? (administrative trust, not >> compromised, ...). If you trust it, then you can check the next headers. >> Otherwise, the next headers may be forged. >> >> This may be the point to make clear with yahoo (after you have clear >> args for them). >> >> >>>X-Sieve: CMU Sieve 2.2 >> >>>Received: from smtp106.biz.mail.re2.yahoo.com ([206.190.52.175]) by >> >>>mailin14.sul.t-online.de >> >>> with smtp id 1F1mCc-20oHIm0; Wed, 25 Jan 2006 16:04:54 +0100 >> >> so if you trust 172.20.26.71, then it passed through yahoo network. >> >> # host 206.190.52.175 >> .... smtp106.biz.mail.re2.yahoo.com >> # whois 206.190.52.175 >> ... >> OrgName: Yahoo! Broadcast Services, Inc. >> OrgID: YAHO >> ... >> OrgAbuseEmail: [EMAIL PROTECTED] >>
