# Mail-receiver relay access denied
**URL:** https://meta.discourse.org/t/mail-receiver-relay-access-denied/145690
**Category:** Self-hosting
**Tags:** mail-receiver
**Created:** [March 26, 2020, 3:43pm UTC](https://meta.discourse.org/t/mail-receiver-relay-access-denied/145690 "2020-03-26T15:43:55Z")
**Posts on this page:** 2
**Page:** 2
### Author:  [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [January 26, 2025, 6:28pm UTC](https://meta.discourse.org/t/mail-receiver-relay-access-denied/145690/21 "2025-01-26T18:28:45Z")
Here is situation when only 22 was open by ufw and my forum still worked just fine.
> [@Will UFW limit Discourse too?](https://meta.discourse.org/t/will-ufw-limit-discourse-too/231873):
>
> How can Discourse bypass UFW? I had enabled only port 22 so all other ports should be closed then. But a forum worked anyway. How’s that possible? DigitalOcean droplet, but that should not mean anything. And no one-click install, but official way. This is not a pure support question, but we don’t have here a catogory named Stupid basic questions by beginners wink
---
### Author:  [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [January 26, 2025, 6:34pm UTC](https://meta.discourse.org/t/mail-receiver-relay-access-denied/145690/22 "2025-01-26T18:34:13Z")
> [@Jagster](#):
>
> But `ufw status` isn’t that interesting. Instead `nft list ruleset` is.
And basically because of that I said earlier
> But `ufw status` isn’t that interesting. Instead `nft list ruleset` is.
[Previous page](https://meta.discourse.org/t/mail-receiver-relay-access-denied/145690.md?page=1)