<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Articles on Megargy Technology Works</title><link>https://megargy.com/articles/</link><description>Recent content in Articles on Megargy Technology Works</description><generator>Hugo</generator><language>en-za</language><lastBuildDate>Fri, 11 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://megargy.com/articles/index.xml" rel="self" type="application/rss+xml"/><item><title>Your Domain Registrar Does Not Have to Run Your DNS</title><link>https://megargy.com/articles/your-domain-registrar-does-not-have-to-run-your-dns/</link><pubDate>Fri, 11 Sep 2026 00:00:00 +0000</pubDate><guid>https://megargy.com/articles/your-domain-registrar-does-not-have-to-run-your-dns/</guid><dc:creator>Gary Kennedy</dc:creator><description>&lt;p&gt;If you bought your domain from a &lt;strong&gt;registrar&lt;/strong&gt; such as GoDaddy, Namecheap or xneelo, that company may also have set up your DNS automatically and included it at no extra cost. You do not have to use the registrar for your DNS. &lt;strong&gt;Choosing where your domain&amp;rsquo;s DNS is hosted is an important step.&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Why Should a Blog Post Be About 66 Characters Wide?</title><link>https://megargy.com/articles/why-should-a-blog-post-be-about-66-characters-wide/</link><pubDate>Wed, 09 Sep 2026 00:00:00 +0000</pubDate><guid>https://megargy.com/articles/why-should-a-blog-post-be-about-66-characters-wide/</guid><dc:creator>Gary Kennedy</dc:creator><description>&lt;p&gt;&lt;strong&gt;For blog posts and other long-form text, aim for about 66 characters per line.&lt;/strong&gt; It is a long-established typography guideline, supported by modern usability and accessibility guidance. On the web, a width around &lt;code&gt;66ch&lt;/code&gt; can be a useful starting point, but the actual number of characters that fit on a line depends on the font and its settings.&lt;/p&gt;</description></item><item><title>Your Google Workspace Email Works — But Is It Fully Authenticated?</title><link>https://megargy.com/articles/your-google-workspace-email-works-but-is-it-fully-authenticated/</link><pubDate>Wed, 09 Sep 2026 00:00:00 +0000</pubDate><guid>https://megargy.com/articles/your-google-workspace-email-works-but-is-it-fully-authenticated/</guid><dc:creator>Gary Kennedy</dc:creator><description>&lt;p&gt;Your company email may be working perfectly, but it is still worth checking that DMARC is correctly configured for your domain. A sound configuration helps receiving systems trust your email and helps stop impostors from damaging your company&amp;rsquo;s reputation. If anything is missing, this article explains how to find and fix it.&lt;/p&gt;</description></item><item><title>Limiting the Blast Radius with a Dedicated Sending Subdomain</title><link>https://megargy.com/articles/limiting-the-blast-radius-with-a-dedicated-sending-subdomain/</link><pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate><guid>https://megargy.com/articles/limiting-the-blast-radius-with-a-dedicated-sending-subdomain/</guid><dc:creator>Gary Kennedy</dc:creator><description>&lt;p&gt;Megargy sends newsletters from an address such as &lt;code&gt;update@newsletter.acme.com&lt;/code&gt; rather than &lt;code&gt;newsletter@acme.com&lt;/code&gt;. The dedicated &lt;code&gt;newsletter&lt;/code&gt; subdomain limits the permission you give us to send email on your behalf, while &lt;code&gt;update@newsletter.acme.com&lt;/code&gt; provides a simple, consistent sender identity for the newsletter.&lt;/p&gt;</description></item></channel></rss>