Configuring custom domain

Handling SPF, DKIM and DMARC profiles

If you do not configure a custom domain on your tenant, then you make use of Upodi's own domain for email sending. If that is the case Upodi is responsible for email delivery and you do not have to consider any configuration on your domain etc.

Using a Custom Domain

If you want to configure Upodi to send out on your behalf you have to first of all register your domain on the Upodi platform here in the domain section of marketing. Once this is done you will see some DNS-records that you will have to install on your domain in order to verify ownership of the domain. Once these are correctly installed the domain will be verified and useable as the sender email of email communication going out from the Upodi platform.


What is DMARC?

DMARC (Domain-based Message Authentication, Reporting and Conformance) record is a type of DNS record such as SPF, CNAME, MX, DKIM, etc.

DMARC (if configured with policy) is used to inform the email receiving server whether or not to accept an email from a particular sender. The email receiving server will check for the policy and decide on whether to allow the email to the users' inbox or to discard it. It validates the From address given in the email sent by verifying it with the domain providers DMARC policy.

For more information, visit

When you have created your domain on the Upodi platform it will be in a pending state. Ask the Upodi helpdesk to receive the DNS-changes you have to implement in the DNS-records of your domain in order to verify ownership of the emails we are sending from Upodi. The guide you receive will explain which changes you have to do but here we also explain some of those changes in depth.

TXT-type changes (Required)

Two changes are required in your TXT-type records, while there are also some MX-type and CNAME-type changes, which are optional. We will cover the required ones here.


The first SPF-record is a record with the name of your hostname, so this would be the same domain as you've created for the domain. Fx. If you have no SPF-record today the SPF-record contents should look like this:

v=spf1 ~all

If you already have an SPF-record and want to include the mailgun alongside other includes, merge it like this:

v=spf1 ~all

Public key SPF-record

You also need to include a TXT-record containing your public key. This is another TXT-file with the name of where you once again insert the chosen domain instead of The contents of this record would look something like this:

k=rsa; p=MAGyMA0GFSqGSIb3DQEBAQUAA4GNADCBiQKBgQC42JSaOGmME/Z90rl9AxV6SAjXPcdtvayRtNdKgN43EG2/GxjCYndOCuZzG2BkB2e0hNCA1lP952Dv0+I+gjwSBa4Ml60yNaJgR3FgNcH0wQ2d8C6dCP+R15LtjD3wo5IEP3exMB/niWYzt+UKnTGtv+48bY0giiEL4g3UUnoQNwIDAQAB

Please be aware if you copy this value from somewhere that the contents match the key exactly and that there are no white spaces or line breaks copied to the contents.