solariz.de

Email server administration covers everything needed to run mail for one or more domains: creating and managing domains, mailboxes, and aliases; setting filtering rules and auto-responders; handling spam quarantine and security; and monitoring the system through statistics and migration tools. Modoboa is an open source email server that bundles these functions behind a single web interface, and its installer handles about 95% of the setup work in under 10 minutes — after which you mainly configure your DNS. This is for anyone who wants to self-host mail without assembling and configuring each component individually.

What the administration interface covers

Modoboa brings together several open source tools in one interface, so the admin panel is the single place where you manage the mail server. Based on the site's feature list, it lets you handle:

• Domains, mailboxes, and aliases — with unlimited creation of each
• Webmail — reading mail through a browser
• Calendars and address books — management for your users
• Filtering rules — to organize incoming email
• Auto-responders — for out-of-office or similar replies
• Administrator tools — statistics and a migration tool

The project reports more than 800,000 mailboxes in use, which is a rough signal of the scale the interface is expected to handle.

Managing domains, mailboxes, and aliases

The core administrative loop is the same for each object type: you create it in the web UI, and the underlying components (Postfix for delivery, Dovecot for storage/access) are configured for you. In practice:

1. Add a domain you want to host.
2. Create mailboxes under that domain.
3. Create aliases to forward or group addresses.
4. Set filtering rules and auto-responders per mailbox as needed.

Because the installer wires up the components, you are not editing Postfix or Dovecot configuration files by hand for these routine tasks — the interface is the control point.

Spam quarantine, rspamd/amavis, and security

Modoboa's keyword set includes quarantine, rspamd, and amavis, which are the anti-spam and filtering components in the stack. The administration interface is where you review and release quarantined messages and adjust filtering behavior, rather than working directly in each tool.

On the security side, the site states that Modoboa encrypts all communications between your email server and the outside by default, using the TLS protocol. That default matters for administration because you don't have to enable transport encryption as a separate hardening step — it is part of the generated server.

Administrator tools: statistics and migration

Two admin utilities are called out specifically:

• Statistics — visibility into what the server is doing.
• Migration tool — for moving existing mail data into the new server.

These sit alongside the day-to-day mailbox management, so a migration and ongoing monitoring happen in the same interface you use for routine administration.

What the installer handles vs. what you still do

The division of labor is the key thing to understand before starting:

So the realistic sequence is: run the installer, then configure your DNS — that is the step the site explicitly says remains yours. After that, administration is largely web-UI work.

How this compares to the alternatives

The site frames Modoboa against three common options: paid provider mailboxes (limited customization, domains, and mailbox counts), free email providers (limited, with data used for commercial purposes), and a fully hand-built server (requires significant technical knowledge). Modoboa positions itself as the fourth path — self-hosted and private, but without assembling every component yourself. If your priority is controlling where data lives and who can administer it, that is the trade: you take on DNS and ongoing administration in exchange for independence from a provider.

Where to start

If you want to try it, the entry points named on the site are Try now and Download. The team also states it helps with installation and maintenance, which is relevant if you expect to need support running the server long-term.

A techblog is a blog whose main subject is technology: code, tools, hardware, networks, and the practical problems the author runs into while working on them. It is usually written by one person or a small team rather than an editorial staff, so the content tends to be first-hand and narrow rather than comprehensive. A techblog is worth following when its topics overlap with what you actually run or want to learn, and when the posts are specific enough to reproduce. The example used throughout this article is solariz.de, a personal tech blog that describes itself as covering "code snippets, small tools and 'how tos'" alongside gaming and anime.

What separates a techblog from a general blog

The distinguishing feature is not the platform but the subject matter and the level of detail. A general blog might mention that a server was replaced; a techblog explains what failed, what replaced it, and what changed as a result.

Typical markers:

• First-person operational writing. Posts describe what the author did to their own systems, including the parts that went wrong.
• Reproducible artifacts. Code snippets, configuration fragments, command-line recordings, or links to tools.
• Narrow but deep scope. A techblog often covers a handful of recurring themes instead of everything under "technology."
• Ongoing series. Problems get revisited as they evolve, which is how you can tell the author actually maintains the systems they write about.

Common content types

Across techblogs, a few formats recur. On solariz.de the stated mix is code snippets, small tools, and how-tos, with the emphasis on whatever the author is currently dealing with.

A concrete example from solariz.de: a post titled "Slashing Watts on My Proxmox Homeserver" is explicitly a follow-up to two earlier posts about the same machine — one about it "dying in slow motion" and one about replacing it. That three-post arc is a good illustration of how a techblog builds knowledge over time rather than publishing isolated articles.

