I installed mailcow with the default mailcow.conf except for the http_port and https_port set to 8987 and 8988. I also changed the IPV4_NETWORK to 172.33.1 bc i was already using 172.22.1 but the dotcov container couldn't access to dns so i changed the unbound config file and allowed the 172.33.1.0/24 network. Im also using traefik with a dynamic config file as reverse proxy for the admin interface and the sog web client. I can send emails but i cant receive.

Traefik does only http(s) reverse proxy. You need to tell your firewall to NAT all the other ports of mailcow to the host.

No. But if you don't tell us a bit more about your setup (where is it hosted? is traefik on the same host? has the host a firewall in front of it (like hetzner for example)?

Are you sure your PC meets the [requirements ](https://docs.mailcow.email/getstarted/prerequisite-system/#supported-os)regarding operating system? Your PC has no firewall to the internet (e.g. your home router)? Really?

SMTP not working.

DavideSirico

I’m selfhosting it on my pc inside my lan. The traefik is on the same host and i dont have a firewall in front of it.
traefik config:

  routers:
    mailcow:
      rule: Host(`mail.sirico.dev`)
      entrypoints:
         - websecure
      service: mailcow
      tls:
       certresolver: cloudflare


  services:
    mailcow:
      loadBalancer:
        servers:
          - url: http://192.168.1.100:8987
        passHostHeader: true


  middlewares:
    https-redirect:
      redirectscheme:
        scheme: https
        permanent: true```

esackbauer

Are you sure your PC meets the requirements regarding operating system?
Your PC has no firewall to the internet (e.g. your home router)? Really?

DavideSirico

$ uname -r
6.8.0-51-generic

$ cat /etc/os-release
PRETTY_NAME="Ubuntu 24.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.1 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo

The firewall on my router is set to

Low: A host on the WAN can directly access hosts on the LAN, but cannot directly access the device itself (except for ping).

esackbauer

DavideSirico but cannot directly access the device itself (except for ping).

There you have it. Try to figure out how to do NAT on your home router for the ports 25, 143, 993 etc to the ubuntu host.
And good luck. Installing a mail server on a residential IP address/router is not recommended. You will have trouble receicing and sending mails.

DavideSirico

I have already set port forwarding for every port specified on the documentation.

esackbauer

And have you tried with telnet or other tools to reach them from the internet? Are you sure your DNS records are correct?
Ok it looks like your DNS is a mess.
MX record points to “server1.sirico.dev”
However, mail.sirico.dev points to a different IP address.

Both servers are not reachable on port 25 from outside:
https://mxtoolbox.com/SuperTool.aspx?action=smtp%3amail.sirico.dev&run=toolpage

So your firewall/router is not working, or your DNS is pointing at the wrong host.

DavideSirico

nmap scan results

$ nmap -sS 141.98.0.105
Starting Nmap 7.95 ( https://nmap.org ) at 2024-12-18 17:55 CET
Nmap scan report for 141.98.0.105
Host is up (0.0038s latency).
Not shown: 989 filtered tcp ports (no-response)
PORT     STATE  SERVICE
80/tcp   open   http
110/tcp  closed pop3
143/tcp  closed imap
443/tcp  open   https
465/tcp  closed smtps
587/tcp  closed submission
993/tcp  closed imaps
995/tcp  closed pop3s

Nmap done: 1 IP address (1 host up) scanned in 4.50 seconds

dns configuration

sirico.dev	3600	IN	SOA	darl.ns.cloudflare.com. dns.cloudflare.com. 2048620762 10000 2400 604800 3600

;; NS Records
sirico.dev.	86400	IN	NS	darl.ns.cloudflare.com.
sirico.dev.	86400	IN	NS	sandra.ns.cloudflare.com.

;; A Records
server1.sirico.dev.	300	IN	A	141.98.0.105
sirico.dev.	1	IN	A	100.102.154.66

;; CNAME Records
autoconfig.sirico.dev.	1	IN	CNAME	server1.sirico.dev.
autodiscover.sirico.dev.	1	IN	CNAME	server1.sirico.dev.
mail.sirico.dev.	1	IN	CNAME	stage.sirico.dev.


;; MX Records
sirico.dev.	1	IN	MX	10 server1.sirico.dev.

;; TXT Records
dkim._domainkey.sirico.dev.	1	IN	TXT	"v=DKIM1;k=rsa;t=s;s=email;p=key
_dmarc.sirico.dev.	1	IN	TXT	"v=DMARC1; p=reject; rua=mailto:mailauth-reports@sirico.dev"
sirico.dev.	1	IN	TXT	"v=spf1 a:server1.sirico.dev -all"

esackbauer

Your mailcow hostname mail.sirico.dev should have the A record, not just a CNAME. Also look at the MX configuration:
https://docs.mailcow.email/getstarted/prerequisite-dns/#the-minimal-dns-configuration

If people would follow properly the documenation, forum would be almost empty here 😉

And your nmap shows port 25 is not open…

And you don’t have PTR records…

DavideSirico

I use mail.sirico.dev to access the webclient and sever1.sirico.dev as fqdn. Can i do this or i need to swap them?

esackbauer

Please stick to the defaults as per mailcows documentation. Do not change something you do not completely understand.
mail.sirico.dev is already a FQDN. Are you sure you are fit enough to run a complex mail server with a reverse proxy in front of it? Seems like you struggle already with some networking basics.
SMTP is very picky about hostnames. It should match with PTR and A records, and MX must point to that hostname (FQDN), or you will have problems sending or receiving mails. This is why you must follow the documenation as closely as possible.

DavideSirico

First of all, I’m asking you to help me with a problem, not your opinion on my “networking skills”.
Then I changed the DNS following the documentation exactly and still can’t receive emails.

esackbauer

DavideSirico Then I changed the DNS following the documentation exactly and still can’t receive emails.

I just checked with mxtoolbox and it seems your port 25 is now open. So from now on you need to check if connections are actually made and received by postfix container. Check its logs.
You still have no reverse DNS (PTR) record for your IP address. Could be also an issue certain mail server to not want to connect to your server.