Jump to content

Routing / Report Address Issues

Problems with Parser output results, such as No Reporting Address Found, wrong address provided and a Refresh Cache doesn't fix it.
Note that only Deputies can actually 'fix' the parsing results.

1,678 topics in this forum

  1. [Resolved] 212.156.91.198 -> using devnull for tracking

    By shirayuki,
    • 1 reply
    • 744 views

  2. [Resolved] 212.58.244.59

    By mrmaxx,
    • 1 reply
    • 1,014 views

  3. [Resolved] 213.92.8.132 sergio.gervasini#genieinternet.com[at]devnull.spamcop.net

    By matteo,
    • 2 replies
    • 688 views

  4. [Resolved] 217.73.224.0/20

    By mrmaxx,
    • 1 reply
    • 531 views

  5. [Resolved] 219.101.128.0/17 -> abuse[at]ultina.softbanktelecom.co.jp

    By shirayuki,
    • 1 reply
    • 700 views

  6. [Resolved] 37.143.48.0/20 - SpamCop does not fetch mnt-by object - Reports should go to abuse[at]hostingundmehr.com

    By A B,
    • 1 reply
    • 1,247 views

  7. [Resolved] 37.235.128.0/17

    By mrmaxx,
    • 1 reply
    • 536 views

  8. [Resolved] 46.151.42.66 Using gmail-abuse#google.com[at]devnull.spamcop.net for statistical tracking

    By JoeColorado,
    • 1 reply
    • 1,187 views

  9. [Resolved] 5.200.128.0/17

    By mrmaxx,
    • 1 reply
    • 615 views

  10. [Resolved] 58.69.0.0 - 58.69.255.255: SpamCop fails to get IRT ressource

    By A B,
    • 1 reply
    • 533 views

  11. [Resolved] 61.196.0.0/16 -> net-abuse[at]odn.ad.jp

    By shirayuki,
    • 1 reply
    • 1,192 views

  12. [Resolved] 67.198.152.82 -> bounces

    By shirayuki,
    • 2 replies
    • 878 views

  13. [Resolved] 69.58.188.40 Using postmaster#bitly.com[at]devnull.spamcop.net for statistical tracking.

    By Snowbat,
    • 1 reply
    • 1,894 views

  14. [Resolved] 69.89.31.124

    By petzl,
    • 1 reply
    • 582 views

  15. [Resolved] 78.131.236.0/24 abuse[at]tktelekom.pl tktelekom[at]tktelekom.pl abuse[at]telia.com

    By _aD,
    • 1 reply
    • 1,417 views

  16. [Resolved] 81.17.21.70 Using gmail-abuse#google.com[at]devnull.spamcop.net for statistical tracking

    By JoeColorado,
    • 1 reply
    • 954 views

  17. [Resolved] 82.128.62.55: multilinks[at]devnull.spamcop.net

    By Snowbat,
    • 1 reply
    • 1,538 views

  18. [Resolved] 83.149.8.182 -> using devnull for tracking

    By shirayuki,
    • 1 reply
    • 675 views

  19. [Resolved] 90.176.0.0/13 (AS5610)

    By mrmaxx,
    • 1 reply
    • 566 views

  20. [Resolved] 91.197.184.26

    By petzl,
    • 1 reply
    • 1,222 views

  21. [Resolved] 91.229.96.0/22

    By mrmaxx,
    • 1 reply
    • 567 views

  22. [Resolved] 92.70.144.73 BOTNET ATTACK HOST

    By petzl,
    • 3 replies
    • 497 views

  23. [Resolved] 94.63.245.5 going to wrong place

    By jrr7,
    • 3 replies
    • 2,815 views

  24. [Resolved] 95.168.160.0/19 -> support[at]leaseweb.de

    By shirayuki,
    • 1 reply
    • 1,077 views

  25. [Resolved] Abuse contact for '188.112.192.0 - 188.112.255.255' is 'ekonovalov[at]glomax.ru'

    By A B,
    • 1 reply
    • 481 views
×