First steps
User Data
- Responsive Email Editor Review
- Designing your email
- Creating Synchronized Modules
- Setting Responsivity
- Building Smart Containers
- Creating a Gmail Promotions Annotation
- Adding The Rollover Effect
- Adding Anchor Links
- Module Library
- Adding a Table to an Email
- Adding Custom Fonts
- Creating CTA Button
- Working with Images
- Using AI in the Email Editor
Omnichannel
- Setting Up Widgets for Your Site
- Widget Calling
- Setting Up Locations for the Widget Calling Rules
- Storing data from widgets to contact fields
- Using Annoyance Safeguard
- Actions After Form Submission
- Replacing Double Opt-In System Workflow
- Using Yespo Extension for Google Chrome
- Creating Pop-ups via Google Tag Manager or WordPress
- Sending Yespo Widget Events to Google Analytics
- Using A/B Tests for Widgets
Automation
- Double Opt-In
- Welcome Сampaign
- Welcome Series Segmented by Category
- Launching a Workflow After a Contact Import
- Regular Workflow for a Segment
- Birthday Campaign
- Linking Workflow to the Button
- Using Variables from Order in Workflow
- Collecting Order Feedback
- Customer Reactivation
- Sending Extra Campaigns
Personalization
Analytics
- Email Campaign Report
- Web Push Campaign Report
- Viber Campaign Report
- Mobile Push Campaign Report
- App Inbox Campaign Report
- Widget Report
- Triggered Campaign Report
- AMP Campaign Report
- SMS Campaign Report
- Multilingual Campaign Report
- Setting up UTM Tags
- Revenue from Campaigns
- Tracking Campaign Performance in Google Analytics
Multilanguage Campaigns
Events and Behaviour Tracking
Recommendations
API
Security and Compliance
Integration
DNS Record Change
Let’s say you have your own domain domain.com and you want to send messages From: name@domain.com
Under typical conditions, the email is formed in such way:
In header, the field From gets your address: name@domain.com, the To field is the recipient's address, in the fields Sender and Return-Path - our technical address, where the delivery errors are caught. The email is signed by our DKIM.
Google shows that such letter is
Mailed-by: our domain
Signed-by: our domain
In some cases, it would be better to sign your letters with your DKIM in order to meet DMARC requirements, for example, make messages correctly displayed in MS Outlook 2016.
There are 3 options to set it up:
1. “Full” option
2. Option “Full+”
3. Option “Subdomain”
1. “Full” option
This option may be required if you want to make your messages as beautiful as possible and do not want to have esputnik reference in the header of the email. So that Google and other email systems believe that mailed-by: domain.com.
As for the "Simple" version, you need to enter 2 lines in the DNS - SPF and DKIM:
esputnik._domainkey.domain.com. | CNAME | dkim.esputnik.com. |
domain.com. | TXT | "v=spf1 include:spf2.esputnik.com ~all" |
But beyond that, you also need to set the Return-Path: header of the email with technical address, where the delivery errors will be caught, in your domain.
An example of this address is: bounce+g3-support=mail.ru@domain.com. In the general case, bounce +smth@domain.com.
All emails arriving at this address must be forwarded to our mailbox, where the handler will parse delivery errors.
This is where the difficulties begin - very few postal providers allow you to receive mail on the bounce box, dropping the suffix "+" and everything that goes after it.
We know for sure that this is how Google services work, and so does ours.
If your mail server is able to drop the suffix off and can all mail sent to bounce+smth@domain.com receive in bounce mailbox, you need to configure only 2 forwarding - send copies of the messages:
From the box bounce@domain.com to the address bounce@trap.esputnik.com,
From the abuse@domain.com box to abuse@trap.esputnik.com.
In case your mail server does not know how to drop the suffix off and you, for some reason, do not want to transfer your mail to a mail service that knows how to do this (for example, Google), you have two options:
1) implement “Full+” option - the 2nd one in this document;
2) you can declare our server as a mail server for your Domain. Then our server will receive all the mail for your domain, process errors and the letters arriving at the boxes, which you specify, and forward them to your other addresses. The rest of the mails will be deleted.
After that, your emails will look as follows - From: name@domain.com, the Sender field: is missed, in the Return-Path field: the technical address in the domain.com domain where the delivery errors are caught. The message is signed by your DKIM.
Google shows that such letter is
Mailed-by: domain.com (your domain)
Signed-by: domain.com (your domain)
2. Option “Full+”
This option may be required if you want to make your messages as beautiful as possible and do not want to have esputnik reference in the header of the email but
your postal provider is not able to drop the suffix off while getting the email so you can not use the second option.
As a solution, we recommend to organize emailing from the technical address in the subdomain zone of your domain.
Our service will process all the emails arriving at this subdomain.
In this case you add four entries to your DNS domain settings: DKIM, SPF and MX.
esputnik._domainkey.domain.com. | CNAME | dkim.esputnik.com. |
domain.com. | TXT | "v=spf1 include:spf2.esputnik.com ~all" |
promo.domain.com. | TXT | "v=spf1 include:spf2.esputnik.com ~all" |
promo.domain.com. | MX | 10 trap.esputnik.com. |
Inform us, so we could change the settings of your personal account on our side.
After that, your emails will look as follows - From: info@domain.com, the Sender field is missed, in the Return-Path field - the technical address in the domain promo.domain.com where the delivery errors are caught. The message is signed by your DKIM.
Google shows that such letter is
Mailed-by: promo.domain.com
Signed-by: domain.com
3. Option “Subdomain”
This option may be required if you want to make your messages as beautiful as possible and do not want to have eSputnik reference in the header of the email but you want to separate campaigns from your main domain.
As a solution we recommend to organize emailing from the subdomain of your domain.
Our service will process all the emails arriving at this subdomain.
Such messages will look “almost like” yours. But they are not from your domain domain.com, they are from the subdomain, for example, promo.domain.com.
In this case you add three entries to your DNS domain settings: DKIM, SPF and MX.
esputnik._domainkey.promo.domain.com | CNAME | dkim.esputnik.com. |
promo.domain.com. | TXT | "v=spf1 include:spf2.esputnik.com ~all" |
promo.domain.com. | MX | 10 trap.esputnik.com. |
All mail sent to the subdomain will be sent to our mail servers and forwarded to your address which should be specified in the email for replies field.
Your emails will look as follows - From: info@promo.domain.com, the Sender field - is missed, in the Return-Path field - the technical address in the domain promo.domain.com where the delivery errors are caught. The message is signed by your DKIM.
Google shows that such a letter is
Mailed-by: promo.domain.com
Signed-by: promo.domain.com
Please Note!
For tracking email deliverability on different domains you should register yourself in relevant postmasters.
For one domain or subdomain the TXT string "v = spf1 ..." should be only one in DNS. Thus, if you already have some SPF settings, you need to combine them with ours. The SPF mechanism has limitations on the total length of the string (450) and the number of DNS queries for obtaining complete information (10). If the values are exceeded, the SPF stops working. Therefore, we recommend to use the SPF validation tool (Advanced tab) before adding a merged string to the DNS.