Transactional Emails¶

This document covers the measures that can be taken in order to ensure that the transactional emails from Tulo Payway reaches the recepients when using the Payway SMTP server.

1. SPF¶

To prevent problems with mail sent from Payway getting classified as "spam" or beeing blocked since it's not allowed to send mail from your domain, you should ask your IT-department or the ones managing your DNS-records to make use of "Sender Policy Framework" (SPF). The following is an example of what can be added to the SPF record:

"v=spf1 ip4:80.76.153.145 ~all"

How to check if a domain has the SPF record added

Run the following command in a command prompt, look for 80.76.153.145 in the output.
nslookup -type=txt <domain>

2. DKIM¶

DomainKeys Identified Mail (DKIM) enables domain owners to automatically sign emails from their domin. The DKIM signature is a digital signature that uses cryptography to verify that the email originates from the domain.

In order to start using DKIM with your transactional emails you first need to contact the Payway Support in order to retreive the public key part of the certificate. This key is then added to your domain in a DKIM record.

basefarm._domainkey     IN      TXT      "v=DKIM1; k=rsa;  p=<your public key>"

If you receive an error message saying its too long you can have a look at this article.

After the addition of the TXT record to your domain you need to contact the Payway Support and confirm the addition of you TXT record. Payway Support will complete the activation of DKIM.

3. DMARC¶

DMARC, or Domain-based Message Authentication Reporting and Conformance, tells a receiving email server what to do given the results of a SPF and DKIM check. A domains DMARC policy can instruct mail servers to quarantine, reject or deliver emails that fail SPF and/or DKIM checks. DMARC policies are stored in DMARC records and can also contain instructions to send reports to the domain administrators.