Deep Dive

Running your own email server has long felt like one of the most intimidating tasks in IT—fragile, overcomplicated, and dangerously easy to misconfigure. In this episode, we explore Chasquid, an open-source mail transfer agent built to challenge that reputation by making secure self-hosted email practical for individuals and small organizations.

Chasquid takes a radically different approach from older mail servers like Sendmail, Postfix, or Exim. Instead of decades of layered complexity, it is built in Go with a philosophy of security through simplicity. Its developers intentionally narrowed the scope so it can serve small teams well, while eliminating many of the configuration traps that have historically made email hosting such a nightmare.

We break down the key guardrails that make this possible: hard-coded protection against open relays, mandatory encrypted authentication, built-in TLS support with Let’s Encrypt, and defenses against downgrade attacks by tracking per-domain encryption history. We also look at native support for standards like SPF and DKIM, which help prove your mail is legitimate and protect your domain’s reputation.

Beyond security, Chasquid includes practical features that make it genuinely usable: support for multiple domains, internationalized email addresses, suffix dropping for tagged inboxes, and extensibility through hooks for spam filtering, antivirus, and greylisting. Its built-in tracing and monitoring tools also make troubleshooting far more transparent than with traditional mail servers.

This deep dive shows how Chasquid transforms self-hosted email from a fragile legacy nightmare into a modern, approachable system—one that gives smaller organizations a realistic path toward independent, secure communication infrastructure.

Let’s have a look at your digital challenges together. What tools are you currently using? Are your processes optimal? How is the state of backups and security updates?

Digital Souvereignty is easily achived with Open Source software (which usually cost way less, too). Our division Safeserver offers hosting, operation and maintenance for countless Free and Open Source tools.

Try it now!

What if one of the most critical systems in your organization is still running on decades-old complexity nobody wants to touch? In this episode, we dive into OpenSMTPD, a modern open-source implementation of the server-side SMTP protocol that shows how email infrastructure can be rebuilt with simplicity, security, and transparency at its core.

OpenSMTPD was created out of frustration with older mail servers that had become bloated, difficult to configure, and increasingly hard to secure. Developed within the OpenBSD ecosystem, it reflects that community’s philosophy of clean code, proactive security, and minimal design. Instead of treating complexity as unavoidable, OpenSMTPD rethinks mail routing as something that should be understandable and manageable.

A major focus of the episode is the software’s security architecture. Built primarily in C, OpenSMTPD addresses the risks of low-level system programming through privilege separation - splitting the public-facing and sensitive internal components into separate operating system users. This design assumes software can fail and contains the damage if it does, dramatically improving security for a network-facing service.

We also explore why OpenSMTPD lowers the barrier to entry for self-hosting. It supports a wide range of Unix-like systems, can be installed through standard package managers, and replaces the chaos of legacy mail server configuration with one plain-text configuration file and a single unified control tool. Its compatibility features even allow older scripts written for legacy tools like Sendmail to keep working without modification.

This episode is about more than mail servers. It is about what happens when developers reject decades of accumulated bloat and prove that even foundational internet infrastructure can be rebuilt in a cleaner, safer, and more transparent way.

Let’s have a look at your digital challenges together. What tools are you currently using? Are your processes optimal? How is the state of backups and security updates?

Digital Souvereignty is easily achived with Open Source software (which usually cost way less, too). Our division Safeserver offers hosting, operation and maintenance for countless Free and Open Source tools.

Try it now!

What happens when a regulator, auditor, or opposing counsel demands a specific email from years ago - and your organization cannot produce it? In this episode, we dive into Piler, an open-source email archiving platform designed to turn chaotic corporate email history into a secure, searchable, and legally reliable system of record.

Piler tackles two massive enterprise problems at once: storage bloat and retrieval speed. Through deduplication and compression, it dramatically reduces archive size by storing identical attachments only once and indexing the rest with lightweight references. At the same time, its full-text search engine makes it possible to locate specific messages - or even phrases buried deep inside attachments - in seconds rather than hours.

But archiving is not just about storage. It is about trust. That is why Piler includes tamper-evident protection through cryptographic hashing, ensuring that archived emails cannot be altered without detection. Combined with retention policies, legal hold features, encryption at rest, TLS in transit, access controls, two-factor authentication, and full audit logging, the platform is built to satisfy the strict demands of compliance, litigation, and data governance.

