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!
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.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.