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

  1. alsonmedia, maybe incorrect reporting address?

    By Jank1887,
    • 3 replies
    • 342 views

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

    By Steve,
    • 2 replies
    • 284 views

  3. 182.160.128.0 - 182.160.191.255: route changed since manual entry

    By gnarlymarley,
    • 0 replies
    • 272 views

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

    By Snowbat,
    • 0 replies
    • 222 views

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

    By Snowbat,
    • 0 replies
    • 261 views

  6. MTA version parsed as IP address

    By Tesseract,
    • 7 replies
    • 656 views

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

    By Snowbat,
    • 5 replies
    • 383 views

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

    By Snowbat,
    • 2 replies
    • 303 views

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

    By Snowbat,
    • 3 replies
    • 368 views

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

    By Snowbat,
    • 1 reply
    • 262 views

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

    By Snowbat,
    • 1 reply
    • 253 views

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

    By Snowbat,
    • 0 replies
    • 344 views

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

    By Snowbat,
    • 0 replies
    • 322 views

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

    By Snowbat,
    • 0 replies
    • 335 views

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

    By Steve,
    • 1 reply
    • 466 views

  16. spam from 193.142.146.221

    By C2H5OH,
    • 1 reply
    • 430 views

  17. Not receiving emails with my submissions

    By mike20878,
    • 9 replies
    • 512 views

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

    By denby,
    • 1 reply
    • 1.1k views

  19. Amazon not Verizon

    By Hanco,
    • 3 replies
    • 528 views

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

    By shirayuki,
    • 0 replies
    • 536 views

  21. no abuse contact for 202.238.198.169 ?

    By HeatherReid43,
    • 3 replies
    • 648 views

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

    By MIG,
    • 3 replies
    • 1.2k views

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

    By AJR,
    • 1 reply
    • 549 views

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

    By Steve,
    • 3 replies
    • 901 views

  25. 27.124.112.0/20 requests spam be reported at spam@syrahost.com

    By Zekamashi,
    • 0 replies
    • 622 views
×
×
  • Create New...