[Scspamcop] Re: SpamCop Parsing hangs when non-Reportable sites in spam?

[Mike Easter]

Tim McGraw wrote:
> Petzl wrote:
>>
http://www.spamcop.net/sc?id=z1603007598zcff1d582ac1f6b3d1dc83165f92c43dbz
>
> I see that this parse works now... did you ever hear back? Or did the
> sc gnomes just fix it?

In order for SC to determine the hanaro notify for the spamvertiser, it
would have to access apnic (or krnic which it is designed to only know
about if apnic tells it so).

SC cannot always access whois.apnic -- when it can, it looks like this:

Tracking details
Display data:
"whois 116.122.193.194 at whois.arin.net" (Getting contact from
whois.arin.net )
   Redirect to apnic:
   "whois 116.122.193.194 at whois.apnic.net" (Getting contact from
whois.apnic.net mirror)
   Display data:
      whois.apnic.net redirects to krnic
      Display data:
      "whois 116.122.193.194 at whois.krnic.net" (Getting contact from
whois.krnic.net) (old krnic) Found ISP IPv4 Admin Contact Information :
ip-adm at hanaro.com
      Found ISP IPv4 Tech Contact Information : ip-adm at hanaro.com
      Found ISP Network Abuse Contact Information : abuse at hanaro.com

Assuming /24 network for cache
      whois: 116.122.193.0 - 116.122.193.255 : abuse at hanaro.com,
ip-adm at hanaro.com
Routing details for 116.122.193.194
Using abuse net on abuse at hanaro.com
abuse net hanaro.com = abuse at hanaro.com, cert at certcc.or.kr,
spamcop at kisa.or.kr
Using best contacts abuse at hanaro.com cert at certcc.or.kr
spamcop at kisa.or.kr
cert at certcc.or.kr redirects to spamrelay at certcc.or.kr


Petzl wrote:
> I think the "look-up" is what is causing the hang
> host 116.122.193.194 (getting name) no name

That lookup part isn't causing the problem;  the weak spot is SC
accessing apnic.

> No reporting addresses found for 116.122.193.194, using devnull for
> tracking.

Alternatively, SC could've accessed apnic before, but the apnic
configuration/ data population/ wasn't adequate.

You can tell the difference at the time of the parse by clicking on the
link called

Resolves to 116.122.193.194
Routing details for 116.122.193.194
[refresh/show]

... where lines 2 & 3 are/ link to a display/ what the parser sees at
the time of the parse, as is pasted above under 'tracking details'.


-- 
Mike Easter
kibitzer, not SC admin