But why expect the user to do that themselves? Shouldn't security be the default, with a secure configuration provided out of the box?
Giving the user a secure configuration which they can then opt out of if they wish does better by the user than giving them an insecure configuration and then asking them to opt in to security does.
Seriously, Debian is the upstream distro does this, and it's the other linux grandparent with RHEL. It's been around for decades, used in production the same way RHEL and BSD are, and we haven't had debian-based boxes compromised left, right, and centre with these 'insecure' defaults. The threat is imaginary, and not born out in real world numbers.
But Ubuntu doesn't come with a postfix server enabled by default, so that's not really a concern, is it?
* https://help.ubuntu.com/lts/serverguide/postfix.html
Here is where it is enabled by default:
* https://git.launchpad.net/postfix/tree/debian/postfix.postin...
And here is where the installation process auto-starts the server:
* https://git.launchpad.net/postfix/tree/debian/postfix.postin...
Technically, if security is your focus, then shouldn't one of your first actions after setting up a new machine be to set iptables default action to drop all incoming new,invalid packets anyway? I mean, I generally install server with nothing. Set up iptables. Then install packages and open ports.