# 关于discourse-setup的拟议更改，因为Digital Ocean屏蔽了出站SMTP **URL:** \ **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:** 1
作者： ![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 月 25 日 13:30 UTC](https://meta.discourse.org/t/proposed-changes-to-discourse-setup-because-digital-ocean-blocks-outbound-smtp/66778/1 "2017-07-25T13:30:12Z")
Continuing the discussion from [Digital Ocean is blocking outgoing mail!](https://meta.discourse.org/t/digital-ocean-is-blocking-outgoing-mail/66740/26): It seems that Digital Ocean is blocking out bound SMTP traffic for at least some customers. My guess is that soon you’ll have to jump through hoops to be able to access a remote SMTP port. Simple solution: Mailgun, Sendgrid, and Sparkpost all accept TLS traffic on port 2525. I propose these changes to `discourse-setup` - changing default SMTP port for those services to 2525. - adding a test (e.g., `nc -z -w5 smtp.mailgun.org 25`) to see if the chosen SMTP port is open Why those 3 services services? They’re the ones that `discourse-setup` currently knows about and recommends `smtp_user_name` for). Unless someone (i.e., @codinghorror) has some reason not to, I’ll try to do this later this week. I’ll also see about changing the scary “your ip doesn’t resolve to your hostname” message too. It continues to confuse people. Or maybe I’ll look again at finding a more reliable way to test that the resolved host IP connects to the server. --- _[View the full topic](https://meta.discourse.org/t/proposed-changes-to-discourse-setup-because-digital-ocean-blocks-outbound-smtp/66778)._