Jump to content

Magna atque magnifica Oz

Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Magna atque magnifica Oz

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Magna atque magnifica Oz

    ipv6 still unsupported?

    Well, not exactly bogus, but not a routeable IP address either. The 2002 range was reserved for IPv4 tunneling. The two 16-bit numbers following the 2002 represent the IPv4 address with the last 16-bit number being a subset on that address. So 2002:a17:902:xxxx translates to: 0a.17.09.02 or in decimal 10.23.9.2, which is also a non-routeable address. My best guess is that Gmail is using these 10.xxx.xxx.xxx addresses to internally route emails through their network. If you're interested, just do a search on the term 6to4 for more information on this tunneling thing, reviews from people who find it a pain in the neck, along with others who have a much lower opinion of it.
  2. Magna atque magnifica Oz

    No unique hostname found for source

    Update: The situation is getting worse. It started with only ISPs on the Asia/Pacific rim, and now it's cropping up in spams from ISPs in the continental U.S. Half of the spam emails I received today were unreportable because of this.
  3. Magna atque magnifica Oz

    ipv6 still unsupported?

    Actually, it's this line that's the crux of the problem: X-Received: by 2002:a17:902:6881:: with SMTP id i1-v6mr7121788plk.323.1516767567431; Tue, 23 Jan 2018 20:19:27 -0800 (PST) If you were to cut it out, then I'm sure the parser would work properly. But, as you pointed out, that's a no no, which is why I didn't suggest it in the first place. I don't even know why that line is parsed because X-Received is non-standard and somewhat untrustworthy. Until some action is taken by Spamcop, there's nothing we can do.
  4. Magna atque magnifica Oz

    No unique hostname found for source

    Not really. I have some old Gmail messages from 2013 with the same type of X-Received field. It seems to be an unintended consequence of the transition to ipv6 which Spamcop was unprepared to deal with. Understandable, because this IP range was designated for private use, and Spamcop would have no reason to expect to see them.
  5. Magna atque magnifica Oz

    ipv6 still unsupported?

    This seems to be a problem within Spamcop and not a question of registering the mailhost. The thing is 2002:a17:902:6881:0:0:0:0 is not a valid ipv6 address and never will be. The 2002 range is reserved for transitioning between ipv6 and ipv4. The 2002 is a flag value followed by the ipv 4 address (a17:902) and the following 6881 is a subnet address. In this case, the ipv4 address works out to 10.23.9.2, which is the Internet Assigned Numbers Authority (IANA). I believe that if you look at the headers of any of your other gmail messages, you'll find that any X-Received line that doesn't start with 2002: will start with 10. As far as I can tell, it's something that Gmail uses internally and has nothing to do with the email source. With the ongoing transitioning to ipv6, this issue is likely to pop up more often. Unfortunately there seems to be nothing that we users can do until the people at Spamcop tweak the parser to deal with these 2002 range addresses. FYI: The actual IP that your spam came from was 113.23.219.233 which is located in Malaysia. It's starting to look like all these errors are occurring when Gmail receives spam from Asian countries along the Pacific coast.
  6. Magna atque magnifica Oz

    No unique hostname found for source

    Yes. That's what I meant when I said I went through the Spamcop registration process again. Sorry if I was unclear. It's cropped up again with invision7.com, and ISP out of Malaysia. So, for the moment, it seems to be isolated to ISPs in east asia. I am certain that the problem originates with the X-Received line that Gmail throws into its headers. The usual ipv4 10.xxx.xxx.xxx works fine, but an ipv6 address seems to give the parser indigestion. The X-Received line is the ONLY place that the ipv6 address appears in these problem emails. While composing this message, I did some digging, and discovered that the ipv6 address that's been causing me grief ( 2002:a17:902: xxxx) is reserved for 6to4 conversion and translates, interestingly enough, back to ipv4 10.xxx.xxx.xxx. So, it's starting to look like an oversight in the parser where the 6to4 conversion is concerned.
  7. Magna atque magnifica Oz

    No unique hostname found for source

    Hello, A few days ago, I started encountering spam messages which cannot be processed due to what appears to be a problem with resolving an ipv6 address. Here is the tracking link: https://www.spamcop.net/sc?id=z6437392727zd5176b494aaf328f9c8ad3ba8a7727ebz The error I received with this particular one was: No unique hostname found for source: 2002:a17:902:aa4a:0:0:0:0 Possible forgery. Supposed receiving system not associated with any of your mailhosts Will not trust this Received line. Mailhost configuration problem, identified internal IP as source The receiving account is a gmail account, and the sending IP (according to gmail) is 114.147.58.100, which belongs to ocn.ad.jp aka the ISP from Hell. There are also numerous references to ocn throughout the header, so I am confident that they are the source. The only place that the aforementioned ipv6 address occurs in the entire header is a single X-Received: line. Every gmail message I've checked has an X-Received: line (invariably with a 10.xxx.xxx.xxx IP address), so I don't know if it's a google error, or if ocn spammers have figured out how to spoof this field, or if the problem is internal to Spamcop. I couldn't find anybody having a similar problem in the forum. I even tried going through the spamcop registration process again, but that didn't solve the problem. The only thing that seems consistent is that these errors only occur with spams sent from ocn. Hopefully, somebody out there has some ideas.
×