# Parece que a DO está desativando SMTP nos seus planos de hospedagem do Discourse

**URL:** https://meta.discourse.org/t/looks-like-do-is-disabling-smtp-in-their-discourse-hosting-plans/321531
**Category:** Self-hosting
**Tags:** hosting
**Created:** [13 Agosto , 2024 21:20 UTC](https://meta.discourse.org/t/looks-like-do-is-disabling-smtp-in-their-discourse-hosting-plans/321531 "2024-08-13T21:20:29Z")
**Posts on this page:** 1
**Showing post:** 17

<div class="post-metadata">

### Author: ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [14 Agosto , 2024 18:30 UTC](https://meta.discourse.org/t/looks-like-do-is-disabling-smtp-in-their-discourse-hosting-plans/321531/17 "2024-08-14T18:30:18Z")

</div>

O bloqueio da porta 25 de saída por padrão pela Digital Ocean está em vigor há _anos_. Isso não é novidade.

Matt explica bem aqui:

> [@Proposed changes to discourse-setup because Digital Ocean blocks outbound smtp](https://meta.discourse.org/t/proposed-changes-to-discourse-setup-because-digital-ocean-blocks-outbound-smtp/66778/10?u=supermathie):
>
> OK then, let me give you the full spiel, then: Port 25 outbound is an obvious candidate for filtering, because if you can hit the Internet on port 25, you can deliver e-mail to practically anyone. If that e-mail is unwanted, the only useful “identity” information that the recipient has to try and prevent further abuse is the sending IP address. That identity is tied, in general, to a hosting provider, not an individual subscriber, so any reputation hit for spamming goes, in the first instanc…

---

_[View the full topic](https://meta.discourse.org/t/looks-like-do-is-disabling-smtp-in-their-discourse-hosting-plans/321531)._