Domain settings

This guide contains examples of records that should be added to your domains for better deliverability.

The following IP addresses are used as an example:

• 192.168.0.1 — IPv4-address for web interface address;
• 192.168.0.2 — IPv4-address for message tracking;
• 192.168.0.3 — IPv4-address for website tracking;
• 192.168.0.4 — IPv4-address for sender (AKMTA).

Web interface domain settings

Choose a subdomain and add the following A record.

Domain	Record type	Contents
altcraft.example.com.	A	192.168.0.1

Message tracking domain settings

Choose a subdomain for your from-domain and add the following A record.

Domain	Record type	Contents
trk.example.com.	A	192.168.0.2

You can use unlimited additional tracking domains. The settings will be the same - or you can use CNAME records.

Web site tracking domain settings

Choose a subdomain and add the following A record.

Domain	Record type	Contents
pxl.example.com.	A	192.168.0.3

You can use unlimited additional tracking domains. The settings will be the same - or you can use CNAME records.

Sender domain settings (AKMTA)

Choose a domain or a subdomain and add the following records.

Domain	Record type	Contents
mail.example.com.	A	192.168.0.4
4.0.168.192.in-addr.arpa.	PTR	mail.example.com.
example.com.	MX	mail.example.com.

SPF settings

Sender Policy Framework (SPF) technology allows to verify that sender domain has not been faked. To make it work you need to add a special TXT record to your sending domain. It will allow only specified hosts to send messages using your domain.

We recommend to add records for different SPF versions:

Domain	Record type	Contents
example.com.	TXT	v=spf1 include:mail.example.com -all
example.com.	TXT	spf2.0/pra include:mail.example.com -all

caution

Note that we recommend to use restricting rules where only the enlisted resources are allowed!

DKIM settings

DomainKeys Identified Mail (DKIM) technology adds to your message a digital signature of your from-domain. The signature is automatically verified on the recipient side and hen it is used to manage sender reputation. The signature is technically an RSA key pair: the private part is built in sender infrastructure and the public part should be added to your domain as a special subdomain TXT record.

In Altcraft Administrative panel open Setup → Keys, then paste or generate a new DKIM:

Domain	Record type	Contents
altcraft._domainkey.example.com.	TXT	v=DKIM1; k=rsa; p=AAAAB3NzaC1yc2EAAAADAQABAAABAQDLWvAVr5k+4nneMRKhUeb/yGjRBlpGu9CLXx4LJJb1dUZeNWBCbjpjN0P5hlXD3tyml8aBJdHWtudeBvauUmxoxIfrkQW6XNwiplAXB/2bsECd1k5lPRnWzGAt8WOVI/ztOITmykZGLz9BHFIQ8i+Zte6ORlwfNiFyTLE9VE4ubzwIaOWr95MTXwtqC+zXIVwPqjZ0FYs7Ij0PnUAx805AK0I+I/4Fb58HJ9hdMeMiMsVb3Sz+AWby208QQubkAVfm4Zf4/RjW6uBlc1pSwYKy0fq13fHb6VltVXE+Q+Cbj8tYLJHStTT8bCepOcgGsvBkw+8WiuYZBHOX6gn3L/+5
_domainkey.example.com.	TXT	o=-;

caution

Please note, that you can use one DKIM for one sender only.

DMARC settings

DMARC technology allows mailing servers to decide what to do if SPF or DKIM verification fails.

Here we recommend to restrict messages sent from unknown IP addresses or signed incorrectly.

Domain	Record type	Contents
_dmarc.example.com.	TXT	v=DMARC1; p=reject; sp=reject; mailto:report@example.com

You will get replies to report@example.com.

BIMI settings

BIMI technology (Brand Indicators for Message Identification) is used along with SPF, DKIM and DMARC or identifying email sender by company brand logo, placed near the message subject in recipient's inbox. Email providers thus can additionally verify the sender.

To start using BIMI you will need an svg image, that is rectangular and has no extra layers.

Add the following record to your domain settings, specifying the svg file path:

Domain	Record type	Contents
default._bimi.example.com	TXT	v=BIMI1; l=https://example.com/bimi/bimi.svg

You can also use BIMI record generator at https://bimigroup.org/bimi-generator/