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

  1. forwarded spam being returned

    By randallw,
    • 2 replies
    • 39 views

  2. alsonmedia, maybe incorrect reporting address?

    By Jank1887,
    • 3 replies
    • 55 views

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

    By Steve,
    • 2 replies
    • 51 views

  4. 182.160.128.0 - 182.160.191.255: route changed since manual entry

    By gnarlymarley,
    • 0 replies
    • 78 views

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

    By Snowbat,
    • 0 replies
    • 39 views

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

    By Snowbat,
    • 0 replies
    • 62 views

  7. MTA version parsed as IP address

    By Tesseract,
    • 7 replies
    • 275 views

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

    By Snowbat,
    • 5 replies
    • 166 views

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

    By Snowbat,
    • 2 replies
    • 98 views

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

    By Snowbat,
    • 3 replies
    • 160 views

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

    By Snowbat,
    • 1 reply
    • 56 views

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

    By Snowbat,
    • 1 reply
    • 60 views

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

    By Snowbat,
    • 0 replies
    • 125 views

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

    By Snowbat,
    • 0 replies
    • 123 views

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

    By Snowbat,
    • 0 replies
    • 140 views

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

    By Steve,
    • 1 reply
    • 248 views

  17. spam from 193.142.146.221

    By C2H5OH,
    • 1 reply
    • 210 views

  18. Not receiving emails with my submissions

    By mike20878,
    • 9 replies
    • 296 views

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

    By denby,
    • 1 reply
    • 478 views

  20. Amazon not Verizon

    By Hanco,
    • 3 replies
    • 323 views

  21. whois 159.255.136.20@whois.ripe.net contains Abuse contact

    By shirayuki,
    • 0 replies
    • 326 views

  22. no abuse contact for 202.238.198.169 ?

    By HeatherReid43,
    • 3 replies
    • 404 views

  23. Abuse contact for 74.6.131.125 = network-abuse@cc.yahoo-inc.com

    By MIG,
    • 3 replies
    • 597 views

  24. Abuse contact for '79.175.128.0 - 79.175.191.255' is 'abuse@afranet.com'

    By AJR,
    • 1 reply
    • 341 views

  25. Cached whois for 133.18.202.245 : search-apnic-not-arin@apnic.net

    By Steve,
    • 3 replies
    • 663 views
×