Running a VPS, Log 5: It’s Not You, It’s Me

July 10, 2014

It is with great sadness that I announce today that I am breaking up with my mail server. At least for a little while, that is. Let’s say we’re “taking a break” to “see other people.”

I’m sorry to say so
but, sadly, it’s true
that Bang-ups
and Hang-ups
can happen to you.

Dr. Seuss

Don’t get me wrong, we’ve had a great run

I’ve learned so much from this foray into system administration and mail servers. I’ve written about some of these experiences, and yet many more will go unwritten. I’ve learned to persevere, to persist, and to have patience. I’ve learned to dig deeper, to follow the clues, and to ask for help.

If asked whether I would do it all again, I would say yes in a heartbeat. Even knowing what I know now, I’m sure that I would screw everything up all over again. Even still, this whole experience has given me the opportunity to plunge into a whole new sphere of discovery, affording me such immense and immersive exposure that would be too much to turn down given a second chance.

If asked whether I would recommend it to a friend, I would flinch for a second, but undoubtedly answer yes in the end. Sure, there are gentler introductions to some of the sysadmin roles I assumed for this project, and there are certainly more glamorous projects for a beginner which yield immediate and visible results, results that can be shown off and shared.

That being said, few projects lend such a sense of belonging in a community, such a sense of having begun a “rite of passage,” as hosting your own mail. For one thing, it’s hard. Trying to mangle to your will the archaic technologies involved in serving mail bend is perhaps one of the most complicated and intensive feats which can be contained under the category of personal VPS projects. More than that, being able to say, “This mail is mine, for me, and only me,” is an incredibly rewarding yet private experience. It’s something no one can take away, something no one can intrude upon.

But I’m just not ready for this kind of commitment

I initially thought this project would take 3 days, perhaps a week tops, given that the original title of the tutorial was “NSA-Proof Your Email in 2 Hours. Somehow, this endeavor has managed to encompass fully two and a half weeks. I’m not saying that I’ve been working exclusively on this project for that time, and I’ve certainly been learning a great deal, but I can feel the marginal returns diminishing as time marches ever forward. As much as I hate to admit it, the summer is already half-way over for CMU students, and there are still so many technologies, projects, and gadgets that I want to sink my teeth into.

Another remark about “being a sysadmin”: it’s stressful! I would be working on fixing something while ssh’ed in to my droplet, and I could see the stream of spammers and attackers trying to get through on random ports. While I had the appropriate firewall protections in place, it’s thoughts like these that making falling asleep harder: “What if I’ve missed something? What if my system is critically vulnerable? How long do I have before everything comes crashing down?” Stress culture aside, this is not a weight I want to shoulder regularly.

Do you think we can still be friends?

Ultimately, I had to make the choice to put this project on the back burner. That does not mean, however, that its flame has been snuffed entirely. This project has been incredibly rewarding, and I’m still crazy-determined to get this system working. I mentioned before how “privately rewarding” it can be to serve one’s own mail–I’ve as of yet only had a taste of this goal, and I will return one day to reap it’s full rewards. When this day will be, though, I’m not sure.


If you’ve been following along this series and you’ve tragically decided to follow a similar path as that which I have followed, feel free to chat me up about it! I’d be more than happy to offer some support, or give you advice on some resources to look at. I can’t say that I’ll answer every question, else I would have a working system, but hopefully I have managed to scrounge up something to make your life easier. See below for ways to get in touch.

Jake on the Web

If you cared enough to read that far, you should consider following me on GitHub or paying a visit to my homepage. If this post was about one of my open source projects, make sure to star it on GitHub! I love hearing what people think, so feel free to open an issue or send me an email.

Haskell Development with Neovim

After a year and a half of using Haskell on and off, I’ve finally settled on a set of high-quality development and editor tools, using Stack and Neovim. Continue reading

Reach for Markdown, not LaTeX

Published on February 26, 2017

Troubleshooting Haskell Stack Setup on OS X

Published on August 03, 2016