Thoroughly looking forward to seeing how this pans out.
Although going through the more beginner-friendly approach, such as using YUNoHost for setting things up for you I'm hoping that you go through the CLI equivalents to illustrate how it's done there, too.
When I was learning how to administrate Windows Server in uni, Server 2003 was available and there were additions that allowed you to do some of the aspects through the GUI. However, we were taught using Server 2000, which required that extra bit of configuring throughout. I felt like this actually gave a better understanding of how things were configured in the server OS. Like, for example, you could run dcpromo with Server 2003, without running any prerequisites and it would tell you that it can automatically make a basic configuration for DHCP and DNS. While that will get you up and running, going in and making the DNS/DHCP configurations yourself gives you that extra bit of insight and control over what you're doing.
Correct me if I'm wrong but it's more likely that in the industry people will come across the CLI versions of the software that they will have to maintain, rather than installing the GUI implementation or, if they have something else on there, like cPanel, then they can translate what they've learned. Not sure how that fits in - anyone else got any takes on this?
Anyway, I digress.
I'd love to get this underway myself and will likely get started on this pretty soon. Getting up and running with a server that hosts my website (and going over the website itself) would be great to get under my belt and adding in the necessary security aspects as well, rather than depending on a server host to do it all for me.
I think for the email side of things I'd like to experiment at some point in implementing an alternative to MS Exchange that would sit connected in a Windows domain - get some VMs set up for the Windows server, connect it up to a Linux box, etc. Long-term personal task to set myself that I think would be interesting to do.
For hosting my own email accounts long-term, I'm not really sure - depending on a large-name organisation like MS, Google, etc, etc means that there's a pretty high reliability already in place. That's really going to depend on how well you configure the server though and how much you rely on an email address with your own domain. Pros and cons but still, would be great to see how to do it properly.
To add on to the choice of server host, take note of where they're based and whether you're likely to need to get in contact with their support team. With Digital Ocean, for example, they operate on US time so their support team aren't available in UK mornings. Whether you're likely to need to get in contact with them is another thing entirely, however, as they control the servers themselves, not the operating systems or software that's installed on them. So, if the node's down, you can't access it via SSH or their shell on their website and you need to get in contact with them before US hours then you might want to consider a different host (that's a lot of ifs and would really only matter in worst-case scenarios and if you need the immediate response). However, under normal circumstances, Digital Ocean's a pretty good choice because they're low-cost, have a shell on their website in case you lock yourself out in some way via SSH and they have decent tutorials for getting you up and running with software. I haven't used Linode before so I can't say either way - do they have shell access in case you lock yourself out of SSH?
tl;dr - I waffled. You missed nothing.