We also explore how Piler integrates quietly into existing environments, supporting SMTP capture, IMAP and POP3, Office 365, Google Apps, Active Directory, LDAP, and single sign-on. That means organizations can gain a hardened archive without disrupting the day-to-day workflow of employees.

If email is the memory of an organization, this deep dive shows why archiving is no longer optional - and how open-source infrastructure like Piler can make that memory secure, searchable, and legally defensible.

Let’s have a look at your digital challenges together. What tools are you currently using? Are your processes optimal? How is the state of backups and security updates?

Digital Souvereignty is easily achived with Open Source software (which usually cost way less, too). Our division Safeserver offers hosting, operation and maintenance for countless Free and Open Source tools.

Try it now!

What if your company’s email system didn’t have to be a fragile stack of legacy software and single points of failure? In this episode, we dive into WildDuck, an open-source mail server that radically rethinks email infrastructure for large-scale organizations.

WildDuck is an opinionated email platform, meaning its developers made strong architectural choices up fron - largely inspired by how Gmail handles scale. Instead of relying on traditional file-based storage and fragile server configurations, WildDuck stores email in a distributed MongoDB cluster, uses stateless application servers behind a load balancer, and is built specifically for horizontal scaling and no single point of failure.

We explore how that architecture changes everything. By separating message text from heavy attachments, WildDuck can keep inbox searches fast on SSDs while storing large files on cheaper disks, dramatically reducing infrastructure costs. Its API-first design replaces old-school configuration files with modern web-based control, making large-scale automation and management far more flexible.

Security is another major focus. Built in Node.js, WildDuck benefits from memory-safe architecture and avoids many of the file-system and shell-level attack surfaces that plague traditional mail servers. It also supports application passwords, multi-factor authentication, GPG-based message encryption, rate limiting, and modern Unicode support, making it both globally capable and enterprise-ready.

This episode shows how open-source infrastructure like WildDuck is making it possible for organizations to reclaim their communications stack - with the performance, resilience, and control once reserved for tech giants.

Let’s have a look at your digital challenges together. What tools are you currently using? Are your processes optimal? How is the state of backups and security updates?

Digital Souvereignty is easily achived with Open Source software (which usually cost way less, too). Our division Safeserver offers hosting, operation and maintenance for countless Free and Open Source tools.

Try it now!

Sending an email feels instant and effortless - but behind that simple click is a vast layer of open-source infrastructure that quietly keeps the internet running. In this episode, we dive into Exim, one of the world’s most important mail transfer agents, and explore the invisible machinery that routes, filters, and secures email at global scale.

Exim operates behind the scenes as a message transfer agent (MTA), the software responsible for moving email from server to server across the internet. Originally developed at the University of Cambridge, it became a major alternative to Sendmail by offering greater flexibility, extensive routing options, and powerful controls for checking incoming mail. Today, it remains a foundational part of internet communication - even if most users never see its name.

We unpack the architectural realities of running software like this: a codebase written primarily in C, optimized for speed and low-level system control, but demanding constant vigilance because of the security risks that come with manual memory management. That tension becomes especially clear in the episode’s discussion of a recent remote heap corruption vulnerability, and why the Exim team takes such a hard line on obsolete versions.

But this deep dive is about more than software internals. We also explore Exim’s recent decision to leave GitHub and move to a self-hosted Forgejo instance, a major act of digital independence that reflects a broader concern in open source: foundational internet infrastructure should not depend on centralized corporate platforms. Combined with self-hosted bug tracking and traditional mailing lists, Exim’s development workflow reflects a deep commitment to open, independent systems.

At its core, this episode is about the hidden communities that maintain the internet’s essential infrastructure—and the urgent question of what happens when those communities must hand that responsibility to the next generation.

If you’ve ever wondered what really happens after you press “send,” this deep dive into Exim reveals the open-source systems - and the people - quietly making global communication possible.

Let’s have a look at your digital challenges together. What tools are you currently using? Are your processes optimal? How is the state of backups and security updates?

Digital Souvereignty is easily achived with Open Source software (which usually cost way less, too). Our division Safeserver offers hosting, operation and maintenance for countless Free and Open Source tools.

Try it now!