Typical topic range

Techblogs cluster around whatever the author administers. On solariz.de the internal quick-links point to Networks, pfSense, unifi, Gaming Stuff, and Anime, and the site keywords list Computer Networking, Routing, Networks, Administration, wifi, and LAN. Recent posts cover a Proxmox homeserver, a local EPUB server for an e-ink reader, and removing web fonts to cut page weight.

That gives a reasonable picture of the usual territory:

• Networking — routing, LAN and WiFi setup, firewall and router platforms such as pfSense and UniFi.
• Home servers and virtualization — Proxmox, power consumption, hardware replacement cycles.
• Self-hosting — running your own services instead of relying on a hosted product.
• Small utilities and scripts — tools built to solve one specific annoyance.
• Adjacent hobbies — gaming, anime, or other interests the author writes about between technical posts.

The adjacent-hobby content is normal for a personal techblog and is one way to judge fit: if you only want the networking posts, you will be skipping a portion of the feed.

How to browse a techblog efficiently

Most techblogs are archives first and feeds second. On solariz.de the navigation options are:

1. Year archives. Posts are grouped by year, with the archive running back to 2000 and a heatmap view showing posting density over time. Use this to gauge how active the blog has been and whether it is still being updated.
2. Quick-links to recurring topics. A short list of the subjects the author writes about most, which is faster than scrolling the archive.
3. A search page. The site explicitly offers search for when the topic links do not cover what you need.
4. An About page. Useful for understanding the author's background, which tells you how much weight to give their conclusions.

A practical approach: start with the topic quick-links, check the most recent year to confirm the blog is still alive, then search for your specific problem. If a topic has multiple posts, read them oldest to newest — follow-up posts often correct or supersede earlier advice.

How to judge whether a techblog fits you

Three signals matter more than production quality.

Topic overlap. Does the blog cover the systems you actually run? A blog about pfSense and UniFi is useful if you have that hardware and much less useful if you do not.

Update frequency and recency. The year archive and heatmap make this visible at a glance. A blog with a dense recent year is more likely to reflect current software versions than one whose last post is several years old.

Depth and honesty. Posts that describe a problem over multiple entries, including the failed attempts, tend to be more trustworthy than posts that present a clean solution with no friction. The "dying in slow motion" series on solariz.de is an example of the former — the author documents a slow hardware decline and the eventual replacement rather than presenting a tidy upgrade guide.

If a blog passes all three, the fastest way to use it is to search for your exact problem first, then read the surrounding posts for context. If it fails on topic overlap, no amount of good writing will make it relevant to your setup.

A network, in the context of interconnection, is an independently operated system of connected devices and infrastructure that exchanges traffic with other networks. The operator controls its own routing decisions and is identified on the internet by an Autonomous System Number (ASN). Networks connect by exchanging routes and traffic — either directly through peering, through a paid transit provider, or by meeting many other networks at an Internet Exchange Point (IXP). The sections below explain the network types involved, how traffic is addressed between them, and what operators weigh when choosing where and with whom to interconnect.

Networks by role

Interconnection discussions usually distinguish networks by what they carry and whom they serve:

The same organization can operate more than one type. A large carrier may run access, transit, and content infrastructure at once, which changes its peering posture in each role.

How networks are identified and how traffic is routed

Every network that participates in global routing is identified by an Autonomous System Number (ASN). The network announces the IP address ranges it is responsible for, and other networks learn those routes through the Border Gateway Protocol (BGP).

The practical effect:

• A network announces its prefixes to its neighbors.
• Neighbors propagate those routes further, so every network builds a routing table of how to reach every prefix.
• When traffic is sent, each network forwards it to the next hop that its routing table says is best for that destination.
• The path traffic takes is therefore the result of many independent routing decisions, not a single central map.

This is why interconnection choices matter: they change which routes a network can use and how directly traffic reaches its destination.

How networks connect to each other

There are three common ways networks interconnect, and most operators use a mix:

Peering

Two networks agree to exchange traffic directly between themselves, typically without paying each other for the exchange. Peering can be private (a direct physical or virtual link between the two parties) or public (both parties connect to the same exchange fabric). Networks decide where to peer based on factors such as traffic volume, geographic proximity, cost, latency, and how much of their traffic goes to that partner.

Transit

A network buys connectivity from another network to reach the rest of the internet. Transit is the fallback that makes a network reachable even where it has no direct peering relationship. It is usually the paid option, in contrast to settlement-free peering.

Internet Exchange Points (IXPs)

