Setting SPF, DKIM, and DMARC for Omnisend

DMARC (RFC 7489) ties SPF and DKIM together by requiring alignment between the envelope sender and the visible From header. According to Google’s February 2024 bulk sender requirements, a DMARC policy of at least p=none is now mandatory for any domain sending 5,000+ messages per day to Gmail users.

DKIM is the authentication protocol that survives email forwarding, says Brad Slavin, CEO of DuoCircle. When SPF fails because a forwarder’s IP isn’t in the original record, DKIM alignment is the only path to DMARC pass. That’s why we monitor DKIM alongside SPF in every DMARC Report dashboard.

					DMARC Report					

				

Setting SPF, DKIM, and DMARC for Omnisend

					<button title="Play" aria-label="Play Episode" aria-pressed="false" class="play-btn">
						

Play Episode

					</button>
					<button title="Pause" aria-label="Pause Episode" aria-pressed="false" class="pause-btn hide">
						

Pause Episode

					</button>
					


				

				

					<audio preload="none" class="clip clip-19909">
						<source src="https://media.mailhop.org/dmarcreport/images/2025/01/Setting-SPF-DKIM-and-DMARC-for-Omnisend.mp3">
					</audio>
					

						

					

					

						

							<button class="player-btn player-btn__volume" title="Mute/Unmute">
								

Mute/Unmute Episode

							</button>
							<button data-skip="-10" class="player-btn player-btn__rwd" title="Rewind 10 seconds">
								

Rewind 10 Seconds

							</button>
							<button data-speed="1" class="player-btn player-btn__speed" title="Playback Speed" aria-label="Playback Speed">1x</button>
							<button data-skip="30" class="player-btn player-btn__fwd" title="Fast Forward 30 seconds">
								

Fast Forward 30 seconds

							</button>
						

						

							<time class="ssp-timer">00:00</time>
							

/

							<!-- We need actual duration here from the server -->
							<time class="ssp-duration" datetime="PT0H2M21S">2:21</time>
						

					

				

			

								<nav class="player-panels-nav">
												<button class="subscribe-btn" id="subscribe-btn-19909" title="Subscribe">Subscribe</button>
																		<button class="share-btn" id="share-btn-19909" title="Share">Share</button>
										</nav>
						

	



		

						

				

					

					

				

				

					

																																																																								

					

						

RSS Feed

							<input value="https://dmarcreport.com/feed/podcast/dmarc-report" class="input-rss input-rss-19909" title="RSS Feed URL" readonly />
						

						<button class="copy-rss copy-rss-19909" title="Copy RSS Feed URL" aria-label="Copy RSS Feed URL"></button>
					

				

			

									

				

					

					

				

				

					

						Share						

					

						<a href="https://www.facebook.com/sharer/sharer.php?u=https://dmarcreport.com/blog/podcast/setting-spf-dkim-and-dmarc-for-omnisend/&t=Setting SPF, DKIM, and DMARC for Omnisend" target="blank" rel="noopener noreferrer" class="share-icon facebook" title="Share on Facebook">
							

						</a>
						<a href="https://twitter.com/intent/tweet?text=https://dmarcreport.com/blog/podcast/setting-spf-dkim-and-dmarc-for-omnisend/&url=Setting SPF, DKIM, and DMARC for Omnisend" target="blank" rel="noopener noreferrer" class="share-icon twitter" title="Share on Twitter">
							

						</a>
						<a href="https://media.mailhop.org/dmarcreport/images/2025/01/Setting-SPF-DKIM-and-DMARC-for-Omnisend.mp3" target="blank" rel="noopener noreferrer" class="share-icon download" title="Download" download>
							

						</a>
					

				

				

					

						Link						

					

						<input value="https://dmarcreport.com/blog/podcast/setting-spf-dkim-and-dmarc-for-omnisend/" class="input-link input-link-19909" title="Episode URL" readonly />
					

					<button class="copy-link copy-link-19909" title="Copy Episode URL" aria-label="Copy Episode URL" readonly=""></button>
				

				

					

						Embed						

					

						<input type="text" value='<blockquote class="wp-embedded-content" data-secret="7RuEqqf0Cg"><a href="https://dmarcreport.com/blog/podcast/setting-spf-dkim-and-dmarc-for-omnisend/">Setting SPF, DKIM, and DMARC for Omnisend</a></blockquote><iframe sandbox="allow-scripts" security="restricted" src="https://dmarcreport.com/blog/podcast/setting-spf-dkim-and-dmarc-for-omnisend/embed/#?secret=7RuEqqf0Cg" width="500" height="350" title=""Setting SPF, DKIM, and DMARC for Omnisend" — DMARC Report" data-secret="7RuEqqf0Cg" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" class="wp-embedded-content"></iframe><script>

