Yehuda

Members
  • Content count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Yehuda

  • Rank
    Newbie
  • Birthday
  1. As a network security researcher, I was just concerned about information leaking out of SpamCop's network that should not be. If it is OK with them, I don't care.
  2. The report I saw this on is https://www.spamcop.net/sc?id=z6332425923zc5dcf71a8dc85a020ff6d1200f7901ccz I can also create a fake report with arbitrary IP addresses: Received: from [192.168.1.254] (helo=wuvb) by aestrada.com with esmtpa (Exim 4.60) (envelope-from <Aratbbvf@outlook.com>) id 1c6dSa-0004Rm-05; Tue, 15 Nov 2016 14:07:54 +0100 Received: from [192.168.1.1] (helo=wuvb) by aestrada.com with esmtpa (Exim 4.60) (envelope-from <Aratbbvf@outlook.com>) id 1c6dSa-0004Rm-05; Tue, 15 Nov 2016 14:07:54 +0100 This gives me: host 192.168.1.254 = netscreen-dig.ironport.com (cached) netscreen-dig.ironport.com is 192.168.1.254 host 192.168.1.1 = juggler-dig.ironport.com (cached) juggler-dig.ironport.com is 192.168.1.1
  3. If I remember correctly, spamcop used to recognize private IP addresses as private and throw them out. Now it appears (no idea how long this has been going on) that it is trying DNS resolution on private IP addresses. host 192.168.1.254 = netscreen-dig.ironport.com (cached) netscreen-dig.ironport.com is 192.168.1.254 I wasnt sure the forum is the right place for this, but i couldnt find anywhere else.