@nikla said in How to configure mail server behind pfsense router:
I have been running my mail server on a server/NAS at home since 15 years. I do it to motivate myself to learn things.
You might be correct when advise me not to run a server exposed on internet at home.
I still believe that it is possible to run a server at home using a pfSense router in front of a NAS. I still fail to configure that so my question remains.
I just wanted to warn you, that using a 'mail server at home, behind an ISP type WAN IP' is cumbersome.
It's excellent for the "how to do so" and "learn" practises, I agree.
But as soon as you get the hang of it, you want an always-on solution, which means : no bad ISP land lines problems, No DNS issues, no power issues, no drive-went-bad issues : you don't want to bother with all the hardware details. You want to be reachable (by mail) at all times, even when you go off the beach for a couple of days.
That's why advise the "2$ / month solution".
For my, my Synology devices are just used for what they are meant to be : backing up local devices.
Btw :
NATting port 25 TCP to an internal device
is like
NATting port 143 TCP to an internal device
is like
NATting port 110 TCP to an internal device
is like
NATting port 993 TCP to an internal device
etc etc
Just that one number changes.
About the certs (from Letenscrypt) : The pfSense package 'acme.sh' is handling the renewal.
Every 60 days or so, when I get a mail that informs me that the cert "*.mydomain.tld" has been renewed, I export the two new 'cert' files, and import them in my Synos.
True, this is a manual operation and I have one month (after renewal) to do so.
I actually do not really need 'known' certs on my Syno, self signed or over-time certs will get flagged by my browser (if I didn't create an exception for my internal 'LAN-bases' internal devices, as I do trust them anyway).
You can probably also have the Syno ask for 'letensrypt' certs.