Custom Outbound Email Domains

Customer teams have the option to enable custom domains for emails sent from the Catalytic app. For example, a Workflow task that sends an email will deliver it from @{team-name}.customdomain.com. When a custom outbound email domain is set, it applies to all emails sent by a team鈥攊t cannot be done for just some emails.

If a custom domain is not set, all emails sent from the Catalytic app will default to @{team-name}.pushbot.com.

When you enable a custom domain, we authenticate emails using one or more of the following:

  • SPF MX record
  • DKIM record
  • DMARC policies

Examples of use

A custom domain is useful for teams depending on how they will be using emails. If many users outside the Catalytic team will receive e-mails, custom outbound domains can be beneficial for a number of reasons:

  • Increase external user trust with consistent company email domains.
  • Increase email delivery rate and avoid spam filters.
  • Or reduce employee or user confusion if they鈥檙e new to Workflow.

How to enable custom outbound email domains

Contact Catalytic Support if you would like to enable custom email domains. We can also configure a Static IP address range for outbound emails if requested by an administrator.

Example configuration requirements and setup for custom email domains

The following steps are a summary of the configuration requirements and implementation for custom email domains鈥攖his is just an overview and at this time, custom email domains must be set up through Catalytic Support.

Below is a summary of DNS records and a proposed plan for configuration, testing and release. The example uses DKIM-only DMARC validation and amazonses.com as the return-path, but other validation options are available.

Configuration summary

Customer will create the following DNS Entries:

  1. Domain verification record - SES validation TXT record
  2. DKIM record set - 3 DKIM records are required - to achieve DMARC compliance
  3. DMARC record - optional - if an official DMARC policy is required - can be added at a later date

For ease of setup we recommend a Time To Live (TTL) of 300 seconds for all records, but it can be different if customer鈥檚 TTL policy requires otherwise.

鈿狅笍 Heads-up: If you鈥檙e ready to enable custom outbound email domains, make sure you are ready for any technical configuration as DNS changes have to be made within 72 hours of starting the process.

Domain verification record

  • Name: _amazonses.<custom-domain>
  • Type: TXT
  • Value: To be provided by Catalytic

DKIM record set

  • Name: ,Token to be provided by Catalytic>._domainkey.<custom-domain>
  • Type: CNAME
  • Value: <Token to be provided by Catalytic>.dkim.amazonses.com

Configuration plan

The following steps outline the typical exchange in setting up the email domain.

Step 1: Catalytic

  1. Generate tokens - From the time we generate the domain verification and DKIM tokens in Amazon SES, customer will have 72 hours to add the DNS entries. Catalytic can generate and send the tokens at any time, but doing so on a Monday, Tuesday or Wednesday will maximize the number of working days for the customer to add the DNS entries.
  2. Send tokens to customer

Step 2: Customer

  1. Add DNS records
  2. Notify Catalytic that records have been added

Step 3: Catalytic

  1. Verify that the records have been validated by Amazon SES
  2. Test in a customer鈥檚 sandbox team

Step 4: Customer

  1. Test in sandbox team team
  2. Select go-live plan and date
  3. (Optional) Communicate internally and with third parties

Step 5: Catalytic

  1. On Go-Live date: Enable sending outbound emails from custom domain in production team
  2. Test

Step 6: Customer

  1. Test to confirm deliverability of emails
  2. (Optional) Communicate internally and with third parties