1import{f as d,a as i,t as y}from"./DCzqUQ3i.js";import"./tK2zuXnD.js";import{f as p,s as e,q as o,c as M,r as P}from"./BnJiPali.js";import{l as F,s as C}from"./CAao-uWN.js";import{L as x}from"./B3NIBYEp.js";import{B as m,D as _}from"./B4UmIJW2.js";import{H as b}from"./BvtQlC5-.js";import{T as R}from"./DgMl03cG.js";const $={name:"MailPace",slug:"mailpace",logo:"mailpace.png",type:"marketing",spfAlignment:!0,dkim:!0,dkimAlignment:!0,updated:"2024-10-09T00:00:00.000Z"},{name:G,slug:O,logo:U,type:X,spfAlignment:Z,dkim:J,dkimAlignment:Q,updated:ee}=$;var T=d('<thead><tr><th>Type</th><th>Host</th><th>Value</th></tr></thead> <tbody><tr><td><code>CNAME</code></td><td><code>mailer.<span class="border border-slate-200 dark:border-slate-700 px-1.5 py-0.5 rounded-md">example.com</span></code></td><td>As provided by MailPace.</td></tr></tbody>',1),I=d('<!> <p>By default, emails sent through MailPace are not SPF-aligned. Outgoing emails will use the domain <code>mailer.mailpace.com</code> in the <code>Envelope From</code> (also known as <code>Return-Path</code>), causing SPF to be unaligned with your sender domain.</p> <!> <p>If you complete the <strong>Advanced Verification</strong> step, MailPace will use your domain in the <code>Envelope From</code>. This makes it possible to achieve DMARC compliance via SPF.</p> <p>To make sure your MailPace emails are SPF-aligned, complete the advanced verification in your domain settings.</p> <p>The advanced verification process involves creating a <code>CNAME</code> record that looks like this:</p> <!> <p>Since this is a <code>CNAME</code> record, MailPace will handle the SPF record for you on the target domain. You donât need to create an SPF record manually.</p> <p><a href="https://docs.mailpace.com/guide/verification#advanced-verification" rel="nofollow">Source</a></p>',1),K=d('<p>MailPace supports custom DKIM signatures domains. This makes it possible to achieve DMARC compliance via DKIM.</p> <p>All emails sent through MailPace are DKIM signed. Follow the instructions provided during the verification process to set up DKIM.</p> <p><a href="https://docs.mailpace.com/guide/verification" rel="nofollow">Source</a></p>',1),E=d('<p>MailPace supports DMARC compliance via both SPF and DKIM, with strict alignment on DKIM but only relaxed alignment on SPF.</p> <p>Set up DMARC to:</p> <ul><li>Receive email delivery reports to identify and fix authentication issues and find out whoâs sending from your domain.</li> <li>Choose the action to apply when both SPF and DKIM are not aligned with your sender domain, blocking abuse attempts.</li></ul> <p>Use a DMARC monitoring tool like <a href="https://dmarcwise.io">DMARCwise</a> to simplify compliance and detect issues before they affect your domain reputation.</p> <p>Hereâs an example of a DMARC record, to be created as a <code>TXT</code> record on <code>_dmarc.<span class="border border-slate-200 dark:border-slate-700 px-1.5 py-0.5 rounded-md">example.com</span></code>:</p> <pre>v=DMARC1; p=none; rua=mailto:<!>;</pre> <p>You may later strengthen the policy and change the alignment mode, but remember that in MailPace:</p> <ul><li>The SPF domain is a subdomain of your sender domain, so <strong>you cannot use the strict SPF alignment mode</strong>.</li> <li>The DKIM signature domain would instead match your sender domain exactly, so <strong>you may use strict DKIM alignment</strong>.</li></ul> <pre>v=DMARC1; p=reject; rua=mailto:<!>; adkim=s;</pre> <p>(<code>aspf=r;</code> for relaxed SPF is implied if left out.)</p> <p><a href="https://dmarcwise.io/docs/guide-to-dmarc-compliance">Guide to DMARC compliance</a></p>',1),H=d("<!> <!> <!>",1);function oe(D,A){const k=F(A,["children","$$slots","$$events","$$legacy"]);x(D,C(()=>k,()=>$,{children:(S,B)=>{var u=H(),h=p(u);m(h,{title:"SPF",children:(n,f)=>{var a=I(),r=p(a);b(r,{children:(t,v)=>{o();var s=y("Without advanced verification");i(t,s)}});var l=e(r,4);b(l,{children:(t,v)=>{o();var s=y("With advanced verification");i(t,s)}});var c=e(l,8);R(c,{children:(t,v)=>{var s=T();o(2),i(t,s)}}),o(4),i(n,a)}});var g=e(h,2);m(g,{title:"DKIM",children:(n,f)=>{var a=K();o(4),i(n,a)}});var w=e(g,2);m(w,{title:"DMARC",children:(n,f)=>{var a=E(),r=e(p(a),10),l=e(M(r));_(l),o(),P(r);var c=e(r,6),t=e(M(c));_(t),o(),P(c),o(4),i(n,a)}}),i(S,u)},$$slots:{default:!0}}
1))}export{oe as default,$ as metadata};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.