[ Sending-service guides ]

Authenticate email sent through MailPoet: configuration and verification

Authenticate the actual MailPoet sending method and From domain, using aligned DKIM for the MailPoet Sending Service rather than trying to align its provider-managed SPF with a root-domain edit.

By the EmailAuth research team · 7 min read

[ Key points ]

  • Record the actual MailPoet sending method and account.
  • Authorize the real From domain and manually verify issued DNS records.
  • Use aligned DKIM rather than guessing a customer-domain SPF include.
On this page

[ Takeaway ]

Use aligned DKIM rather than guessing a customer-domain SPF include.

[ By role ]

What this means for you

Choose your role for practical next steps.

IT / Mail Admin

Authenticate the real sender

Account, template and transport settings all affect the message being tested.

Next steps

  1. Capture the current Send With setting.
  2. Use records for the actual From domain.
  3. Retest each material workflow.

CISO / SecOps

Require aligned evidence

Provider SPF does not necessarily align with the customer From.

Next steps

  1. Inspect every DKIM identity.
  2. Preserve enforced DMARC policy.
  3. Approve the original receiver evidence.

Founder / Non-technical

Keep WordPress mail routes explicit

Newsletters and other site messages may travel through different systems.

Next steps

  1. Identify the actual delivery provider.
  2. Assign owners to active automations.
  3. Approve route changes before resuming sends.

[ FAQs ]

Frequently asked questions

[ Sources ]

Sources

  1. Settings > The Send With Tab

    Sections Sending methods31 onward; Sending Service34; Other43 onward

  2. How to Set Up the MailPoet Sending Service – MailPoet Knowledge Base

    Sections Key activation32–41; preview44–48; domain51–55

  3. Authorizing FROM Email Addresses

    Sections Address confirmation40–50; domain55–66; account/template80–84

  4. Email Authentication: SPF, DKIM, DMARC – MailPoet Knowledge Base

    Sections From65–73; verify76–98; DNS failures110–136; pause137–143; provider SPF146–150

  5. The Newsletters Are Not Being Received – MailPoet Knowledge Base

    Sections Account suspension47–49; restricted recipients52–54; verified sender55–57; Other sending method

  6. RFC 7208 SPF

    Sections §3.2; 3.3; 4.6.4

  7. RFC 6376 DKIM

    Sections §3.5; 3.6.2; 6.1

  8. RFC 9989 DMARC

    Sections §4.4; 4.7; 4.10; 5

[ Glossary ]

Glossary

Send With setting
The MailPoet selection that determines the newsletter delivery method.
Sender Domain
The domain in the actual email From address, which need not match the site domain.
Address authorization
An account-level permission to use a From address, separate from receiver authentication.
Provider envelope
The SMTP identity managed by a sending service and evaluated for SPF.
Workflow-specific evidence
A received message from the newsletter or automation being approved rather than an unrelated site email.

Enterprise provenance

Why top financial institutions and governments retired their email security dashboards.

Traditional email authentication platforms sell you a dashboard and ask your engineers to do the labour. In high-stakes environments, manual oversight means delayed enforcement, configuration drift and unmonitored shadow domains.

EmailAuth is the agentic email provenance platform. Our agents enforce p=reject, keep third-party senders aligned and move your domains to full RFC 9989 compliance, the new DMARC standard,, with human-in-the-loop auditability.

Governments Large enterprises Tier-1 financial institutions

SaaS · Dedicated tenancy · Air-gapped on-prem · BYOK encryption

Knowledge Base