What happens when legacy hardware can no longer send email because modern cloud providers have tightened security? In this episode, we dive into Email Relay, a lightweight open-source mail proxy that helps old devices like scanners, switches, and monitoring systems continue to send alerts securely in a modern infrastructure.

Email Relay acts as a local middleman between legacy equipment and strict upstream providers such as Microsoft 365 or Google Workspace. Older devices can send simple, unauthenticated messages to Email Relay on the local network, and it then upgrades those messages with modern authentication, encryption, and routing before forwarding them onward. This makes it possible to preserve expensive hardware investments without replacing perfectly functional equipment just because email standards have changed.

We explore how Email Relay achieves this with a remarkably efficient architecture. Built in C++ and using a non-blocking I/O model, it can handle large volumes of mail traffic with minimal system resources - making it practical even on modest hardware. Its policy-free design also gives administrators full control over routing and filtering logic, rather than forcing them to work around hard-coded assumptions.

The episode also examines the platform’s flexible filter system, built-in tools for routing and splitting traffic, and integrations with SpamAssassin and address verifiers to protect against spam and abuse. Security features like TLS encryption, PAM authentication, and optional proxy or Tor routing make it suitable even for sensitive environments.

Finally, we look at real-world user reports that validate its stability and scale - including deployments that have run for years without crashing and others that process hundreds of thousands of emails per day.

If you’ve ever wondered whether a small, open-source tool can replace bloated proprietary mail infrastructure, this deep dive into Email Relay shows just how powerful a focused, efficient design can be.

Let’s have a look at your digital challenges together. What tools are you currently using? Are your processes optimal? How is the state of backups and security updates?

Digital Souvereignty is easily achived with Open Source software (which usually cost way less, too). Our division Safeserver offers hosting, operation and maintenance for countless Free and Open Source tools.

Try it now!

What if tracking your reading didn’t mean handing your habits, reviews, and recommendations over to a giant corporate platform? In this episode, we explore BookWyrm, an open-source, federated social reading platform that offers a community-driven alternative to services like Goodreads.

BookWyrm lets readers track books, log progress, write reviews, set reading goals, and share updates - but with a fundamentally different philosophy. Instead of feeding algorithms and ad systems, it is designed for high-trust communities, where recommendations come from real people and users control who can see their posts through granular privacy settings.

A major part of BookWyrm’s power comes from federation. Built on the ActivityPub protocol, individual BookWyrm servers can communicate with one another while remaining independently owned and operated. That means a small private book club can still interact with readers on other servers - and even connect with people on platforms like Mastodon - without relying on one centralized corporation to control the network.

We also dive into the technology behind it: a backend built with Python, Django, and PostgreSQL, asynchronous communication handled by Celery and Redis, and a deliberately lightweight front end using Django templates, Bulma, and minimal JavaScript. The result is a platform that prioritizes accessibility, resilience, and user control over trend-driven complexity.

Most importantly, BookWyrm points toward a different future for online culture: one where communities own their infrastructure, preserve their conversations collectively, and build a shared literary record that isn’t dependent on the survival or policies of a single company.

If you’ve ever wanted a social reading platform that feels more like a trusted local book community than a data-mining algorithm, this deep dive into BookWyrm shows what that future could look like.

Let’s have a look at your digital challenges together. What tools are you currently using? Are your processes optimal? How is the state of backups and security updates?

Digital Souvereignty is easily achived with Open Source software (which usually cost way less, too). Our division Safeserver offers hosting, operation and maintenance for countless Free and Open Source tools.

Try it now!

For years, self-hosting email meant stitching together a fragile patchwork of outdated tools - mail routing, storage, spam filtering, calendars, contacts - all running separately and barely cooperating. In this episode, we dive into Stalwart, a modern all-in-one mail and collaboration server that rethinks that entire model from the ground up.

Stalwart replaces the traditional maze of disconnected components with a single unified system, managed through one configuration and built in Rust, a language designed for memory safety. That architectural choice matters: it eliminates entire classes of vulnerabilities that have plagued legacy mail infrastructure for decades, making the server both more stable and dramatically harder to exploit.

We explore how Stalwart secures data at every level. Emails can be protected with OpenPGP or S/MIME encryption at rest, secure transport is maintained through automatically provisioned TLS certificates via ACME, and modern synchronization is handled through JMAP, a protocol that enables fast, real-time updates across devices without the constant polling overhead of older systems like IMAP.

