Email configuration

This guide covers domain and email addresses verification

To configure the Email platform, you have to

Please note that platform configuration is project-specific. Configure the Email platform for each project you want to use for sending emails.

Verified emails and domains are available for all projects in your account.

Email address verification

In your Pushwoosh project, go to the Configure Platforms section and click Configure next to the Email platform:

When configuring the Email platform for the first time, you'll have to verify the email address you're going to send messages from.

Enter the sender's email address (From Email) and name (From Name). After that, press Continue.

If you want the reply email and name to differ from the sender's, you can also specify them in the Reply-to Email and Reply-to Name fields. If you leave the Reply-to Email field empty, the recipients will reply to the sender email. You can also verify the additional Reply-to Email later.

We will send a verification email to the address you've entered. Please check the inbox and follow the instructions contained in the Sender Address Verification email. To complete the verification process, verify your domain.

Domain verification


The domain name should not contain non-ASCII characters. In case it does, please encode the domain name with Punycode as described in RFC3492.

Once you’ve added the email address and completed its verification, you have to verify the domain. By verifying the domain, you ensure your emails will be sent and delivered as they are supposed to be, and will not be filtered as spam.

Verify the domain by following these steps.

1. DMARC policy

Domain-based Message Authentication, Reporting and Conformance (DMARC) is an email authentication protocol. It is designed to give email domain owners the ability to protect their domain from unauthorized use, commonly known as email spoofing. Your Domain-based Message Authentication, Reporting, and Conformance (DMARC) policy is defined in a line of text values, called a DMARC record.

DMARC record is published in DNS with a subdomain label _dmarc, for example

Put the following content to TXT resource record to

v=DMARC1; p=quarantine;; pct=100; adkim=r; aspf=r should be a valid email address based on your domain.

More information about DMARC configuration options can be found on

If the DMARC policy is configured correctly, your DMARC domain's status on the Domains list will change to Verified.

2. DKIM authentication

DomainKeys Identified Mail (DKIM) is an email authentication method allowing the receiver to check that an email claimed to have come from a specific domain was indeed authorized by the owner of that domain.

To pass the DKIM authentication, follow the steps below to add CNAME records to your domain's DNS.

All the information about your domain is contained in a set of Domain Name System (DNS) records. A CNAME record is a type of resource record in the DNS which maps one domain name (an alias) to another (the Canonical Name).

1. To see the DKIM CNAME records, press the Settings button next to the domain status.

2. Carefully copy 4 CNAME records, double check each CNAME record value:

3. Sign in to your domain's account on the DNS provider’s website and add CNAME records to your domain's DNS.

Check out your DNS provider's instructions on adding CNAME records. For different providers, CNAME records may include or not include the domain name automatically.

If your DNS providers add the domain name to your DNS records automatically, you should enter only the domain key part manually, e.g.:

  • Name: f25jambtewmknd5u3wxa5v75uxkf7jnx._domainkey

  • Type: CNAME

  • Value:

To check whether that particular DNS provider serves the domain you're verifying, use free Whois services.

A CNAME record should consist of Name and Value as follows:

where first, second, third and fourth are unique CNAME parts for specific domains.

Make sure you've added all four CNAME records to your DNS records.

If the CNAME records are published correctly, your DKIM domain's status on the Domains list will change to Verified.

The verification process usually takes from 5 to 10 minutes. In some cases, it might take up to 24 hours. If the domain is not verified after 24 hours, please do not hesitate to contact us.

3. SPF authentication

Sender Policy Framework (SPF) is an email validation standard, defined in RFC 7208, designed to combat email spoofing. SPF enables domain owners to specify which mail servers are authorized to send emails for their domain.

Adding a new SPF record

If your domain does not have an existing SPF record, publish a TXT record with the following value. The name of the record can be blank or @, depending on your DNS service.

"v=spf1 ~all"

A TXT record is a type of DNS record providing additional text information about the domain.

Adding to an existing SPF record

If your domain already has an SPF record, then you must add the following SPF mechanism to the existing record.

You can check by yourself whether your domain's DNS records are updated correctly by following the procedure described in the Amazon How to Check Domain Verification Settings guide.

If the SPF record is published correctly, your SPF domain's status on the Domains list will change to Verified.

Adding Emails

To add one more email address, enter it into the field left to the Add email button, then press the button. Verify the address by following the instructions in the verification email you'll receive.

If the domain of the address you've added is not verified yet, verify it by following the steps described above.

Configuring Emails via Pushwoosh API

To configure Email platform via the Pushwoosh API, submit the configureApplication request.

Last updated