<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Deliverability on Sender Audit Blog</title><link>https://senderaudit.com/blog/en/tags/deliverability/</link><description>Recent content in Deliverability on Sender Audit Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 04 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://senderaudit.com/blog/en/tags/deliverability/index.xml" rel="self" type="application/rss+xml"/><item><title>Email trackers explained: pixels, link wrapping, and privacy</title><link>https://senderaudit.com/blog/en/email-trackers-pixels-privacy/</link><pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate><guid>https://senderaudit.com/blog/en/email-trackers-pixels-privacy/</guid><description>&lt;p&gt;Every marketing email you receive likely contains one or more invisible trackers. They measure whether you opened the message, when, how many times, from which device, and which links you clicked. Here&amp;rsquo;s how it works - and how to do better.&lt;/p&gt;
&lt;h2 id="how-open-tracking-works"&gt;How open tracking works&lt;/h2&gt;
&lt;h3 id="the-spy-pixel-an-invisible-image"&gt;The spy pixel: an invisible image&lt;/h3&gt;
&lt;p&gt;The mechanism is straightforward: the sender inserts a 1×1 pixel transparent image hosted on their server. When your mail client renders the message, it downloads the image. The server records:&lt;/p&gt;</description></item><item><title>Shadow IT and Email: The Tools Sending on Your Behalf Without You Knowing</title><link>https://senderaudit.com/blog/en/shadow-it-email/</link><pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate><guid>https://senderaudit.com/blog/en/shadow-it-email/</guid><description>&lt;p&gt;You&amp;rsquo;ve configured &lt;a href="https://senderaudit.com/blog/en/configure-spf/"&gt;SPF&lt;/a&gt;, &lt;a href="https://senderaudit.com/blog/en/configure-dkim/"&gt;DKIM&lt;/a&gt;, and &lt;a href="https://senderaudit.com/blog/en/configure-dmarc/"&gt;DMARC&lt;/a&gt;. Your email infrastructure is under control. Then one day, while analyzing your &lt;a href="https://senderaudit.com/blog/en/understanding-dmarc-reports/"&gt;DMARC reports&lt;/a&gt;, you discover dozens of unknown IPs sending emails on behalf of your domain. Not phishing - internal tools that nobody in IT ever approved.&lt;/p&gt;
&lt;p&gt;Welcome to the world of &lt;strong&gt;email shadow IT&lt;/strong&gt;.&lt;/p&gt;
&lt;h2 id="what-is-email-shadow-it"&gt;What Is Email Shadow IT&lt;/h2&gt;
&lt;p&gt;Shadow IT refers to the use of technology services without explicit approval from the IT team. Applied to email, it&amp;rsquo;s extremely common: business teams configure SaaS tools to send emails from your domain without going through IT.&lt;/p&gt;</description></item><item><title>DMARC: Safely Migrating from p=none to p=reject</title><link>https://senderaudit.com/blog/en/dmarc-none-to-reject/</link><pubDate>Sat, 11 Apr 2026 00:00:00 +0000</pubDate><guid>https://senderaudit.com/blog/en/dmarc-none-to-reject/</guid><description>&lt;p&gt;You&amp;rsquo;ve published your &lt;a href="https://senderaudit.com/blog/en/configure-dmarc/"&gt;DMARC&lt;/a&gt; record with &lt;code&gt;p=none&lt;/code&gt;. That&amp;rsquo;s a good start, but &lt;code&gt;p=none&lt;/code&gt; blocks nothing: fraudulent emails still get through. The end goal is &lt;code&gt;p=reject&lt;/code&gt;, and this guide walks you through the migration without breaking your legitimate mail flows.&lt;/p&gt;
&lt;h2 id="why-pnone-isnt-enough"&gt;Why p=none Isn&amp;rsquo;t Enough&lt;/h2&gt;
&lt;p&gt;With &lt;code&gt;p=none&lt;/code&gt;, you&amp;rsquo;re asking mailbox providers to &lt;strong&gt;do nothing&lt;/strong&gt; when an email fails DMARC. You receive RUA reports, but:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Emails spoofing your domain still reach inboxes&lt;/li&gt;
&lt;li&gt;Your domain can be used for phishing&lt;/li&gt;
&lt;li&gt;Google and Yahoo now require a published DMARC record, but the real benefits start at &lt;code&gt;p=quarantine&lt;/code&gt; or &lt;code&gt;p=reject&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="recommended-timeline"&gt;Recommended Timeline&lt;/h2&gt;
&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;Week&lt;/th&gt;
 &lt;th&gt;Policy&lt;/th&gt;
 &lt;th&gt;Goal&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;W1-W2&lt;/td&gt;
 &lt;td&gt;&lt;code&gt;p=none; rua=mailto:...&lt;/code&gt;&lt;/td&gt;
 &lt;td&gt;Collect reports, inventory sources&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;W3-W4&lt;/td&gt;
 &lt;td&gt;Report analysis&lt;/td&gt;
 &lt;td&gt;Identify each source IP, fix SPF/DKIM&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;W5-W6&lt;/td&gt;
 &lt;td&gt;&lt;code&gt;p=quarantine; pct=10&lt;/code&gt;&lt;/td&gt;
 &lt;td&gt;Test on 10% of traffic&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;W7-W8&lt;/td&gt;
 &lt;td&gt;&lt;code&gt;p=quarantine; pct=50&lt;/code&gt;&lt;/td&gt;
 &lt;td&gt;Gradually increase&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;W9-W10&lt;/td&gt;
 &lt;td&gt;&lt;code&gt;p=quarantine; pct=100&lt;/code&gt;&lt;/td&gt;
 &lt;td&gt;Observe for 2 weeks&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;W11-W12&lt;/td&gt;
 &lt;td&gt;&lt;code&gt;p=reject; pct=10&lt;/code&gt;&lt;/td&gt;
 &lt;td&gt;Begin gradual rejection&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;W13-W14&lt;/td&gt;
 &lt;td&gt;&lt;code&gt;p=reject; pct=50&lt;/code&gt;&lt;/td&gt;
 &lt;td&gt;Scale up&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;W15+&lt;/td&gt;
 &lt;td&gt;&lt;code&gt;p=reject; pct=100; sp=reject&lt;/code&gt;&lt;/td&gt;
 &lt;td&gt;Full protection&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;This timeline is indicative. The key is to &lt;strong&gt;never skip a step&lt;/strong&gt; without verifying that reports are clean.&lt;/p&gt;</description></item><item><title>Why Do You See Two DKIM Signatures on a Single Email?</title><link>https://senderaudit.com/blog/en/double-dkim-signature/</link><pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate><guid>https://senderaudit.com/blog/en/double-dkim-signature/</guid><description>&lt;p&gt;You inspect the headers of an email sent through your ESP (Brevo, Mailchimp, SendGrid…) and notice &lt;strong&gt;two distinct DKIM signatures&lt;/strong&gt;: one with your domain, one with the ESP&amp;rsquo;s domain. Is this normal? Absolutely, and it&amp;rsquo;s actually desirable.&lt;/p&gt;
