Routing / Report Address Issues

1,823 topics in this forum

1. spam from 194.27.36.67

   By C2H5OH, September 21
   • 0 replies
   • 33 views
   • 
   • C2H5OH
   • September 21

2. Invalid abuse contacts for IP Address 2001:288:3001:17:0:0:0:12

   By Steve, September 14
   • 2 replies
   • 87 views
   • 
   • ninth
   • September 14

3. Why is everything going to "bonded sender"??

   By amberj, July 26   

   • bondedsender
   • 11 replies
   • 511 views
   • 
   • jeffc
   • August 29

4. No report filed due to "BondedSender+ confirmed opt-in only"?

   By Seb, July 22   

   • bondedsender
   • 13 replies
   • 684 views
   • 
   • jeffc
   • August 29

5. spam from 198.46.190.149

   By C2H5OH, August 23
   • 0 replies
   • 37 views
   • 
   • C2H5OH
   • August 23

6. Invalid abuse contacts for IP Address 212.119.190.148

   By Steve, August 4
   • 0 replies
   • 210 views
   • 
   • Steve
   • August 4

7. Microsoft spam reports go to the sewer? 1 2

   By sc_aswglo, January 16
   • 41 replies
   • 2.3k views
   • 
   • petzl
   • June 30

8. Delivery incomplete to fbl-spamcop@ext.godaddy.com

   By Steve, June 10
   • 3 replies
   • 266 views
   • 
   • Steve
   • June 14

9. Delivery has failed to these recipients or groups (abuse@mtnnigeria and customercare@mtnnigeria.net)

   By Steve, May 28
   • 0 replies
   • 171 views
   • 
   • Steve
   • May 28

10. whois.apnic.net gives abuse email for 60.36.166.29 as "hostmaster@nic.ad.jp"

    By C2H5OH, April 2
    • 3 replies
    • 210 views
    • 
    • Steve
    • May 28

11. Sorry, no reporting addresses found for 164.100.138.251

    By Nexttime, May 5
    • 2 replies
    • 125 views
    • 
    • petzl
    • May 15

12. SC can't parse this URI: https://bookdnx.cfd#user@example.com

    By gurnec, May 8
    • 1 reply
    • 122 views
    • 
    • Lking
    • May 8

13. Can anyone help get me to report this?

    By Steve, May 2
    • 6 replies
    • 316 views
    • 
    • petzl
    • May 5

14. abuse@timbrasil.com.br not accepting abuse reports?

    By Steve, April 20
    • 0 replies
    • 102 views
    • 
    • Steve
    • April 20

15. Invalid abuse contact for 91.220.182.196

    By Steve, April 9
    • 1 reply
    • 176 views
    • 
    • petzl
    • April 9

16. Abuse contact for 194.0.189.8 is abuse@tele2.kz

    By C2H5OH, March 29
    • 2 replies
    • 181 views
    • 
    • C2H5OH
    • April 2

17. Abuse contact for '146.19.143.0 - 146.19.143.255' is 'abuse@bluevps.com'

    By C2H5OH, March 14
    • 0 replies
    • 107 views
    • 
    • C2H5OH
    • March 14

18. IP range of velia.net Internetdienste GmbH showing Host Europe GmbH abuse contact

    By GeForce777, February 18   

    • parsing
    • abuse contact
    • 5 replies
    • 303 views
    • 
    • gnarlymarley
    • February 27

19. Incorrect abuse contact for 89.34.236.6

    By Anna, February 16
    • 1 reply
    • 148 views
    • 
    • Anna
    • February 20

20. Invalid abuse contact for 200.62.229.190

    By Steve, February 10
    • 2 replies
    • 159 views
    • 
    • ninth
    • February 10

21. Incorrect abuse contact for 49.3.27.76?

    By Steve, January 27
    • 2 replies
    • 153 views
    • 
    • ninth
    • January 28

22. Invalid abuse contact for 202.172.28.138

    By Steve, January 22
    • 1 reply
    • 133 views
    • 
    • ninth
    • January 22

23. Plala not responding to spam reports anymore?

    By Steve, January 18
    • 2 replies
    • 203 views
    • 
    • Steve
    • January 21

24. Can't continue parsing. DNS-server-error; Try to refresh this page later.

    By neuronaut, April 26, 2023
    • 13 replies
    • 472 views
    • 
    • petzl
    • December 30, 2023

25. Invalid third party abuse contact for 15.235.166.207

    By Steve, December 13, 2023
    • 1 reply
    • 151 views
    • 
    • petzl
    • December 13, 2023