unable to recieve emails when sending emails works correctly

dario48

as the title states, I am fully able to send emails to most servers, but when it comes to receiving them it seems I’m out of luck
here are a couple of things that might be useful

log.txt

831kB

postfix-dovecot-logs.txt

113kB

the dns is a follows (taken from the mailcow ui as I imagine this is what matters to the conversation)
{a screenshot of the dns setup shown by mailcow}
I’ve sent various emails from protonmail and one from gmail, but it does not seem to work
the firewall on the router (as I am self hosting this) does redirect all the ports mentioned in the docs to the server so it should not be a firewall problem
thank for your attention : )

pkernstock

Your mailserver’s most important port - used for email delivery - TCP/25 is not accessible from outside:

$ dig +short dario48.site MX
10 mail.dario48.site.
$ dig +short mail.dario48.site A
151.62.15.61
$ time nc -vz 151.62.15.61 25
nc: connect to 151.62.15.61 port 25 (tcp) failed: Connection timed out

real    2m13.671s
user    0m0.001s
sys     0m0.001s

dario48

pkernstock that seems really strange as I put in the router settings to allow port 25 from WAN to LAN and to redirect it to the server’s local ip, so idk why it won’t work I will have to contact costumer support to find out more ig, thank you for taking the time to respond :]

pkernstock

It sounds like you’re planning to use NAT? Make sure to use the “correct NAT”. If wrongly configured and the Source-IP is the wrong IP, it can lead to an open-relay.

Without NAT is usually the better choice.

dario48

I’m not this is just running on a laptop from the year 2000 connected via ethernet to the wifi router in my home, and this worked fine with my git forge, with ssh, with the website itself and vaultwarden, it also already lets me login to cowmail from another device without the webui running on the server, it’s 99% working :)

mlcwuser

Well, you need to make sure that your Mailcow is reachable via port 25 from the internet. Maybe also try posting in the forums for your specific router/firewall. Furthermore, it’s possible that your ISP is blocking port 25 inbound. Granted, it’s a bit strange that they would block it inbound but leave it open outbound, but hey, ISPs do strange things sometimes. ;-)

And, to be honest, I’m rather surprised that you can send emails successfully, because your IP address is on several blacklists and there is also no PTR record for your IP address. These are additional things you would need to take care of to be able to use your Mailcow server reliably on a daily basis.

dario48

mlcwuser they shut down the forum for my ISP in service of AI, so I’m trying to find a way to contact them, and even that is easier said then done :P

[unknown] I don’t plan to use this as an email for stuff that needs to be really reliable (uni and the likes) I just want an email that I can make available to contact me for my socials :) this whole thing of setting up an email did start when I wanted to invite a friend on my vaultwarden instance after all :P

pkernstock

Agree. Mailservers at home tend to be a very bad idea typically. Especially if you rely on reliable email delivery on a day-to-day basis. If emails cannot be delivered reliably, it’s not really adding much benefit.

Also, Home-ISP-IP-Ranges generally tend to have a bad reputation.

Mail is very different to other self-hosting services like Vaultwarden. Mail relays on so much more stuff and reputation these days.

I’d strongly advise against running this at home.