Email Domain Configuration

If you plan to send bulk emails, take care of the sender's reputation. Here we will look at the technical aspects that help you to verify email content and avoid the forgery of your sender’s name.

Under typical conditions, the email is formed in such way:

In header, the field From gets your address: [email protected], 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.

It would be better to sign your letters with your DKIM in order to meet DMARC requirements.

3 options how to set it up

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:

🚧

But beyond that, you also need to set the Return-Path: header of the email with the technical address, where the delivery errors will be caught, in your domain.

An example of this address: bounce+g3-support=[email protected]. In the general case, bounce [email protected].

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 and Yandex mail services work, and so does ours.

If your mail server is able to drop the suffix off and can all mail sent to [email protected] receive in bounce mailbox, you need to configure only 2 forwarding - send copies of the messages:

From the box [email protected] to the address [email protected],
From the [email protected] box to [email protected].

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:

• implement “Full+” option - the 2nd one in this document;
• 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 emails will be deleted.

Inform us, we change the settings of your personal account on our side.

After that, your emails will look as follows - From: [email protected], 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 a letter is

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 Reteno 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.

🚧

Inform us, so we could change the settings of your personal account on our side.

After that, your emails will look as follows - From: [email protected], 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

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.

🚧

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: [email protected], 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

🚧

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 the 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.