You are amazing in teaching, period. I've spent numerous hours reading this, reading that, many enthusiasts' websites on "How to", yet none of them were able to share the information the way I find it right - sharing it in such a way in order to teach the other side. Thank you! You did great! My server is running right now and it's receiving all the emails (tested).
25:48 - you just made me flashback to a Better Call Saul scene with that word "truly". "is there no other way, truly?" this sentence lives in my heart rent-free
thank you! mailcow has made the process so easy that its a no brainer for a tech company to run their own mail server - especially if privacy matters to your organization. now need to look into backups.
Hi Karsten, das ist das genialste Tutorial, dass ich jemals zu dem Thema gesehen habe. Du hast damit meinem Mailserver Projekt krassen Rückenwind gegeben. Tausend Dank dafür. Das ist so kurzweilig und cool gemacht und hat zwischen den Parts, die ich schon kannte, die Brücken gebaut. Genial.
Awesome tutorial, I did this as self-hosted on proxmox vm. I only needed additional port forwarding, edits to my reverse proxy and also my domain name host screen layout looked different to the one used, but it came up as in the tutorial. Scored 10/10 on the email test. Great job on the video.
Seriously good job at explaining the process - although I installed mine on a ubuntu platform, most of it was the same - so thanks for your video tutorial. It helped a lot!
I love the content. I have one bit of unsolicited constructive criticism though, and I only am saying this because I believe you will succeed in this RU-vid game: I would back off a bit on the zoom cuts. If you do it too often, it can become distracting. I would use it to add emphasis only on particular points or when the subject is changing or taking a slight detour. Great camera angle and your technique is on point too, just over used. Most important of all, you're a good speaker and the content is top notch. Keep up the good work, my friend! I'm your 777th subscriber!
One of the best tutorials I have seen in years of watching. No extraneous babbling, just the facts. Seriously, this was excellent. My only mild complaint is the background music, especially one part where it had vocals. I am hard of hearing anyway, and have to focus to hear the narration. Thanks so much, and praying for your safety in these troubled times for the Ukraine!
Thank you for your excellent tutorial, Mr Opentaq. 🙏😎 Sound quality was plenty good enough and your explanations were very helpful. One thing I ran into after the main installation was done was the need to set up an SMTP relay server for my VPS. I couldn't send any email without doing this. This can now be done in the Mailcow UI. There's a section in the mailcow docs under Postfix and Relayhosts. Apart from this, I had a few other things to sort out. I'm testing mailcow on a 2GB RAM server which meant I had to disable ClamAV to prevent out-of-memory situations. I realise this is not recommended for a production email server but it has seemingly been fine for testing and has allowed me to familiarise myself with the rest of the mailcow services.
By far one of the better mail server tutorials that I have had the pleasure of sitting through. Wonderful. Thank you for sharing your time and expertise with us. Much appreciated.
Thanks so much for this video. Every other video I found about a mail server was installing a server that had no GUI. Thisa make it so much easier. Liked & subscribed!
@@kennethlau8108 In the beginning i used AWS Lightsail, but now i moved my box to Hertzner, they have better deals and overall i feel the performance is better. For Hertzner you have to wait 1 month for your account to be able to open port 25.
Hello and thank you very much for the clear and simple guide, but I wanted to ask you if you could also add the guide for port forwarding that needs to be done on your home router (provided that you always need to have a static public address) and if NGINX Proxy is also present Manager what should he manage and how? Sorry for too many questions but I think this part should be explored :-) Thank you very much
Mooohooooo it works !!!! Thank you so much ! (I am on this for almost 1 month already...) I still have to fix these anoying email blocking and spam categorization, but I can send and receive mails :)
I setup the same in ec2 instance and one more local machine. It is working fine. When I am working on the production it is not working ans expected. After adding the DNS. while clicking in the DNS ( to see the record). It is showing 504 gateway time out error. Do have any idea?
For better security don't setup a root password when installing Debian. If you skip this and only setup a user account the root account will be disabled and you'll get root access on the user account when using the sudo automatically. You may also want to enable automatic updates by installing and configuring unattended-upgrades.
I managed to get everything but the DNS setup by myself. But this tutorial is awesome and I wish I had used it for the whole setup. Regardless, thanks for the help with the DNS portion!
You are a marvellous person, thank you for the video. I understand almost everything that you said, and it was quite useful for me. A few times I skiped a content, and got lot of waste of time then, so It was a little funny to find solution of my problem in a passage of the video that I skiped :)
Excellent tutorial; saved me a ton of time! Got this running and created a few mail boxes with a password that the users should change on first login. What config changes do I make to require users to change their passwords on first login? Appreciate any help. I didn't see any UI elements on the webmail client to change the password.
I liked, subscribed and HIT the notification bell! Can you go a bit deeper on the rest of the DNS settings? btw, I like the female vocalist's voice in your background music. What is it?
Why didn't you used port 587? Like these ports are supposed to used for SMPT delivery rather than port 25 which is SMPT relay and is blocked by most ISP and Cloud Providers.
Great tutorial!! Question tho.. would using a service like no-ip or duckdns work for setting this up in my home lab? I really dislike the idea of having a monthly bill of using a VPS and I find the cost of using no-ip way more affordable
Running Mailcow on homelab🤓 and use VPS as a Reverse-Proxy. Full control over Storage on your local server without paying extra for Cloud Storage which is also not under your control! It's like a Portforwarding from your Local Server to the VPS that expose anything of your Mailserver for you. You just manage the tunnel and mailserver on-Premise without anything extra in the Cloud! If something is suspicious you just need to cut off the Tunnel to your VPS and anything is safe again.
not working for me. When sending a mail, I got "orange screen with ERROR" but no error description... When login the admin panel, I checked all logs but no error reported in postfix or any other section. So mail is not sent and I have not idea why... However thks for this very clean and detailed video
Great tutorial, I got issues with mailcow's web GUIs (admin andwebmail) with port 80 and 443 since I already had a web server running, just change them on mialcow's configuration and now its fine. Also got problems sending emails since my server is hosted by vultr and by default they block the SMTP ports (solved by opening a ticket explaining I will not be a spammer).
I followed the tutorial to build the mailserver, it's working properly but i can't connect through smtp with a mail client, please what could be the issue.
Prefect !, With German precision. I've watched lots of other videos that skip some parts so you end up without a worker server. A second part might add a spam filter ? Just an idea ...
I have a setup with virtual hosts but with a dedicated IP address for this. How do I go about setting this up on an existing server I'm running with virtualhosts and apache2
I've started using Cloudflare Tunnel for 3 of my domains, and it effectively masks your home IP and does not require a static IP. Would this work for a mailserver as well?
salam alaikoum, Thank you for this wonderful tutorial, I hope doing well, I just have question after searching for what reason allowing the port 4190 (ManageSieve Protocol).
Do you know of any information on how to migrate my email domains away from Exchange 2007 to mailcow. I have mailcow set up per this tutorial but having trouble getting the correct mail server to show in the mailcow dns recoreds. It keeps wanting to show the exchange server even after all the dns records are set and the mailcow server is set with a lower priority level than the exchange priority. Any hints or references are appreciated.
Hi, super Anleitung. Was aber interessant wäre - Mailcow in Verbindung mit Proxy wie z.B.: Proxmox Mail Gateway nutzen oder Mailcow selbst mit MTA-STS benutzen, was wäre sinnvoller ?
Hi i got an error: dovecot-mailcow Cannot start service dovecot-mailcow: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting rlimits for ready process: error setting rlimit type 6: operation not permitted: unknown
I am confused at 8:27 part, is it ssh from my VM to my PC? or from my PC to its VM? I am just confused what machine we are referring to. sorry for being newb
This is incredible! I am now able to send emails through my own domain, but I don't seem to be able to recieve anything. Any pointers as to what I might be doing wrong or missing?
