Connect Servercore email service
- Create an email resource.
- Create a TXT record to verify domain ownership.
- Add the domain to the resource.
- Create a DKIM record.
- Configure a DMARC record.
- Configure an SPF record.
- Configure sending via SMTP.
1. Create an email resource
- In the control panel, in the top menu, click Products and select Email Service.
- Click Create resource.
- Enter a resource name. The name does not affect resource settings and is used only in the Control Panel.
- Click Create.
2. Create a TXT record
To add a domain to a resource, you must first verify your ownership of it by creating a TXT record for the domain with the unique resource key. Propagation of the record to caching servers may take up to 72 hours.
- In the control panel, in the top menu, click Products and select Email Service.
- Open the resource page → Information tab.
- Copy the value in the Domain ownership verification key field.
- Go to the domain registrar panel where your domain's resource records are stored.
- Create a new resource record for the domain.
- Specify the record type as TXT.
- Specify the record name — the name of your domain, for example
example.com. - Paste the record value of the format
74f878e2-dia4-477a-ccc5-989f428173f9that you copied in step 3.
3. Add a domain to a resource
You can add up to three domains to a resource.
- In the control panel, in the top menu, click Products and select Email Service.
- Open the resource page → Information tab.
- In the Linked domains block, click Add.
- Enter the domain name for which you created a TXT record, without specifying the protocol.
- Click Add.
4. Create a DKIM record
After changes, DNS records may take up to 72 hours to update.
-
Go to the domain registrar panel that manages your domain.
-
Create a new resource record.
-
Specify the record type as TXT.
-
Specify the record name:
srvcr._domainkey.example.comHere,
example.comis the domain name you added to the resource. -
Specify the record value; you can copy it in the control panel: in the top menu, click Products → Email Service → resource page the domain is linked to → Information tab → domain card → DKIM line.
5. Configure a DMARC record
After changes, DNS records may take up to 72 hours to update.
-
Go to the domain registrar panel that manages your domain.
-
If you already have a DMARC record, change the value of the
pparameter toquarantine, for example:v=DMARC1; p=quarantine; -
If you do not have a DMARC record, create one:
- record type — TXT;
- record name —
_dmarc.example.com, whereexample.comis the domain name you added to the resource; - value —
v=DMARC1; p=quarantine;.
6. Configure an SPF record
After changing a DNS record, it may take up to 72 hours for updates to propagate. A domain can have only one SPF record.
-
Go to the domain registrar panel that manages your domain.
-
If you already have an SPF record, add the
include:spf.servercore-smtp.comblock to it, for example:v=spf1 include:spf.servercore-smtp.com include:domain2.com ?allWhere:
include:spf.servercore-smtp.com— added block;include:domain2.com— example of the rest of the record content.
-
If you do not have an SPF record, create one:
- record type — TXT;
- record name —
example.com, whereexample.comis your domain name; - record value —
v=spf1 include:spf.servercore-smtp.com ?all.
7. Configure SMTP sending
You can use any email address on the domain for which you enabled the email service as the sender address.
In the settings of the utility used on your server to send emails, enter the sending details:
-
server name (hostname) —
smtp.servercore-smtp.com; -
port (port):
- port 1126 — if you need to establish a no SSL / STARTTLS connection;
- port 1127 — if you need to establish a TLS (SSL) connection.
-
login and password can be found in the control panel: in the top menu, click Products → Email Service → Email Service section → page of the resource to which the domain is added → Information tab.
To configure mailouts from a Linux server via the sSMTP utility, use the Configure sending mail via sSMTP on Linux instructions.
Pay attention to possible errors in the SMTP conversation.