The episode also examines Stalwart’s advanced security stack for the modern threat landscape. Built-in support for SPF, DKIM, and DMARC helps verify sender authenticity, while LLM-assisted spam filtering, collaborative digest systems like Pyzor, and defenses against homograph attacks help detect phishing and malicious messages before they ever reach the user.

Finally, we look at how Stalwart scales - from a small deployment using SQLite all the way to large enterprise environments backed by distributed databases like FoundationDB. The result is a platform that makes secure, sovereign, self-hosted communications far more practical than ever before.

If you’ve ever assumed that controlling your own email infrastructure had to mean complexity, fragility, and pain, this deep dive into Stalwart shows why that assumption may no longer hold.

Let’s have a look at your digital challenges together. What tools are you currently using? Are your processes optimal? How is the state of backups and security updates?

Digital Souvereignty is easily achived with Open Source software (which usually cost way less, too). Our division Safeserver offers hosting, operation and maintenance for countless Free and Open Source tools.

Try it now!

Silent failures are one of the most dangerous risks in modern systems - when critical jobs stop running and no one notices until it’s too late. In this episode, we explore healthchecks.io, an elegant open-source solution that turns background tasks into actively monitored systems.

At the core is the “ping model”: every scheduled job sends a simple HTTP request when it completes successfully. If that ping doesn’t arrive within an expected timeframe, the system assumes failure and triggers an alert. This shifts monitoring from reactive log-checking to proactive detection of missing signals.

We break down how to configure effective monitoring using key concepts like period (expected run interval) and grace time (buffer for delays), and how these combine to prevent false alarms while still catching real failures. The system’s state model - up, late, and down - ensures alerts are meaningful and reduces notification fatigue.

Beyond cron jobs, healthchecks.io can monitor a wide range of systems, from Kubernetes jobs and CI pipelines to IoT devices and simple server health checks. Its flexible integrations - Slack, PagerDuty, email, webhooks, and more - ensure alerts reach the right place at the right time.

Finally, we explore the trade-offs between using the hosted service and self-hosting the open-source version, where greater control comes with added responsibility for security, maintenance, and infrastructure management.

If you rely on scheduled tasks, this deep dive shows how a simple concept - monitoring by absence instead of presence - can eliminate one of the most costly and invisible failure modes in software systems.

Let’s have a look at your digital challenges together. What tools are you currently using? Are your processes optimal? How is the state of backups and security updates?

Digital Souvereignty is easily achived with Open Source software (which usually cost way less, too). Our division Safeserver offers hosting, operation and maintenance for countless Free and Open Source tools.

Try it now!

Running your own email server has long been considered one of the most complex - and frustrating - tasks in IT. In this episode, we explore Mailcow: Dockerized, an open-source mail server suite that simplifies this challenge by packaging all essential components into a single, containerized system.

Mailcow combines critical email infrastructure - Postfix (sending), Dovecot (receiving), Rspamd (spam filtering), ClamAV (antivirus), and SOGo (webmail and groupware) - into isolated Docker containers. This approach eliminates dependency conflicts, simplifies updates, and makes deployment far more accessible, even for those new to self-hosting.

We break down how Docker enables this “all-in-one” architecture, allowing each service to run independently while working seamlessly together. Additional tools like Docker Compose orchestrate the system, while ACME integration automates SSL certificate management - ensuring secure communication without manual intervention.

The episode also highlights Mailcow’s active development and strong security focus. From rapid vulnerability patches to modern standards like MTA-STS for enforced encryption, the project demonstrates a commitment to keeping self-hosted email both secure and up to date.

Finally, we explore the broader lesson: modern infrastructure doesn’t have to be overwhelming. With the right containerized approach, even complex systems like email can become manageable, reliable, and accessible.

If you’ve ever considered self-hosting email but were intimidated by the complexity, this deep dive shows how Mailcow transforms a notorious challenge into a practical, maintainable solution.

Let’s have a look at your digital challenges together. What tools are you currently using? Are your processes optimal? How is the state of backups and security updates?

Digital Souvereignty is easily achived with Open Source software (which usually cost way less, too). Our division Safeserver offers hosting, operation and maintenance for countless Free and Open Source tools.

Try it now!