Hey. I heard about MailCow and wanted a mailserver to self-host on my VPS. The issue I've came accross is that I cannot find a way to properly setup my DNS records. I made all the records needed, verified them but the DNS check on MailCow UI prints out things that are different than what I putted on Cloudflare. I don't proxy any of the mail-related records, as I've seen that it causes issues (on this forum and other forums when I was searching for a solution). Here are screenshots for y'all to see what the UI says, and what I've configured. 1 (UI): https://safe.classydev.fr/zsHVMAV3c4XdvBUJejHEBMhIHz9r5BRp.png 2 (Cloudflare): https://safe.classydev.fr/Glj7s8jAAG279JKzJnzI0de63T2su8cK.png 3 (Cloudflare): https://safe.classydev.fr/s4sGBsGtOG15yIcGsDfsZbESFfqR7GVe.png And I cannot send or recieve any emails, even though all ports and open and accessible as I've tested. Any ideas?

you should be able to receive mails if you have a mailbox created. one problem is your PTR record. you should be able to change that in the Admin panel of your hoster. [upl-image-preview url=https://community.mailcow.email/assets/files/2024-02-28/1709154745-871680-image.png] it this might be your second problem. [upl-image-preview url=https://community.mailcow.email/assets/files/2024-02-28/1709155803-367623-image.png] And you're sure you're on a proper VPS and not behind a router from your internet provider with a DHCP address?

@"piperino"#p13827 What do you mean panel of hoster? I don't have access to such a thing, I only have terminal access (the server is a server that is running in my friend's network). The thing is that the PTR record is not supposed to be what mailcow detects (On cloudflare, as you can see on the screenshots, I've configured the `mail.project-hestia.me` to the IP (and not the weird domain) and the PTR record to `mail.project-hestia.me` so everything *should* work). And why is my friend's IP blacklisted? As the server is at his home, it's behind a router (*Freebox*) and I've configured the port redirection to allow all Mailcow ports and domains. **EDIT**: I saw that "82-65-80-184.subs.proxad.net" is a domain name associated with my friend's router as proxad.net redirects to his internet provider's website. But IDK why only for this record it shows the internet provider weird domain instead of the IP. (Also I saw that I am able to recieve emails through Mailcow but not send them as expected)

@"classycraft3r"#p13829 If you would have rent VPS, you could adjust needed DNS setting for running a mailserver. Running a mailserver is quite different than running a simple webserver. Your friends IP is blacklisted because he has a DHCP IP assigned on his Modem. Long story short, you cannot run a mailserver behind ISP Modem/Router. period. Even mail is using SMTP (Simple Mail Transfer Protocol ) it's not so simple.

@"piperino"#p13830 So I should give up? There ain't no way to run it? Everything works fine except for the sending of emails. (Also, he has a fixed IP because his dad has his servers in his home too, as he owns a society and needs to make backups to his servers)

@"classycraft3r"#p13831 i don't want to disappoint you. but yes. don't try to run a mailserver behind an ISP modem. Look around for a cloud server with a static IP and start over if you're really interested in to have your own mailer. but believe me, if you're new to this topic it's a steep learning curve to get this properly done. :)

@"piperino"#p13832 I don't want to seem like a pushover, I also own a VPS with a fixed IP, but this is a complicated situation: My VPS is a VM on another VPS as my american boss gives me a VPS on his. If my memory's good he told me not to setup one, can't remember why. So I can't really setup one on it. Can I have the reasons why i can't run the mailserver behind an ISP modem? (curiosity, I don't wanna be annoying) Cause that's my almost only option, and best as we will soon buy a good server (64Gb ram, 6 CPU Cores, 1To storage NVMe) that'll be our primary server and will be on the home network, behind the ISP modem.

@"classycraft3r"#p13833 you should not do it because of the problem you currently facing. most prominent is the blacklisting. the majority of the well maintained mailservers out there are using RBL's and your would never be able to properly sending mails. The second reason is that your IP on the modem will change sooner or later. yes, you can go through the hassle and setup something like DynDNS or similar. but..... Better save your money and rent a VPS for 10euros instead of buying hardware and messing around behind an ISP Modem.

@"piperino"#p13834 I see. Also, the issue on my VPS, is that the host itself, the datacenter has the port 25 blocked and I (or my american boss) does not have a valid reason to have it open for a mailserver instead of getting a google workspace..

And if I have a fixed IP (which is the case, the operator allows advanced users to request one as they host servers on their network, which is our case), wouldn't it be possible?

@"classycraft3r"#p13843 A static ip is of course a step in the right direction. Just make sure it's not listed on any RBL's. And also sort out the PTR.

DNS resolving issue on Cloudflare

piperino

classycraft3r
PTR Records are only added in the in-addr.arpa. zones of the IP owner. But the A and PTR records should match.

Means you can put whatever PTR you want in cloudflare DNS, since they don’t own the IP Block it has no affect.

« Previous Page