<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Home on Justin Morrison</title><link>https://justinmorrison.com/</link><description>Recent content in Home on Justin Morrison</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 15 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://justinmorrison.com/index.xml" rel="self" type="application/rss+xml"/><item><title>Announcing Cyniva Email Hosting</title><link>https://justinmorrison.com/blog/announcing-cyniva-email-hosting/</link><pubDate>Mon, 15 Jun 2026 00:00:00 +0000</pubDate><guid>https://justinmorrison.com/blog/announcing-cyniva-email-hosting/</guid><description>&lt;p&gt;For the last couple of years I ran my own mail server. Postfix and Dovecot on a little VPS, full-service mail servers like &lt;a href="https://mailcow.email/"&gt;Mailcow&lt;/a&gt; and &lt;a href="https://stalw.art"&gt;Stalwart&lt;/a&gt;, etc. It started as a learning project and it genuinely was one, but what I didn&amp;rsquo;t expect was how much of it turned into ongoing maintenance. Running email yourself quickly becomes a full time job.&lt;/p&gt;
&lt;p&gt;Here&amp;rsquo;s the short version of what that actually involves.&lt;/p&gt;
&lt;h2 id="the-stuff-that-actually-breaks"&gt;The stuff that actually breaks&lt;/h2&gt;
&lt;p&gt;Getting mail to &lt;em&gt;send&lt;/em&gt; is easy. Getting it to land in someone&amp;rsquo;s inbox instead of their spam folder is the hard part, and it never really ends. You sort out your SPF and DKIM records, add a DMARC policy, figure you&amp;rsquo;re in good shape. Then Gmail decides your IP looks a little new and quietly routes you to spam for a month while it makes up its mind about you. You can&amp;rsquo;t even see it happening. The mail just vanishes into a folder nobody checks.&lt;/p&gt;</description></item></channel></rss>