# Proposed changes to discourse-setup because Digital Ocean blocks outbound smtp

**URL:** <https://meta.discourse.org/t/proposed-changes-to-discourse-setup-because-digital-ocean-blocks-outbound-smtp/66778>\
**Category:** Development\
**Created:** [July 25, 2017, 1:30pm UTC](https://meta.discourse.org/t/proposed-changes-to-discourse-setup-because-digital-ocean-blocks-outbound-smtp/66778 "2017-07-25T13:30:12Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![cipheos](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cipheos/32/501491_2.png) [@cipheos](https://meta.discourse.org/u/cipheos)\
**Post date:** [May 1, 2025, 10:02pm UTC](https://meta.discourse.org/t/proposed-changes-to-discourse-setup-because-digital-ocean-blocks-outbound-smtp/66778/20 "2025-05-01T22:02:42Z")

</div>

Oh, no, they got _a lot_ more aggressive. We’ve had services hosted there which were able to send mail through 587 just fine up until a few days ago. Quite a rug pull if you imagine that some services require e-mail to authenticate users. On top of that we suddenly can’t send emails while connected to our VPN, because we host our gateway there. All of these things were still working last week for us. I’d certainly say now might be the time to worry.

---

_[View the full topic](https://meta.discourse.org/t/proposed-changes-to-discourse-setup-because-digital-ocean-blocks-outbound-smtp/66778)._
