To make sure that your emails reach your subscribers’ inboxes and not their spam folders, it is important to properly set up the email you will use for email marketing.
If you send emails from public domains like @gmail.com, your campaigns are more likely to end up in spam.
Some email service providers prohibit bulk emails from public domains, so if you do that, your campaign will be rejected by the recipient's service and the email will not be delivered.
If you use a public domain email address to send emails via Selzy, you can only send to a list of up to 50 contacts.
Using a public domain email address you will also not be able to send emails in automations.
We recommend creating a corporate email on your domain and setting up email authentication. This way, you can send any number of emails within your chosen plan.
If you already have a corporate email address, go to the Set up email authentication section and follow the setup instructions.
To set up your corporate email address, you will need a website and access to the control panel of the website hosting.
Register a corporate email address
Any campaign works better when sent from a corporate email address. It is an address that is registered with the website domain. For example, @uber.com, @booking.com.
The campaigns sent from a corporate email address don’t raise suspicions in email service providers. Besides, a corporate email address looks nice and is convenient to use. The domain in its name tells the recipient which company is the sender.
If you want to register a corporate email using Google, follow this instruction on how to create an email address at your domain.
Set up email authentication
Email authentication is the process of verification of an email sender. It is used to improve the deliverability of campaigns.
Email authentication works as an ID. Email service providers check whether you have authentication or not and decide whether to allow a campaign to go to their inboxes or not. If you set up authentication, the fraudsters won’t be able to send emails using your domain name.
Authentication gives you two benefits:
- Increases the chances for your campaigns to end up in the inbox. Authentication helps an email provider understand who sent the email — a reliable sender or a fraudster. If you are not sending spam, your chances of getting to the inbox grow.
- Allows you to use postmasters. Postmaster Tools from Gmail is an example. These are special services from email providers that show the domain reputation, the percentage of emails of ending up in spam, and the deliverability for a specified email service provider. You will not be able to access this data without email authentication.
Follow the steps below to set up email authentication.
If you do not have enough time or experience difficulties with the process, you can always order the setup service from Selzy Customer Service.
Add your email to confirmed emails
Before setting up email authentication, add a corporate email address at Confirmed Emails in your Selzy account. Go to Account → Settings → Account setup → Confirmed emails.
Click Add. Next, enter your email and name. In the Name field, you can enter your name or the company name. This is the sender’s name that will be indicated in your emails when sending. The name helps your subscribers to determine the sender of the campaign. You can change the sender’s name in the Confirmed emails section of the Settings.
Click the Confirm button.
You will receive a confirmation email to the specified email address.
Check the inbox for the Selzy email and click on the Confirm e-mail address button.
Set up domain authentication
SPF & DKIM
In your Account, go to Settings and choose Domain Authentication. To set up domain authentication for the corporate email address you use to send your campaigns, click on the Create button.
You will be able to add a domain only if you have a confirmed email with this domain at Selzy.
Add the domain name (the address of the website without the protocol), and click on the Obtain Settings button.
You will see the window with the information you need to copy to the domain hosting.
SPF shows which email servers are allowed to send emails on your behalf. If you use an email marketing service, you should state it in the SPF.
DKIM allows the sending server to sign your emails with a unique key. If someone decides to send an email using your domain name, they will not have this key. So email service providers will detect that and put the fraudster’s email in the spam folder.
To complete the setup of DKIM and SPF authentication, add TXT records using the information obtained from your Selzy account to your domain hosting account.
If you don't know what hosting you are using, go to NsLookup to look it up.
For example, let’s find out the hosting for Reserved.com.
After the check-up, we see that according to NS records, the authentication should be set up in the Cloudflare hosting.
Let’s take Hostinger to show how to add records. You can do it with any other hosting, only the interface will be different.
Go to the hosting homepage, find the domain you need in the Domain tab, then click on the Manage button next to it.
Domain management panel at Hostinger
Then, go to the DNS / Nameservers tab where you can manage DNS records of the domain.
From the DKIM & SPF settings window in your Selzy account, copy @ TXT v=spf1 include:spf.selzy.com ~all and paste it to the hosting.
- @ — the name of the record (host) or subdomain. If @ is not allowed to be used, use your domain name in the Host (Subdomain) field.
- TXT — the type of the record.
- v=spf1 include:spf.selzy.com ~all — the value of the record.
Enter the data you have for the SPF record into the fields. In the TTL field, you can leave the default value. This value is the record data refresh time in seconds.
Fill in all the fields and click on the Add Record button.
Even if you use different services, you must have one merged SPF record. This record includes all services you are going to use for your campaigns.
In the example below the SPF record includes 2 services: Selzy and mail.hostinger.com.
Here is what the merged SPF record looks like
Now, you need to create another record, just as you did with the SPF record before. To create the DKIM record, take the record data from your Selzy account and add it to the hosting.
| us._domainkey | TXT | v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQD0l3mpHnuXwYcWwNQjURQKJGPDrzQH9BVXXWMT2TGLdxbXitJEdbjd7fB729q0kaoYK61eDAyaaEg0Y4ITmO+xvatxTQCNq0srPTF3dfc5mbrOFc0HsAtOy0faXUDF8veDr+bs8kcCtoQHpwks+51SXv3ETjMld/TWZicwc3nVIQIDAQAB |
- us._domainkey — the name of the record (host) or subdomain. The record must contain us._domainkey.
- TXT — the type of the record.
- v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3D… — the unique value of the record for each domain in the system. This is the DKIM key.
Some domain control panels demand your domain (the one you are setting up the authentication for) to be manually given next to us._domainkey, e.g., us._domainkey.yourdomain.com. However, at the majority of hostings, the us._domainkey as the name of the entry is enough.
Choose the same type of record as for the SPF — TXT. Copy and paste the DKIM key in the TXT value field and click on the Add Record button when you are ready.
After you have set up the hosting data, return to your Selzy account, go to Settings → Domain Authentication and check whether the status has changed to Enabled. This status means that the authentication was successful.
The status update takes time. You might need to wait from half an hour to a couple of hours for the status to change.
To refresh the status manually, click on two arrows next to the status.
Done! You have successfully set up email authentication for your account.
DMARC
In addition to SPF and DKIM, you can set up DMARC, an additional email authentication protocol, to specify the policy for interpreting these records. The three main policies are "none," "quarantine," and "reject."
This way, email providers will receive instructions on how to handle situations where an email is sent from your domain but SPF and DKIM authentication fail, typically indicating an attempt to send spam using your domain.
With DMARC in place, you will also receive aggregate reports about failed checks.
If you send more than 5,000 messages per day to Gmail accounts, you must set up DMARC to comply with the Google policies for bulk senders.
If you have configured the SPF and DKIM just now, wait for a couple of days before configuring DMARC. DKIM and SPF should be authenticating messages for at least 48 hours before you can turn on DMARC.
Unlike with DKIM and SPF, you should create a DMARC record yourself. Open a text editor and create a DMARC TXT record for your domain.
A basic DMARC record looks like this:
v=DMARC1; p=none; rua=mailto:[email protected]
- v=DMARC1 — Indicates that this is a DMARC record.
- p=none — Specifies the policy for messages that fail DMARC checks. In this example, it's set to "none," meaning no action will be taken. You can later change it, if you need to.
- rua — Specifies the email address to which aggregate reports should be sent.
Start with a DMARC policy of "none" to monitor and gather reports without impacting your legitimate emails. This is sufficient to meet Google requirements for bulk senders.
Once you are confident that your legitimate emails pass authentication checks, consider moving to a more restrictive policy like "quarantine" or "reject."
Store the record in your domain’s DNS settings. Again, as with DKIM and SPF, go to your hosting account, in our example it’s Hostinger, choose the domain and add a new TXT DNS record, containing the DMARC record you created.
Common questions
What should I do if I already have an SPF record from a different service?
Even if you use different services, you will have one SPF record. This record includes all services you are going to use for your campaigns.
For example, you are using Selzy together with your inbox at Outlook.
In this case, add “include:spf.selzy.com” to the already existing record of “v=spf1 include:spf.protection.outlook.com ~all”. If there is “redirect=” in your record, you must change it to “include:”. The merged record must end with “~all”.
As a result, your SPF record will look like this:
v=spf1 include:spf.protection.outlook.com include:spf.selzy.com ~all
You can edit the standard SPF record at any other email provider in the same way.
I have followed all the instructions, but the Selzy status is still "created" or "disabled". What should I do?
If you refresh the status and see the notification that no errors were found, wait for 30 more minutes. The status will be updated to enabled.
When you refresh the status, the following errors might occur:
- DKIM record not found.
- SPF record missing.
- The obligatory parameter “include:spf.selzy.com” is missing from the SPF record.
In this case, you should check whether your records at the domain hosting are correct.
We recommend you double-check extra spaces, as they are taken into account when reading the record. You can also check whether you have added the records to the right hosting.
Useful links:
Google & Yahoo Introduce New Requirements for Bulk Sending
The Importance of SPF Record and How To Set It
How To Authenticate an Email: SPF, DKIM, DMARC, and BIMI