Steve Posted March 16, 2019 Share Posted March 16, 2019 Ran an APNIC whois and cam up with these abuse contacts: Kagoya Japan, Inc/KAGOYA Network Administrator Group nss.ipadmin@kagoya.net & support.domain@kagoya.net Cached whois for 133.18.202.245 : search-apnic-not-arin@apnic.netI refuse to bother search-apnic-not-arin@apnic.net. Using search-apnic-not-arin#apnic.net@devnull.spamcop.net for statistical tracking. Using last resort contacts search-apnic-not-arin#apnic.net@devnull.spamcop.net Tracking URL: https://www.spamcop.net/sc?id=z6530520464z62ab467a37e6b02a56ca327c58498ed7z Quote Link to comment Share on other sites More sharing options...
HeatherReid43 Posted June 30, 2019 Share Posted June 30, 2019 another similar issue with IP address 171.22.120.197 points to: search-apnic-not-arin#apnic.net@devnull.spamcop.net Tracking URL https://www.spamcop.net/sc?id=z6557282707z6103b66408e567a586822dba70eec0f9z any idea how to solve this issue ? Quote Link to comment Share on other sites More sharing options...
RobiBue Posted June 30, 2019 Share Posted June 30, 2019 13 hours ago, HeatherReid43 said: Using last resort contacts search-apnic-not-arin#apnic.net@devnull.spamcop.net any idea how to solve this issue ? Unfortunately, that is not something we "mere mortal users" can solve unless we report manually and not through spamcop. This issue has to be resolved through fixing spamcop's whois lookup with the registries, and following the correct protocol, which apparently ARIN changed a while back. RIPE also seems to have made some changes, but it's affecting spamcop only marginally. Sadly many ARIN redirections to APNIC end up devnulled because cisco/talos seems to have only a minimal desire to keep spamcop up to date (at least so it seems to me personally) What happens now, is, that someone asks in this forum to fix the reporting address (which may or may not happen), and if this reporting address gets manually changed, it is then prone to end up being the wrong address when the registrant changes the info in the whois DB. Quote Link to comment Share on other sites More sharing options...
petzl Posted July 1, 2019 Share Posted July 1, 2019 Email server website hyamer.com 220 states.hyamer.com ESMTP Postfix Test Result SMTP TLS Warning - Does not support TLS. SMTP Reverse DNS Mismatch OK - 171.22.120.197 resolves to states.hyamer.com Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.