mailcow-dockerized-docs icon indicating copy to clipboard operation
mailcow-dockerized-docs copied to clipboard

Add documentation for outgoing ports and destinations

Open Stefomat opened this issue 3 years ago • 4 comments

Hi,

In the installation requirements there is a chapter that deals with firewalls and ports. It explains exactly which incoming ports Mailcow needs and how to check if they are free. However, outgoing ports are not covered in this chapter. Outgoing ports and destinations are only briefly touched in "Hetzner Cloud (and probably others)", as there are specialities for Hetzner.

Can we have a chapter that deals with outgoing destinations and ports during installation and operation? E.g. for http/https towards GitHub (git clone), DNS towards root server and recursive resolution, etc.?

I think not every Mailcow instance is placed on the internet with the firewall completely open for outgoing connections. For such installations, an overview of the required connections would be helpful.

Greetings Stefomat

Stefomat avatar Dec 28 '22 13:12 Stefomat

If you want to contribute that feel free to do so. Right now it's not planned to implement such information from our side.

DerLinkman avatar Dec 28 '22 20:12 DerLinkman

As far as I figured out at the moment you need to allow on top of the obvious mail traffic ports, outgoing: UDP 53,11445,11335 Else, rspamd ist taking a significant longer scan time.

robertoswald avatar Aug 07 '24 10:08 robertoswald

DNS TCP AND UDP Port 53, Rspamd is also correct, that are the fuzzy ports for eg. fuzzy.mailcow.email

DerLinkman avatar Aug 07 '24 12:08 DerLinkman

DNS TCP AND UDP Port 53, Rspamd is also correct, that are the fuzzy ports for eg. fuzzy.mailcow.email

Only UDP 53 für DNS showed up blocked in firewall log. Just for information.

robertoswald avatar Aug 07 '24 12:08 robertoswald