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,796 topics in this forum

  1. 40.71.166.2 - Microsoft netblock but SpamCop sends reports to the spammer

    By Snowbat,
    • 0 replies
    • 176 views

  2. 40.80.155.206 - Microsoft netblock but SpamCop sends reports to the spammer

    By Snowbat,
    • 0 replies
    • 208 views

  3. 13.91.129.244 - Microsoft netblock but SpamCop sends reports to the spammer

    By Snowbat,
    • 0 replies
    • 234 views

  4. 52.235.37.152 - Microsoft netblock but SpamCop sends reports to the spammer

    By Snowbat,
    • 0 replies
    • 192 views

  5. 40.112.218.153 - Microsoft netblock but SpamCop sends reports to the spammer

    By Snowbat,
    • 0 replies
    • 197 views

  6. 20.191.230.87 - Microsoft netblock but SpamCop sends reports to the spammer

    By Snowbat,
    • 0 replies
    • 171 views

  7. 20.199.120.113 - Microsoft netblock but SpamCop sends reports to the spammer

    By Snowbat,
    • 0 replies
    • 188 views

  8. 20.101.39.254 - Microsoft netblock but SpamCop sends reports to the spammer

    By Snowbat,
    • 0 replies
    • 179 views

  9. 52.229.120.216 - Microsoft netblock but SpamCop sends reports to the spammer

    By Snowbat,
    • 0 replies
    • 194 views

  10. 20.98.201.26 - "Using rdns to route to correct Microsoft department" but reports go to spammer

    By Snowbat,
    • 0 replies
    • 202 views

  11. 52.235.30.65 - "Using rdns to route to correct Microsoft department" but reports go to spammer

    By Snowbat,
    • 0 replies
    • 175 views

  12. 52.249.195.146 - "Using rdns to route to correct Microsoft department" but reports go to spammer

    By Snowbat,
    • 0 replies
    • 220 views

  13. 13.68.154.53 - "Using rdns to route to correct Microsoft department" but reports go to spammer

    By Snowbat,
    • 2 replies
    • 228 views

  14. 137.116.138.125 - "Using rdns to route to correct Microsoft department" but reports go to spammer

    By Snowbat,
    • 0 replies
    • 184 views

  15. Abuse contact for '217.79.176.0 - 217.79.191.255' is 'abuse@myloc.de'

    By RobiBue,   
    • 0 replies
    • 277 views

  16. Abuse report for www.nationalsurveysonline.com is abuse@moniker.com

    By ob1db,
    • 1 reply
    • 242 views

  17. abuse@gtt.net for IP 67.200.116.254, NOT abuse@brookstonenetworks.com

    By ob1db,
    • 3 replies
    • 270 views

  18. 40.83.112.59 - "Using rdns to route to correct Microsoft department" but reports go to spammer

    By Snowbat,
    • 1 reply
    • 200 views

  19. parsing errors

    By karl,
    • 2 replies
    • 260 views

  20. No reporting address found for 102.221.231.56

    By Steve,
    • 2 replies
    • 307 views

  21. abuse@Tinyurl.com is quick to shutdown URLs after manual LARTs, why doesn't SC use it?

    By lartingyou,
    • 0 replies
    • 1.3k views

  22. Abuse contact for '193.27.228.0 - 193.27.228.255' is 'info@starcrecium.com'

    By DRSpalding,
    • 1 reply
    • 414 views

  23. amazonaws.com now accepting reports

    By ob1db,
    • 2 replies
    • 389 views

  24. Abuse contact for '203.245.32.0 - 203.245.63.255' is 'irt@nic.or.kr'

    By cwg,
    • 0 replies
    • 296 views

  25. forwarded spam being returned

    By randallw,
    • 2 replies
    • 372 views
×
×
  • Create New...