When sending emails from you workspace, via Backstage, the @spotme.com domain is used by default.

The Emailing module on SpotMe Backstage allows you to use your own domain name when sending app activation emails, invitations or others.

This however requires a change on a certain email authentication method used by the Emailing module, called SPF and DKIM.

Both DKIM (DomainKeys Identified Mail) and SPF (Sender Policy Framework) are designed to detect forging sender addresses in emails.

SPF (Sender Policy Framework)

If you use your own domain to send emails from SpotMe Backstage, you have to update your SPF record (or create one if you don't have one already) in order to publicly allow our servers to send emails on your behalf. Otherwise, it is very likely that email recipients will consider your emails sent from the platform as spam.

To ensure emails are correctly delivered, the SPF record of your domain needs to include "include:_spf.spotme.com", as follows:  

v=spf1 include:_spf.spotme.com -all

SPF records are public and can be verified using a SPF record lookup from any free web tool, such as MxToolBox (https://mxtoolbox.com).

The SPF record can be updated via the DNS server by the administrator. Therefore, to change the domain name for emails sent from your workspace, you will need to contact your organization's dedicated IT department.

Important: The recommendation is to use a TXT record type to publish the SPF record.
More information.

For more information about SPF, please refer to https://tools.ietf.org/html/rfc4408 and https://tools.ietf.org/html/rfc7208

DKIM (DomainKeys Identified Mail)

Add a new TXT record with the name mandrill._domainkey.yourdomain.com (just replace yourdomain.com with the domain you're setting up).

The value for the record should be one of the options listed below. There are two options because the record contains semicolons. Some DNS providers escape semicolons for you while others require you to do it when you set up the record.

With semicolons escaped:

v=DKIM1\; k=rsa\; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB\;

With semicolons unescaped:

v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSR

For more information about DKIM, please refer to https://tools.ietf.org/html/rfc6376.