/*! This file is auto-generated / !function(d,l){“use strict”;l.querySelector&&d.addEventListener&&“undefined”!=typeof URL&&(d.wp=d.wp||{},d.wp.receiveEmbedMessage||(d.wp.receiveEmbedMessage=function(e){var t=e.data;if((t||t.secret||t.message||t.value)&&!/[^a-zA-Z0-9]/.test(t.secret)){for(var s,r,n,a=l.querySelectorAll(‘iframe[data-secret=”‘+t.secret+’”]’),o=l.querySelectorAll(‘blockquote[data-secret=”‘+t.secret+’”]’),c=new RegExp(“^https?:$”,“i”),i=0;i<o.length;i++)o[i].style.display=“none”;for(i=0;i<a.length;i++)s=a[i],e.source===s.contentWindow&&(s.removeAttribute(“style”),“height”===t.message?(1e3<(r=parseInt(t.value,10))?r=1e3:~~r<200&&(r=200),s.height=r):“link”===t.message&&(r=new URL(s.getAttribute(“src”)),n=new URL(t.value),c.test(n.protocol))&&n.host===r.host&&l.activeElement===s&&(d.top.location.href=t.value))}},d.addEventListener(“message”,d.wp.receiveEmbedMessage,!1),l.addEventListener(“DOMContentLoaded”,function(){for(var e,t,s=l.querySelectorAll(“iframe.wp-embedded-content”),r=0;r<s.length;r++)(t=(e=s[r]).getAttribute(“data-secret”))||(t=Math.random().toString(36).substring(2,12),e.src+=”#?secret=“+t,e.setAttribute(“data-secret”,t)),e.contentWindow.postMessage({message:“ready”,secret:t},"")},!1)))}(window,document); //# sourceURL=https://dmarcreport.com/wp-includes/js/wp-embed.min.js ’ title=“Embed Code” class=“input-embed input-embed-19909” readonly/>

					<button class="copy-embed copy-embed-19909" title="Copy Embed Code" aria-label="Copy Embed Code"></button>
				

			

				

Omnisend users who don’t have SPF, DKIM, and DMARC protocols in place are in for a problem. Their emails are highly likely to be blocked, hindering communication and operations. With these three email authentication protocols in place, users comply with Omnisend’s requirements and keep their brand names out of phishing and spoofing reports.

No matter how frequently you send emails, you must protect your domain and brand image with SPF, DKIM, and DMARC.

How Do You Configure up SPF for Omnisend?

SPF allows you to list down all the servers that are officially authorized to be used for sending emails on your behalf. If any other server than the ones you mentioned in your **SPF record is used for sending emails from your domain, then those emails will fail the SPF checks. They will either land in the spam folders of the recipients or get rejected from entering their mailboxes. This ultimately **prevents the targeted victims from engaging with such malicious emails sent under your name.

Here is how you can start with SPF for Omnisend-

• Use an online SPF record generator tool to create a TXT record. While you can generate it manually, we don’t recommend this approach as it’s time-consuming and more prone to errors.

• Authorize Omnisend as a trusted sender by entering ‘mailgun.org’ in the ‘authorize third-party domain’ field of the tool, as Omnisend relies on Mailgun for email delivery.

• Publish the generated SPF TXT record in your domain’s DNS. To do this, log in to your DNS management console or request that your hosting provider add it for you.

• Finally, use an SPF lookup tool to verify the accuracy of your SPF record and confirm that Omnisend is listed as an authorized sender.

If you already have an SPF record, here’s how to update it for Omnisend:

• Use an SPF checker tool to find your current record, such as: v=spf1 include:_spf.example.net -all.

• Add Mailgun for Omnisend, updating it to: v=spf1 include:mailgun.org include:_spf.example.net -all.

• Edit the record in your DNS management console and save it.

• Wait up to 24 hours for the changes to take effect.

How Do You Configure up DKIM for Omnisend?

• Use your login credentials to log in to your Omnisend account.

• Go to Store Settings

Sender Domains.

• On the Sender Domain page, go to the ‘Your sender domains’ tab and click on ‘+ Add sender domain’ to log in to your domain.

• Next, enter your domain name.

• The DKIM record for your domain is on the ‘Domain Authentication’ page. It is a TXT record that consists of the public key and name.

• Add this record to your domain’s DNS settings.

• The authentication mechanism will be activated in a maximum of 24 hours.

How Do You Configure up DMARC for Omnisend?

• Generate a DMARC record using an online tool, starting with the ‘none’ policy before moving to ‘quarantine’ and ‘reject.’

• Log in to your DNS management console and add the DMARC record.

• Check its accuracy with an online DMARC lookup tool.