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

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

    By Snowbat,
    • 0 replies
    • 256 views

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

    By Snowbat,
    • 0 replies
    • 285 views

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

    By Snowbat,
    • 0 replies
    • 266 views

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

    By Snowbat,
    • 0 replies
    • 295 views

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

    By Snowbat,
    • 0 replies
    • 318 views

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

    By Snowbat,
    • 0 replies
    • 281 views

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

    By Snowbat,
    • 0 replies
    • 280 views

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

    By Snowbat,
    • 0 replies
    • 253 views

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

    By Snowbat,
    • 0 replies
    • 283 views

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

    By Snowbat,
    • 0 replies
    • 268 views

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

    By Snowbat,
    • 0 replies
    • 284 views

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

    By Snowbat,
    • 0 replies
    • 287 views

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

    By Snowbat,
    • 0 replies
    • 259 views

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

    By Snowbat,
    • 0 replies
    • 307 views

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

    By Snowbat,
    • 2 replies
    • 323 views

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

    By Snowbat,
    • 0 replies
    • 266 views

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

    By RobiBue,   
    • 0 replies
    • 375 views

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

    By ob1db,
    • 1 reply
    • 333 views

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

    By ob1db,
    • 3 replies
    • 402 views

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

    By Snowbat,
    • 1 reply
    • 292 views

  21. parsing errors

    By karl,
    • 2 replies
    • 360 views

  22. No reporting address found for 102.221.231.56

    By Steve,
    • 2 replies
    • 387 views

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

    By lartingyou,
    • 0 replies
    • 1.5k views

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

    By DRSpalding,
    • 1 reply
    • 530 views

  25. amazonaws.com now accepting reports

    By ob1db,
    • 2 replies
    • 499 views
×
×
  • Create New...