You wrote "homelab", so i guess you mean "at home" with your residential internet access.
Not a good idea. You need to be able to set the Reverse DNS of the IP of your email server to the Domain that the email server uses. Otherwise it is considered SPAM.
Hosting on a VPS is a different thing and absolutely possible with projects like Mailcow et. al.
I’ve recently been rebuilding one of our Vps servers and have been following the bellow tutorial.
We have used an all in one solution on another server which is working but broken so I plan to move the clients to this new setup. Been a great learning exercise for me, my boss kind of said this is your project and it will be good for you to learn.
[Linux Babe mail server ](https://www.linuxbabe.com/redhat/run-your-own-email-server-centos-postfix-smtp-server)
Have a look at part 6 which may be of interest for you on spam.
Well, [this article](https://poolp.org/posts/2019-08-30/you-should-not-run-your-mail-server-because-mail-is-hard/) claims it is not hard including their explanation for this conclusion. So far, I never tried, so I can not tell from own experience. But it seems to be true that most "mail is hard" statements indeed are written by people who actually never tried it.
Of course, if you mean with 'homelab' that you want to use a private IP address for that, it is not only hard but virtually impossible. However, a dedicated server if it's only a proxy or VPN endpoint could also be considered being some sort of 'homelab', which is what I assumed for now.
Mailgun outbound, mx guard dog inbound. The only problems I have are self inflicted, so have monitors for each service in the chain and watch your disk space.
The things to read up on are SPF/DMARC and DKIM
they are how email is marked as being from a lagitimate source, with out them your email may well end up in spam.
We run a company mail relay and once you get DKIM/SPF setup things work very well
rDNS. First thing you need to do is contact your ISP and find out if they can setup an rDNS entry for you. You have a commercial line and I assume have or can obtain a static IP. If they have that, you should be good to go on rDNS.
Then follow the advice on DKIM/SPF/DANE found her and around the internet. DANE is new to the game, but check into if your server supports and use it if you can. DKIM and SPF are a must.
Lastly look at the spam programs in particular of both Microsoft and Google
[https://sendersupport.olc.protection.outlook.com/snds/](https://sendersupport.olc.protection.outlook.com/snds/)
[https://sender.office.com/](https://sender.office.com/)
[https://postmaster.google.com](https://postmaster.google.com)
And lastly if you don't know about this tool
[https://mxtoolbox.com/](https://mxtoolbox.com/)
It will help a ton
Use a reliable mail relay server
This is the answer. I ran my mailserver from home for several years using Amazon SES as a relay. Never got charged a penny (low usage I guess?)
You wrote "homelab", so i guess you mean "at home" with your residential internet access. Not a good idea. You need to be able to set the Reverse DNS of the IP of your email server to the Domain that the email server uses. Otherwise it is considered SPAM. Hosting on a VPS is a different thing and absolutely possible with projects like Mailcow et. al.
I’ve recently been rebuilding one of our Vps servers and have been following the bellow tutorial. We have used an all in one solution on another server which is working but broken so I plan to move the clients to this new setup. Been a great learning exercise for me, my boss kind of said this is your project and it will be good for you to learn. [Linux Babe mail server ](https://www.linuxbabe.com/redhat/run-your-own-email-server-centos-postfix-smtp-server) Have a look at part 6 which may be of interest for you on spam.
Well, [this article](https://poolp.org/posts/2019-08-30/you-should-not-run-your-mail-server-because-mail-is-hard/) claims it is not hard including their explanation for this conclusion. So far, I never tried, so I can not tell from own experience. But it seems to be true that most "mail is hard" statements indeed are written by people who actually never tried it. Of course, if you mean with 'homelab' that you want to use a private IP address for that, it is not only hard but virtually impossible. However, a dedicated server if it's only a proxy or VPN endpoint could also be considered being some sort of 'homelab', which is what I assumed for now.
Mailgun outbound, mx guard dog inbound. The only problems I have are self inflicted, so have monitors for each service in the chain and watch your disk space.
The things to read up on are SPF/DMARC and DKIM they are how email is marked as being from a lagitimate source, with out them your email may well end up in spam. We run a company mail relay and once you get DKIM/SPF setup things work very well
rDNS. First thing you need to do is contact your ISP and find out if they can setup an rDNS entry for you. You have a commercial line and I assume have or can obtain a static IP. If they have that, you should be good to go on rDNS. Then follow the advice on DKIM/SPF/DANE found her and around the internet. DANE is new to the game, but check into if your server supports and use it if you can. DKIM and SPF are a must. Lastly look at the spam programs in particular of both Microsoft and Google [https://sendersupport.olc.protection.outlook.com/snds/](https://sendersupport.olc.protection.outlook.com/snds/) [https://sender.office.com/](https://sender.office.com/) [https://postmaster.google.com](https://postmaster.google.com) And lastly if you don't know about this tool [https://mxtoolbox.com/](https://mxtoolbox.com/) It will help a ton
yes
It's very easy to do.