An IXP is a shared physical and logical location where many networks connect to a common switching fabric and peer with each other. Joining one IXP can give a network many peering options through a single connection instead of building a separate link to every partner. DE-CIX operates neutral Internet Exchanges in Europe, the Middle East, Africa, Asia, and the Americas, and describes its services as premium interconnection services.

What networks consider when choosing interconnection partners or locations

The decision is usually a trade-off among measurable and strategic factors:

• Traffic volume and ratio — how much traffic flows each way between the two networks.
• Latency and path quality — whether a direct connection shortens the route to important destinations.
• Cost — port, cross-connect, transport, and any paid arrangement, weighed against the cost of transit.
• Reach — how many relevant networks, content sources, or end users are available at a given location.
• Redundancy — whether a new connection adds diversity or just duplicates an existing path.
• Operational effort — the work of configuring, monitoring, and maintaining each relationship.
• Neutrality and governance — whether the exchange or partner operates neutrally and under terms the network can accept.

Key terms to recognize

• Peering — direct traffic exchange between two networks, often settlement-free.
• Transit — paid connectivity that provides reach to the broader internet.
• IXP — a shared interconnection location where many networks meet.
• AS / ASN — an independently routed network and its identifying number.
• BGP — the routing protocol that exchanges reachability information between networks.
• Prefix — an IP address range a network announces and routes.

Understanding these terms is enough to follow most interconnection discussions and to evaluate why a given network peers where it does.

Routing is the process a router uses to forward a packet toward its destination by comparing the packet's destination IP address against a routing table and sending it out the best matching path. It applies whenever traffic crosses between networks — your LAN and the internet, two VLANs, or two sites connected over a VPN. If everything stays inside one subnet, no routing is involved; that's switching. The rest of this article explains how the decision is actually made, what fills the routing table, and how to reason about it when packets don't arrive.

The core decision: longest prefix match

A router does not "know the internet." It only knows a list of routes, each pairing a destination network with a next hop (or an interface). For every packet, it runs the same lookup:

1. Read the destination IP address from the packet header.
2. Compare it against every entry in the routing table.
3. Pick the most specific match — the entry with the longest prefix (highest subnet mask length). This is the longest prefix match rule.
4. Forward the packet to that entry's next hop, or drop it if nothing matches.

Example: a packet to 192.168.20.55 arrives at a router with these entries:

All three match, but /24 is the longest, so the packet goes to the VLAN 20 interface directly. The default route only wins when nothing more specific matches — which is exactly why it's called the route of last resort.

What goes into a routing table

Routes get there in three ways, and the distinction matters when you troubleshoot:

• Directly connected — the router automatically adds a route for each subnet on its own interfaces. These are the most trusted.
• Static routes — you type them in manually. Predictable, no protocol overhead, but they don't adapt if a link fails.
• Dynamic routes — learned from other routers via a routing protocol. Common ones:
  • OSPF — interior gateway protocol, typically inside one organization. Routers exchange link states and converge on shortest paths.
  • BGP — the protocol that exchanges routes between autonomous systems, i.e. how the global internet's routing table is assembled.
  • RIP — older, hop-count based, mostly of historical interest.

When multiple sources offer a route to the same prefix, the router prefers by administrative distance (trustworthiness) first, then by metric (cost). A static route usually beats a dynamically learned one to the same destination unless you deliberately change the distance.

Routing vs. switching, NAT, and firewalls

These get conflated constantly, so keep them separate:

A home "router" is usually all four in one box. NAT is not routing — it's address translation applied after the routing decision. A firewall rule can drop a packet that routing already decided to forward. So "the route exists but traffic still fails" is a normal outcome: check NAT and firewall policy next.

How this looks in a home or small network

On platforms like pfSense or UniFi, the routing table is mostly built for you:

• Each interface (LAN, WAN, VLANs) contributes a connected route.
• The WAN interface gets a default route from the ISP via DHCP or PPPoE.
• You add static routes only for things the router can't infer — for example, reaching a remote subnet behind a second router or across a VPN tunnel.

A typical static route entry says: "to reach 10.10.0.0/24, go via 192.168.1.2." If the next-hop address isn't reachable on a directly connected subnet, the route won't work — the router has nowhere to hand the packet.

When routing doesn't work: a checklist

Work outward from the host, because most "routing problems" are actually host configuration problems:

