[ Sending-service guides ]

Authenticate email sent through LianaMailer: configuration and verification

Configure LianaMailer domain authentication and its related subscription-page identity, then prove the actual newsletter route with a received message.

By the EmailAuth research team · 4 min read

[ Key points ]

  • Keep newsletter changes coordinated
  • Prove the envelope relationship
  • Protect shared domain policy
On this page
  1. Key points
  2. Takeaway
  3. By role
  4. Frequently asked questions
  5. Sources
  6. Glossary
  7. Related guides

[ Takeaway ]

Configure LianaMailer domain authentication and its related subscription-page identity, then prove the actual newsletter route with a received message.

[ By role ]

What this means for you

Choose your role for practical next steps.

IT / Mail Admin

Prove the envelope relationship

The domain used by the subscription site can affect the documented envelope identity.

Next steps

  1. Capture the suggested account records.
  2. Confirm support finalization.
  3. Compare site, From and Return-Path in a test.

CISO / SecOps

Protect shared domain policy

A newsletter rollout must not remove another sender or dilute established enforcement.

Next steps

  1. Review SPF scope and lookup cost.
  2. Check DKIM alignment.
  3. Approve the evidence before production.

Founder / Non-technical

Keep newsletter changes coordinated

The sending template, domain and subscription site can involve different owners.

Next steps

  1. Name a campaign owner.
  2. Schedule DNS and support work together.
  3. Retain the prior working campaign route.

[ FAQs ]

Frequently asked questions

Where do I get the correct LianaMailer DNS records?

Use the suggested values for the active domain in Settings > Domain Settings, with support confirmation for the exact account.

Information about DMARC changes and deliverability

Why must I also check Settings > Sites?

Liana documents a relationship between the subscription-site domain and the envelope sender in its setup arrangement. Confirm the actual result in a received message.

Instructions for IT support

Can I assume SPF must be changed at my root domain?

No. Liana support checks the need and supplies the appropriate value; inspect the actual envelope domain before editing DNS.

Instructions for IT support RFC 7208 SPF

Does a green Verified indicator prove DMARC passes?

No. It confirms a configuration check, while a received message is needed to establish authentication and alignment.

Information about DMARC changes and deliverability RFC 9989 DMARC

Should I copy another account’s DKIM selector?

No. Use the DNS owner and public value provided for your account and sending domain.

Information about DMARC changes and deliverability

Does a branded subscription URL guarantee delivery?

No. It is a separate configuration and functional check; authentication, content and receiver filtering still matter.

Instructions for IT support

Is support involvement finished when DNS is saved?

The cited workflow calls for informing support so it can finalize the settings. Retain that confirmation.

Instructions for IT support

What still blocks approval of this guide?

Exact tenant applicability, live DNS, the original received-message identity table and human SME review remain open.

[ Sources ]

Sources

  1. Information about DMARC changes and deliverability

    Sections What should I do? · Suggested DNS settings · Subscription page url

  2. Instructions for IT support

    Sections DKIM · SPF · Follow these instructions

  3. RFC 7208 SPF

    Sections §4.6.4 · §3.2

  4. RFC 6376 DKIM

    Sections §3.5 · §6

  5. RFC 9989 DMARC

    Sections Identifier Alignment

[ Glossary ]

Glossary

Subscription site
The LianaMailer site used for subscription-related pages and relevant to its documented envelope setup.
Suggested DNS values
Account-displayed public records proposed for a selected LianaMailer domain.
Support finalization
The provider step described after required DNS records have been published.
Envelope sender
The SMTP identity used by SPF and associated with the received Return-Path.
Alignment mode
The policy setting determining how closely an authenticated domain must match the visible From domain.

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