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

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

    By Snowbat,
    • 0 replies
    • 241 views

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

    By Snowbat,
    • 0 replies
    • 216 views

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

    By Snowbat,
    • 0 replies
    • 256 views

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

    By Snowbat,
    • 2 replies
    • 271 views

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

    By Snowbat,
    • 0 replies
    • 221 views

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

    By RobiBue,   
    • 0 replies
    • 322 views

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

    By ob1db,
    • 1 reply
    • 291 views

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

    By ob1db,
    • 3 replies
    • 330 views

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

    By Snowbat,
    • 1 reply
    • 240 views

  10. parsing errors

    By karl,
    • 2 replies
    • 305 views

  11. No reporting address found for 102.221.231.56

    By Steve,
    • 2 replies
    • 342 views

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

    By lartingyou,
    • 0 replies
    • 1.4k views

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

    By DRSpalding,
    • 1 reply
    • 474 views

  14. amazonaws.com now accepting reports

    By ob1db,
    • 2 replies
    • 438 views

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

    By cwg,
    • 0 replies
    • 350 views

  16. forwarded spam being returned

    By randallw,
    • 2 replies
    • 421 views

  17. alsonmedia, maybe incorrect reporting address?

    By Jank1887,
    • 3 replies
    • 499 views

  18. Sorry, no reporting addresses found for 195.208.155.243. Nothing to do.

    By Steve,
    • 2 replies
    • 380 views

  19. 51.132.220.203 - "Using rdns to route to correct Microsoft department" but reports go to spammer

    By Snowbat,
    • 0 replies
    • 352 views

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

    By Snowbat,
    • 0 replies
    • 382 views

  21. MTA version parsed as IP address

    By Tesseract,
    • 7 replies
    • 1k views

  22. 40.78.83.67 - "Using rdns to route to correct Microsoft department" but reports go to the spammer

    By Snowbat,
    • 5 replies
    • 507 views

  23. 51.120.93.44 - "Using rdns to route to correct Microsoft department" but reports go to the spammer

    By Snowbat,
    • 2 replies
    • 426 views

  24. 52.138.55.160 - "Using rdns to route to correct Microsoft" but reports go to the spammer

    By Snowbat,
    • 3 replies
    • 516 views

  25. 168.61.170.142 - "Using rdns to route to correct Microsoft department" but reports go to the spammer

    By Snowbat,
    • 1 reply
    • 384 views
×
×
  • Create New...