I have self hosted `Mailcow` at home in a `VM` running on my `Proxmox` server. Because I don't have a public IP, I have rented a `VPS` on which I have `Wireguard VPN` and `NginxProxyManager` installed. I have another instance of `NginxProxyManager` running at home which is connected to this `VPN`. So if I go to `foo.MY_DOMAIN` for example, the `NPM` on `VPS` forwards this request to the internal `VPN IP` of `NPM` at home, then `NPM` at home forwards the same `foo.MY_DOMAIN` to the respective app/service's local `IP` on my local network, this is how I access my self hosted services from outside. Now the `Mailcow VM` is connected to this `VPN` directly and only `NPM` on `VPS` forwards my `mail.MY_DOMAIN` to `Mailcow`'s internal `VPN IP` on port 80. To install I ran the `.generate_config.sh` script typed my domain as `mail.MY_DOMAIN` added my `TZ` and ran `docker compose up -d`, I didn't edit anything in the `mailcow.conf` file. Now when go to `mail.MY_DOMAIN` I can access `mailcow UI` and I can login. After logging in, under Email -> Configuration, I added a domain entry for `MY_DOMAIN` left all options as default. Then I edited the DNS for this domain and added `autodiscovery`, `autoconfig` as `CNAME` records and added `DKIM`, `DMARC`, `SPF` as `TXT` record and a `MX` record that points to `mail.MY_DOMAIN`. About `DNS` and my domain, I have a domain say `example.com`, for this domain I created an `A` record `mail` pointing to the `VPS` public `IP`. I use `Cloudflare` for `DNS`, here are screenshots of how I have setup my `DNS` entries, [upl-image-preview url=https://community.mailcow.email/assets/files/2024-07-13/1720857223-497056-2024-07-13-13-21.png] [upl-image-preview url=https://community.mailcow.email/assets/files/2024-07-13/1720857223-478418-2024-07-13-13-21-1.png] [upl-image-preview url=https://community.mailcow.email/assets/files/2024-07-13/1720857223-454273-2024-07-13-13-23.png] Here is the `DNS` configuration from `mailcow` `Domains` page, [upl-image-preview url=https://community.mailcow.email/assets/files/2024-07-13/1720857739-792331-2024-07-13-13-31.png] Then I added a `Mailbox` I used `admin` as `username` set a password for it and left everything as default. So the `email` address looks like, `admin@MY_DOMAIN`. Then I added an `Alias`, [upl-image-preview url=https://community.mailcow.email/assets/files/2024-07-13/1720857974-528031-2024-07-13-13-35.png] After this I logged in to `SOGo` via `admin@MY_DOMAIN`, which worked, then I sent a `email` to my real `GMail` account, the `email` showed as `sent` in `SOGo`, but I have not received any `mail` on my `GMail` account. I followed this video on YouTube BTW for help with setting up `Mailcow`, https://www.youtube.com/watch?v=_z6do5BSJmg Am I missing something?

> @"apoorv569"#p17106 Then I added a Mailbox I used admin as username Not the smartest idea to create a mailbox with the same username as the internal admin account. That could lead to unexpected results, because admin account is treated differently throughout mailcow. More helpful would be the postfix logs for the attempt to try to forward the mail to the VPS. Can you do a telnet on port 25 from your home server to the VPS via the tunnel?

@"esackbauer"#p17108 I see. Should I delete this mailbox and create new one with a different username? How/Where do I check the `postfix` logs? `telnet` from home server to `VPS` via tunnel, meaning from the `mailcow VM` at home to `VPS` public `IP`? so if the `VPS` public `IP` is `1.2.3.4`, I do `telnet 1.2.3.4 25` from the `mailcow VM` at home while I am connected to the `VPN`?

> @"apoorv569"#p17112 How/Where do I check the postfix logs? In the mailcow UI if you log in with your admin account. Alternatively: https://docs.mailcow.email/troubleshooting/debug-logs/ > @"apoorv569"#p17112 from the mailcow VM at home to VPS public IP No, that would be outside the tunnel. Can it be that you are very new to all this? Seems you are overcomplicating things. You actually do not need 2 NPMs and a VPN tunnel.

@"esackbauer"#p17113 > @"esackbauer"#p17113 In the mailcow UI if you log in with your admin account. I see this in the `postfix` logs, [upl-image-preview url=https://community.mailcow.email/assets/files/2024-07-13/1720871440-431947-2024-07-13-17-19.png] > @"esackbauer"#p17113 No, that would be outside the tunnel. Can it be that you are very new to all this? > Seems you are overcomplicating things. You actually do not need 2 NPMs and a VPN tunnel. I am new to self hosting mail server, but not in self hosting in general. In the case of `mailcow` there is only one `NPM` involved the one on the `VPS` as `mailcow` `VM` is directly connected to the `VPN`. I only do this (2 `NPM` with a `VPN` setup) because I don't have a public `IP` and I want to be able to access my self hosted services from outside my `home`. I suppose I could connect every service to `VPN` on their own and remove `NPM` at home and only have `NPM` instance on the `VPS`?

It depends on what you have, I am also hosting my private mailcow at home. My IPv4 address does not change so often, so I use a the [ddns-updater](https://github.com/qdm12/ddns-updater) container to update the DNS records. You need ONLY for **SMTP outgoing** a static IP address in good state. So I have everything pointed at my dynamically updated DNS records at home, and just use a relay ("sender dependent transport" in mailcow) to forward mails to a VPS. No need for VPN because you can force this connection to be encrypted via TLS.

@"esackbauer"#p17117 So I need enable/open port 25 on the `VPS` I am assuming (`ufw`)? There is no active firewall on the `VM` (at least I didn't configure one).

Here is everything you need to know: https://community.mailcow.email/d/1275-the-ultimate-guide-to-run-your-own-smtp-relay-server

@"esackbauer"#p17119 So I need a relay server? It won't work with it in my case?

You need a relay server. Its all explained in that link. You can host one yourself on a VPS, or you can use Sendgrid or Mailgun which have a free tier.

@"esackbauer"#p17121 Do you use a relay server as well? Asking because you said you also self host mailcow at home. Or is it specific to my scenario?

Mailcow over VPN not sending emails.

DocFraggle

LMGTFY

https://sa.ndeep.me/post/how-to-use-sendgrid-as-an-smtp-relay-in-mailcow/

Port 587

esackbauer

apoorv569 but looks like even a relay needs port 25?

You sure need to learn a lot about SMTP and firewalls. Firewall rules have a source and destination. So it can apply to incoming and/or outgoing traffic. Outgoing Port 25 is what providers are blocking.
We posted already several solutions here in this thread, please pick one.
Sorry you have to learn the basics for running servers elsewhere. This is a mailcow specific forum.

« Previous Page