&lt;h2 id="what-it-looks-like-in-the-headers"&gt;What It Looks Like in the Headers&lt;/h2&gt;
&lt;p&gt;Here&amp;rsquo;s a typical &lt;code&gt;Authentication-Results&lt;/code&gt; example:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;Authentication-Results: mx.google.com;
 dkim=pass header.i=@yourdomain.com header.s=mail header.b=xjAWgYt1;
 dkim=pass header.i=@esp-domain.com header.s=mail header.b=zNRqfud1;
 spf=pass ...
 dmarc=pass (p=REJECT) header.from=yourdomain.com
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;And two &lt;code&gt;DKIM-Signature:&lt;/code&gt; blocks in the message: one with &lt;code&gt;d=yourdomain.com&lt;/code&gt;, the other with &lt;code&gt;d=esp-domain.com&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>Email Blacklists: Understand, Check and Get Delisted</title><link>https://senderaudit.com/blog/en/understanding-blacklists/</link><pubDate>Mon, 09 Feb 2026 00:00:00 +0000</pubDate><guid>https://senderaudit.com/blog/en/understanding-blacklists/</guid><description>&lt;p&gt;Your delivery rate drops suddenly. Your emails go to spam, or worse, they&amp;rsquo;re rejected with &lt;code&gt;550 5.7.1 Service unavailable; client host blocked&lt;/code&gt;. There&amp;rsquo;s a good chance your IP or domain is on a &lt;strong&gt;blacklist&lt;/strong&gt;.&lt;/p&gt;
&lt;h2 id="what-is-an-email-blacklist"&gt;What Is an Email Blacklist?&lt;/h2&gt;
&lt;p&gt;A blacklist (or RBL, Realtime Blackhole List, or DNSBL, DNS-based Blackhole List) is a database that catalogues IP addresses and domains identified as spam sources or abusive senders.&lt;/p&gt;
&lt;p&gt;Receiving servers (Gmail, Outlook, ISPs, corporate servers…) query these lists in real time to decide whether to accept, filter, or reject an email.&lt;/p&gt;</description></item><item><title>Email Deliverability: The Ultimate Guide to Reaching the Inbox</title><link>https://senderaudit.com/blog/en/email-deliverability/</link><pubDate>Tue, 03 Feb 2026 00:00:00 +0000</pubDate><guid>https://senderaudit.com/blog/en/email-deliverability/</guid><description>&lt;p&gt;You send emails, but do they actually reach the inbox? &lt;strong&gt;Deliverability&lt;/strong&gt; is the rate at which your emails land in recipients&amp;rsquo; inboxes, as opposed to the spam folder or outright rejection. It&amp;rsquo;s a critical issue for any business that communicates via email.&lt;/p&gt;
&lt;h2 id="why-your-emails-arent-arriving"&gt;Why Your Emails Aren&amp;rsquo;t Arriving&lt;/h2&gt;
&lt;p&gt;ISPs (Gmail, Outlook, Yahoo, etc.) use hundreds of signals to decide the fate of each email. Here are the main ones:&lt;/p&gt;
&lt;h3 id="1-dns-authentication"&gt;1. DNS Authentication&lt;/h3&gt;
&lt;p&gt;This is the absolute prerequisite. Without it, you&amp;rsquo;re a stranger to ISPs.&lt;/p&gt;</description></item><item><title>SPF: The Complete Guide to Authorizing Your Sending Servers</title><link>https://senderaudit.com/blog/en/configure-spf/</link><pubDate>Sat, 17 Jan 2026 00:00:00 +0000</pubDate><guid>https://senderaudit.com/blog/en/configure-spf/</guid><description>&lt;p&gt;SPF (Sender Policy Framework) is the first line of defense in email authentication. It lets you declare in your DNS which servers are allowed to send email for your domain. Simple on the surface, it hides subtleties that trip up even experienced admins.&lt;/p&gt;
&lt;h2 id="what-does-spf-actually-do"&gt;What Does SPF Actually Do?&lt;/h2&gt;
&lt;p&gt;When a receiving server gets an email from &lt;code&gt;contact@yourdomain.com&lt;/code&gt;, it asks one question: &lt;em&gt;&amp;ldquo;Is this server allowed to send for this domain?&amp;rdquo;&lt;/em&gt;&lt;/p&gt;</description></item></channel></rss>