Email Authentication

Introduction

Email authentication helps prove that your emails really come from your organization. It’s a set of mechanisms that lets receiving email servers verify your sender identity. This reduces the risk of email spoofing and improves your chances of reaching the inbox.

Authentication is essential for email deliverability and sender reputation, but it doesn't validate the content or safety of your emails.

Common Use Cases

• Prevent spoofing and phishing using your domain

• Improve inbox placement by proving sender identity

• Establish sender reputation with mailbox providers

• Enable DMARC-based reporting and policy enforcement

• Support secure sendouts from new domains

Components and Workflow

All authentication methods follow a similar process:

1. You send an email via Mapp Engage.

2. Mapp adds authentication info to the email header.

3. The receiving server fetches DNS records for your domain.

4. It compares these records to the header info.

5. If they match, the email is accepted as legitimate.

Mapp supports these key mechanisms:

• SPF (Sender Policy Framework): Lists authorized sending servers.

• DKIM (DomainKeys Identified Mail): Adds a cryptographic signature to verify sender and content integrity.

• DMARC: Builds on SPF and DKIM to define policies and receive feedback from mailbox providers.

Tip: Use the Message Check feature in Mapp Engage to verify that your authentication settings are correctly in place before sendout.