<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">

  <title>Vinland Technology Blog</title>
  <subtitle>Free Software, license compliance, and sovereign email hosting in the EU.</subtitle>
  <id>https://vinland.technology/blog/</id>
  <link rel="alternate" type="text/html" href="https://vinland.technology/blog/"/>
  <link rel="self" type="application/atom+xml" href="https://vinland.technology/blog/atom.xml"/>
  <updated>2026-08-24T14:39:59+02:00</updated>
  <rights>Copyright (c) 2026 Vinland Technology AB. Licensed under the GNU Free Documentation License, Version 1.2 or later.</rights>
  <author>
    <name>Jeremiah C. Foster</name>
    <uri>https://jeremiahfoster.com/</uri>
  </author>

  <!--
    ADDING A POST: copy one <entry> block, put it at the top, and update
    <id>, <title>, <link>, <published>, <updated> and <summary>. Then bump
    the feed-level <updated> above to match the newest entry. Dates are
    RFC 3339 (YYYY-MM-DDThh:mm:ss+02:00).
  -->

  <entry>
    <id>https://vinland.technology/blog/suomalainen-server-changes.html</id>
    <title>Changes to the suomalainen.email Mail Server</title>
    <link rel="alternate" type="text/html" href="https://vinland.technology/blog/suomalainen-server-changes.html"/>
    <published>2026-08-24T14:39:59+02:00</published>
    <updated>2026-08-24T14:39:59+02:00</updated>
    <category term="Infrastructure"/>
    <summary type="text">We would like to update to a new version of Stalwart and update our kernel as well, plus new webmail. There may be some reboots as a consequence but no significant planned downtime.</summary>
  </entry>

  <entry>
    <id>https://vinland.technology/blog/dnssec-setup.html</id>
    <title>Setting up DNSSEC</title>
    <link rel="alternate" type="text/html" href="https://vinland.technology/blog/dnssec-setup.html"/>
    <published>2026-07-07T01:24:25+02:00</published>
    <updated>2026-08-24T14:23:21+02:00</updated>
    <category term="Infrastructure"/>
    <summary type="text">DNS had no way of proving that an answer was the one the domain owner actually published. DNSSEC closes that gap by cryptographically signing DNS records — here's how we signed the zones behind our sovereign email hosting.</summary>
  </entry>

  <entry>
    <id>https://vinland.technology/blog/sovereign-email-beta.html</id>
    <title>Sovereign Email Hosting — Our Beta</title>
    <link rel="alternate" type="text/html" href="https://vinland.technology/blog/sovereign-email-beta.html"/>
    <published>2026-06-10T16:00:32+02:00</published>
    <updated>2026-07-07T01:24:25+02:00</updated>
    <category term="Announcements"/>
    <summary type="text">Our first sovereign cloud service is live as a beta: email hosting held in the EU under the GDPR, built entirely on Free Software, with nodes in Stockholm and Helsinki — and Oslo coming soon.</summary>
  </entry>

  <entry>
    <id>https://vinland.technology/blog/eu-cloud-sovereignty-framework.html</id>
    <title>The EU's Cloud Sovereignty Framework</title>
    <link rel="alternate" type="text/html" href="https://vinland.technology/blog/eu-cloud-sovereignty-framework.html"/>
    <published>2026-05-01T14:36:09+02:00</published>
    <updated>2026-05-04T15:15:48+02:00</updated>
    <category term="Policy"/>
    <summary type="text">The European Commission's DG DIGIT has published v1.2.1 of the Cloud Sovereignty Framework — eight Sovereignty Objectives and a five-level SEAL assurance scale that together turn "sovereign cloud" from a slogan into a hard procurement gate.</summary>
  </entry>

</feed>
