<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Alexandru Ionescu | CV</title>
    <link>/</link>
    <description>Recent content on Alexandru Ionescu | CV</description>
    <generator>Hugo -- 0.147.7</generator>
    <language>en</language>
    <lastBuildDate>Wed, 12 Feb 2025 01:55:53 +0000</lastBuildDate>
    <atom:link href="/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Email Security (SPF, DKIM, and DMARC)</title>
      <link>/blog/email-security/</link>
      <pubDate>Tue, 13 Jul 2021 18:39:59 +0000</pubDate>
      <guid>/blog/email-security/</guid>
      <description>&lt;p&gt;The following is a mirror of the content I authored at &lt;a href=&#34;https://www.praetorian.com/blog/email-security/&#34;&gt;my previous employer&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Our clients occasionally ask us to look into why a particular email that spoofed the client was not blocked by a mail server. Generally these emails are intended to impersonate a user at the company in question, and naturally our clients would want to ensure that the emails are rejected by a receiving mail transfer agent (MTA). In this blog post we will discuss the various technologies that are used to authenticate email, along with their strengths and weaknesses. The intended audience of this blog post is one who wishes to better understand how to protect their email from attackers impersonating its domain.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
