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

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

    By Snowbat,
    • 1 reply
    • 27 views

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

    By Snowbat,
    • 1 reply
    • 87 views

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

    By Snowbat,
    • 0 replies
    • 69 views

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

    By Snowbat,
    • 0 replies
    • 69 views

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

    By Snowbat,
    • 0 replies
    • 92 views

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

    By Snowbat,
    • 1 reply
    • 98 views

  7. MTA version parsed as IP address

    By Tesseract,
    • 2 replies
    • 133 views

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

    By Steve,
    • 1 reply
    • 190 views

  9. spam from 193.142.146.221

    By C2H5OH,
    • 1 reply
    • 155 views

  10. Not receiving emails with my submissions

    By mike20878,
    • 9 replies
    • 233 views

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

    By denby,
    • 1 reply
    • 346 views

  12. Amazon not Verizon

    By Hanco,
    • 3 replies
    • 261 views

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

    By shirayuki,
    • 0 replies
    • 266 views

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

    By AJR,
    • 1 reply
    • 281 views

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

    By MIG,
    • 3 replies
    • 485 views

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

    By Zekamashi,
    • 0 replies
    • 276 views

  17. no abuse contact for 202.238.198.169 ?

    By HeatherReid43,
    • 3 replies
    • 336 views

  18. Abuse contact for '176.56.208.0 - 176.56.208.255' is 'abuse[at]phe.uk.com'

    By RobiBue,
    • 1 reply
    • 376 views

  19. spam from 69.50.208.13

    By C2H5OH,
    • 0 replies
    • 272 views

  20. Abuse contact for '212.16.193.0 - 212.16.193.255' is 'abuse[at]vtc.ru'

    By C2H5OH,
    • 0 replies
    • 308 views

  21. No reporting addresses found for 185.163.220.107, using devnull for tracking.

    By Steve,
    • 1 reply
    • 308 views

  22. Abuse contact for '91.216.58.0 - 91.216.58.255' is 'abuse[at]eyona.com'

    By C2H5OH,
    • 0 replies
    • 291 views

  23. Abuse contact for Brazilian spammer 200.160.198.170

    By C2H5OH,
    • 0 replies
    • 300 views

  24. Abuse contact for '148.66.128.0 - 148.66.159.255' is 'abuse[at]godaddy.com'

    By C2H5OH,
    • 0 replies
    • 303 views

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

    By Steve,
    • 3 replies
    • 594 views
×