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. 52.175.53.32 - "Using rdns to route to correct Microsoft department" but reports go to the spammer

    By Snowbat,
    • 1 reply
    • 359 views

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

    By Snowbat,
    • 0 replies
    • 439 views

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

    By Snowbat,
    • 0 replies
    • 440 views

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

    By Snowbat,
    • 0 replies
    • 441 views

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

    By Steve,
    • 1 reply
    • 609 views

  6. spam from 193.142.146.221

    By C2H5OH,
    • 1 reply
    • 589 views

  7. Not receiving emails with my submissions

    By mike20878,
    • 9 replies
    • 623 views

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

    By denby,
    • 1 reply
    • 1.3k views

  9. Amazon not Verizon

    By Hanco,
    • 3 replies
    • 647 views

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

    By shirayuki,
    • 0 replies
    • 669 views

  11. no abuse contact for 202.238.198.169 ?

    By HeatherReid43,
    • 3 replies
    • 777 views

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

    By MIG,
    • 3 replies
    • 1.4k views

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

    By AJR,
    • 1 reply
    • 724 views

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

    By Steve,
    • 3 replies
    • 1k views

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

    By Zekamashi,
    • 0 replies
    • 770 views

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

    By RobiBue,
    • 1 reply
    • 738 views

  17. spam from 69.50.208.13

    By C2H5OH,
    • 0 replies
    • 628 views

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

    By C2H5OH,
    • 0 replies
    • 662 views

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

    By Steve,
    • 1 reply
    • 674 views

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

    By C2H5OH,
    • 0 replies
    • 620 views

  21. Abuse contact for Brazilian spammer 200.160.198.170

    By C2H5OH,
    • 0 replies
    • 617 views

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

    By C2H5OH,
    • 0 replies
    • 643 views

  23. Abuse address for 192.92.97.133 is aburch[at]activecampaign.com

    By C2H5OH,
    • 0 replies
    • 637 views

  24. search-apnic-not-arin

    By Maxim1970,
    • 1 reply
    • 750 views

  25. Mailhost configuration problem, identified internal IP as source

    By Steve,
    • 16 replies
    • 2.9k views
×
×
  • Create New...