Purpose
This section explains the technical foundation required to send email from your own domain using Mapp Engage: setting up and verifying your sending domain, and authenticating your mail so that mailbox providers trust it.
Before productive sendouts can take place, the sending domain must be properly configured, verified, and authenticated. These settings are typically handled during system setup and may require coordination with your IT or domain administrator.
What This Covers
Getting your domain ready to send covers two areas:
Sender domain setup – delegating and verifying the (sub)domain you send from.
Email authentication – SPF, DKIM, and DMARC, which let mailbox providers verify that messages are legitimately sent on behalf of your organization.
Proper setup:
Confirms sender identity
Protects against spoofing and phishing
Contributes to sender reputation
Improves inbox placement
These settings apply at domain level and are independent of individual email messages or campaigns.
How Authentication Works (High-Level Overview)
All authentication mechanisms follow the same general process:
An email is sent via Mapp Engage.
Authentication information is included in the email header.
The receiving server retrieves DNS records for the sending domain.
The server validates the sender against those records.
If validation succeeds, the message is accepted as legitimate.
In This Section
Sender Domains
Delegate a Domain – hand a subdomain to Mapp's nameservers for sending
Domain Verification – ensure sendouts use a domain authorized for your system
Authentication Standards
SPF (Sender Policy Framework) – defines authorized sending servers
DKIM (DomainKeys Identified Mail) – adds a cryptographic signature
DMARC – defines domain-level policies and reporting