A birds-eye view of Monit

Use your keyboard arrows to navigate or swipe on mobile

Some examples in this presentation might only work with a recent version of Monit. Please download Monit below or use your package manager to install the latest versio

atop , htop alternative

• lsscsi
• lsblk
• lsb_release
• lsusb
• lscpu
• lspci
• lshw / lshw-gtk
• ls
• lsof
• lsattr
• lshal
• lsinitramfs
• lsmod
• lspcmcia
• lswm
• lsdvd
• lslk
• lsmbox
• lscgroup
• lsdiff
• lspst
• lsdnssec
• lsmem
• lsdev
• lslocks
• lsar
• lslogins
• lsgpu
• lstopo
• lsipc

Snoopy is a small library that logs all program executions on your Linux/BSD system.

Developer documentation outlines how it actually does that (a fairly technical read). And don't miss the security disclaimer about it.

Very few technologies have persisted near to their original form as much as email services over time on the internet. It has been over 50 years since Ray decided to use the at symbol to designate a user and destination for electronic mail1. And while it has a few different skins, the fundamental concept and protocols remain largely unchanged to this day.

Given the lack of underlying evolution of email services, combined with the growth of ecosystems, there has been a dramatic shift to a seemingly monopolistic dominance of email services by Google, Microsoft and Apple (via Gmail, M365 and iCloud respectively). One major advantage enjoyed by users of the users of large providers is their price (free) and accessibility from anywhere (web and mobile applications). Combined with enhanced security capabilities and good spam mitigation, it’s completely understandable why we don’t really spend time thinking about non-mainstream email capabilities.

The scale of the larger operators is difficult to estimate, but it’s very safe to say that Google, Microsoft and Apple are responsible for the majority of email services online. As of March 2020, Google had 2 billion MAU alone2.

While Google and others provide easy access to email, it comes at a cost for other providers - to ensure safe delivery and reduction of spam across large user bases, the bar has been raised, and continues to be raised3 to successfully deliver email into each ecosystem.

Having recently had a small side project which required email capabilities whilst simultaneously wishing to avoid adopting any specific ecosystem, I set about building a self-hosted email solution.

I am a strong believer that very few problems that I face in life are unique, so I turned to the good folk at /r/selfhosted4 to find prior art relating to self-hosted email. What I found across dozens of threads relating to email capabilities was a mass of confusion, ad-hoc solutions, dodgy recommendations, delivery nightmares and general complexities intertwined with people who have successfully self-hosted mail for years without issue.

In short - mail hosting looked like a bit of a mess5.

The former systems administrator in me ended up wondering was it as hard as some on the subreddit asserted? Was it as easy as others suggest? Or does it land somewhere inbetween?

For the remainder of this essay, I will explore the basic design, build and deployment of Mail Transfer Agent (MTA) and Mail Delivery Agent (MDA) capabilities to host an informal email solution for a non-enterprise project.

Delegate self-service automation to
operate faster and eliminate toil

Rundeck is the open source core of Rundeck products. It's great for small
teams and getting started with runbook automation.

Unikraft is a fast, secure and open-source Unikernel Development Kit

By tailoring the operating system, libraries and configuration to the particular needs of your application, it vastly reduces virtual machine and container image sizes to a few KBs, provides blazing performance, and drastically cuts down your software stack’s attack surface.

process manager workers

router routeur wifi