Like others I've reached the end of my tether with DO. In my case, I've seen increasing volumes of malicious / junk traffic via their IPv6 prefixes, with reports to abuse doing virtually nothing, so now I just define ip/ip6tables drop rules.
30 seconds' browsing will return the ranges you need, https://www.peeringdb.com/net/6494 https://bgp.he.net/AS14061#_prefixes & https://bgp.he.net/AS14061#_prefixes6 https://bgp.he.net/AS46652#_prefixes I don't miss their traffic... On Thu, 9 May 2019 at 17:57, John Levine via mailop <mailop@mailop.org> wrote: > In article <20190509145346.gd8...@gsp.org> you write: > >It would be far easier and much more effective if everyone on this > >mailing list caused every mail server that they run to refuse all > >mail from all Digital Ocean network space without warning, effective > >immediately > > Don't waste your time, they don't care. I've blocked all of the > blocks I was aware of for a long time and haven't seen it affect any > real mail at all. > > I would encourage people to block their corporate mail servers except > that they don't have any. Mail for digitalocean.com is outsourced to > Google. > > They could save themselves a lot of pain by just blocking port 25 > across their entire network, and saying if you want to send mail, send > it through a submission server somewhere else, and you can get your > VPS port 25 unblocked after you've been a paying customer for three > months. > > Other cloud providers do roughly that and it works pretty well. Some > of them even monetize it by referring users to freemium service at > Sendgrid. > > > > > > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop >
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
