Ports, rules, NAT
-
Running an email server out of home connection, while can be a useful learning experience - not going to be very useful if your actually wanting to send mail from your "home" ip..
Most consumer IP blocks are listed and major players block them for accepting mail. Also unless you can edit your PTR for the IP in question - again blocked by most major players.
So sending would need to be through a relay if you want to actually send mail to major domains.
Have fun! And you have any questions, while the general section doesn't get all that much traffic... Some of us like to answer just general networking and IT questions not always related to pfsense, etc. ;)
-
i have a mail server myself at home for fun
fortunately I have never encountered any problems, my ip is not in any blacklist and even if i can't change my ipv4 ptr, i have a ipv6 tunnel with he.net and they let you change it. i just need to be sure that my email server use ipv6 to send emails -
There are a shitton of major players email that is not on ipv6.. And pretty much every isp consumer IPs are listed as such.. But sure you might be lucky there.. But no ptr is can be a killer..
Other than a toy/learning experience running mail servers off a home connection is pretty pointless.
-
Apologies, didnt realise I would have to cover that, was purely providing a little background.
I have a VPS I relay through, that has correct rDNS, SPF, DKIM, DMARC all setup and working, including TLS 1.2
I've been running exchange for almost 10 years this way, have my own domain, they are secure and get A+, I do not suport any less than TLS 1.2 etc. I run Nessus (community edition) and OpenVAS against my network regularly.
Almost everything I do in my lab is to mimic work, its the first place I apply security patches and PCI fixes, if I break my lab no one gets hurt, if I take a business down, it's my problem and I get it in the neck, so I practise at home first (where possible)
Do apricate the additional feedback though..
P.S. while I dont generate crazy amounts of traffic, I am all for securing my system more effectively- those tools mentioned above will be looked at better when I have more dedicated time.
And just in case anyone asks, exchange is covered, as are all my Windows licenses under an MDSN subscription by work for the sole purpose of learning. :)
Side note, if I can do the same thing as work, but for free, I often take this option. Certificates = Let's Encrypt (currently I have a paid one), email filtering - also free, firewall (from home router to PfSense), VPN - OpenVPN.
I like free and opensource, so use it as a 'similar' to works paid enterprise products.
P.P.S (expect me asking for help), my next plan is to remove the IIS proxy and move my HTTPS traffic to either Squid or HA via PfSense to be my reverse proxy. If I can do it for free and consolidate, meaning I need to manage and maintain less, I'm all for it.
-
FYI, work are moving to O365 in the near future, so my requirement to run and learn exchange may also go away, at which point I will likely start looking at putting email on my VPS server, using something else hosted at home that is free or just leaving it as is until it becomes EOL - I'm not at that stage yet though.
-
yes of course
at home i'm using it only for toy/learning experience/test etc etc
sure not something to do for work where we have professional ip with rdns and stuff configured as it should
