# 关于discourse-setup的拟议更改，因为Digital Ocean屏蔽了出站SMTP

**URL:** <https://meta.discourse.org/t/proposed-changes-to-discourse-setup-because-digital-ocean-blocks-outbound-smtp/66778>\
**Category:** Development\
**Created:** [2017 年7 月 25 日 13:30 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:** 18

<div class="post-metadata">

作者： ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
发布日期： [2017 年7 月 26 日 16:13 UTC](https://meta.discourse.org/t/proposed-changes-to-discourse-setup-because-digital-ocean-blocks-outbound-smtp/66778/18 "2017-07-26T16:13:04Z")

</div>

Lovely explication, @mpalmer. Crickets from Digital Ocean.

I’ve changed my install script to use 2525 since there’s no easy way to tell whether 587 is blocked (my script blindly pipes values into `./discourse-setup` so that I’m continually making sure that it’s working correctly).

It appears that people who use Digital Ocean and want to get their ports un-blocked need to file a ticket to request that, which is not something I’m willing to ask my install customers to do if at all possible.

> [@codinghorror](#):
>
> Probably fine to quick test the 587 port during setup and warn if it is not working,

I’ll try to add such a test to `./discourse-setup` in the next week.

---

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