Purpose
This section explains the technical foundation required to send emails from your domain using Mapp Engage.
Before productive sendouts can take place, the sending domain must be properly configured and authenticated. These settings are typically handled during system setup and may require coordination with your IT or domain administrator.
What This Covers
Email authentication ensures that mailbox providers can verify that messages are legitimately sent on behalf of your organization.
Proper authentication:
Confirms sender identity
Protects against spoofing and phishing
Contributes to sender reputation
Improves inbox placement
Authentication applies at domain level and is 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.
Supported Standards
Mapp Engage supports the following industry standards:
SPF (Sender Policy Framework) – Defines authorized sending servers
DKIM (DomainKeys Identified Mail) – Adds a cryptographic signature
DMARC – Defines domain-level policies and reporting
Detailed configuration instructions are provided in the articles below.