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

  1. parsing errors

    By karl,
    • 2 replies
    • 39 views

  2. No reporting address found for 102.221.231.56

    By Steve,
    • 2 replies
    • 43 views

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

    By lartingyou,
    • 0 replies
    • 46 views

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

    By DRSpalding,
    • 1 reply
    • 106 views

  5. amazonaws.com now accepting reports

    By ob1db,
    • 2 replies
    • 78 views

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

    By cwg,
    • 0 replies
    • 64 views

  7. forwarded spam being returned

    By randallw,
    • 2 replies
    • 119 views

  8. alsonmedia, maybe incorrect reporting address?

    By Jank1887,
    • 3 replies
    • 124 views

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

    By Steve,
    • 2 replies
    • 117 views

  10. 182.160.128.0 - 182.160.191.255: route changed since manual entry

    By gnarlymarley,
    • 0 replies
    • 140 views

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

    By Snowbat,
    • 0 replies
    • 89 views

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

    By Snowbat,
    • 0 replies
    • 113 views

  13. MTA version parsed as IP address

    By Tesseract,
    • 7 replies
    • 371 views

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

    By Snowbat,
    • 5 replies
    • 227 views

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

    By Snowbat,
    • 2 replies
    • 155 views

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

    By Snowbat,
    • 3 replies
    • 218 views

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

    By Snowbat,
    • 1 reply
    • 113 views

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

    By Snowbat,
    • 1 reply
    • 116 views

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

    By Snowbat,
    • 0 replies
    • 185 views

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

    By Snowbat,
    • 0 replies
    • 180 views

  21. 13.67.72.254 - "Using rdns to route to correct Microsoft department" but reports go to the spammer

    By Snowbat,
    • 0 replies
    • 192 views

  22. No reporting addresses found for 210.227.118.83, using devnull for tracking.

    By Steve,
    • 1 reply
    • 313 views

  23. spam from 193.142.146.221

    By C2H5OH,
    • 1 reply
    • 285 views

  24. Not receiving emails with my submissions

    By mike20878,
    • 9 replies
    • 372 views

  25. Alot of my spam is is being reported to google?

    By denby,
    • 1 reply
    • 639 views
×