In the time that I’ve been hosting projects at Digital Ocean, I can truly say I’ve been more than happy. Performance and functionality is great. However one small problem that is becoming major.
Digital Ocean is rejecting SpamCop reports. I’ve lodged a ticket to this effect a bit back, I was asked info, I provided it and it would have been resolved. Now the users of projects that I’m host are requesting I move as they are starting to see Digital Ocean as not being serious about spam. See http://i.imgur.com/3kMG16V.png
Bad things will happen, but if reports are not received about bad things, we may soon all be in a bad neighborhood without without the abuse team being aware of it. What follows next is RBLs and like.
Could the abuse team please make a plan to resolve issues linked to spamming and reports about it from SpamCop?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Actually, your response is not helpful domains266064. But you probably left tracking links in …
However, this post is about abuse@ not working as it should which affects all legitimate users. So please do not cloud issues.