1. Is the host's default gateway correct? A wrong gateway means the host can reach its own subnet but nothing beyond it.
2. Is the destination in the same subnet as the host? If the host thinks it's local, it will ARP instead of routing, and fail silently.
3. Does the router have a route to the destination? Check the routing table for a matching prefix, not just a default route.
4. Does the return path exist? Routing is per-direction. A packet can arrive fine and the reply can have no route back — a classic asymmetric-routing symptom.
5. Is NAT or a firewall rule blocking it? Confirm the route is being used before blaming the route.
6. DNS is separate. If names fail but IP addresses work, you have a name-resolution problem, not a routing one.

A quick way to see the decision on most systems is traceroute (or tracert on Windows): each hop is a router that matched the destination and forwarded it onward. Where the trace stops is usually where the route or the policy ends.

The takeaway

Routing is a table lookup with one rule that matters most: longest prefix match, with the default route as fallback. Everything else — static vs. dynamic, OSPF vs. BGP, NAT, firewall rules — is about how that table gets populated and what happens to the packet afterward. When traffic fails, verify the gateway, the matching prefix, the return path, and the policy in that order.

A blog is a website whose primary content is a stream of dated entries ("posts") shown newest-first, usually with an author byline and a way to browse older material by category, tag, or archive. It differs from a static site mainly in how content is organized and updated: a static site presents fixed pages you edit in place, while a blog is built around an accumulating timeline of posts. You'd choose a blog when you expect to publish repeatedly over time; you'd choose static pages when the content changes rarely and each page stands alone.

Blog vs. static site vs. wiki

The lines blur in practice. A project site can host a blog as one section, and a blog can contain static pages (About, Contact) alongside the post stream. The distinguishing feature is the post timeline, not the software.

The typical structure of a blog

• Posts — the individual dated entries. Each usually has its own URL, title, date, author, and body.
• Reverse-chronological index — the home page or a "blog" page listing posts newest-first.
• Categories — broad, usually pre-defined groupings (e.g., "Releases," "Tutorials").
• Tags — finer, often free-form labels that can cut across categories.
• Archives — views by month, year, or author for reaching older posts.
• Feeds — an RSS or Atom file that lets readers and other tools subscribe to new posts.
• Comments — optional; some blogs enable them, many disable them to avoid spam and moderation work.

Categories and tags both help readers and search engines, but they only work if you apply them consistently. A common failure is creating a new tag for every post, which produces dozens of one-item tag pages that help no one.

Hosted or self-hosted?

The main decision is who runs the software and the server.

• Hosted platforms (e.g., WordPress.com, Blogger, Medium-style services) handle hosting, updates, and often the domain for you. You trade control and sometimes portability for less maintenance.
• Self-hosted means you install and run the software yourself on a server or static host. You get full control over themes, plugins, and data, but you own backups, updates, and security.

A middle path is a static site generator such as Jekyll, which builds plain HTML files from templates and Markdown posts. These are fast and cheap to host, but they have no built-in comment system or admin interface, so publishing means running a build step. The OpenBVE project homepage, for example, is a project site that publishes dated release notes in a blog-like stream — the August 10, 2026 entry lists OpenBVE v1.14.0.3 changes such as a fix for builds failing to launch on non-Windows platforms and new quality options for viewers. That is the blog pattern applied to software releases: dated, newest-first, each entry a discrete update.

Basic steps to start a blog

1. Decide hosted vs. self-hosted based on how much control and maintenance you want.
2. Choose a platform that matches that choice — a hosted service, a self-hosted CMS, or a static generator.
3. Pick a domain — either a subdomain on the platform or your own registered name. Your own domain makes it easier to move later.
4. Select a theme that is responsive, so it works on phones as well as desktops.
5. Configure the basics — site title, author, time zone, and permalink structure.
6. Write and publish your first post, then verify it appears on the index and at its own URL.
7. Set up a feed so readers can subscribe, and check that it validates.

Ongoing tasks

Publishing is the visible part; the rest is upkeep.

• Comments — if enabled, expect spam. Most platforms offer moderation queues and spam filters; many bloggers simply turn comments off.
• Feeds — keep the feed working and decide whether to publish full text or excerpts.
• SEO basics — descriptive titles, clean URLs, sensible headings, and internal links between related posts. Avoid duplicating the same content across multiple URLs.
• Backups — especially self-hosted. A blog is a database plus files; back up both.
• Updates — self-hosted software needs security patches. Skipping them is the most common way small blogs get compromised.

How to tell it's working

After the first few posts, check that: the index lists posts newest-first, each post has a stable URL, categories and tags resolve to real pages, the feed validates, and the layout holds up on a narrow screen. If any of those fail, fix them before publishing more — structural problems get harder to correct as the archive grows.