Custom Email Domain

By default, outbound emails (sent via /send) come from no-reply@mail.scitor.io. With a Pro plan, you can send from your own company email address instead.

You don't need a separate email provider account

Scitor handles email sending for you through our email infrastructure. You don’t need to sign up for a separate email delivery service yourself — the entire setup is driven from inside your GitHub issues using the /authenticate-domain and /verify-domain commands below.

Prerequisites

A Pro plan (upgrade)
A domain you own (e.g., yourcompany.com)
Access to your domain’s DNS settings
Scitor installed on your repository

Step 1: Authenticate your domain

Run the /authenticate-domain command in any issue or discussion managed by Scitor:

/authenticate-domain mail.yourcompany.com

Use a subdomain

We recommend authenticating a subdomain like mail.yourcompany.com rather than your root domain yourcompany.com. This keeps your existing email setup (Google Workspace, Microsoft 365, etc.) on the root domain untouched while letting Scitor send from the subdomain.

Scitor will respond with three CNAME DNS records you need to add to your domain. These provide DKIM signing and a branded return-path so your outbound emails authenticate correctly and pass spam filters.

Step 2: Add DNS records

Add the three CNAME records from Scitor’s response at your DNS provider (Cloudflare, Route 53, your domain registrar’s DNS panel, etc.). They will look something like:

Type     Host                                       Value
CNAME    em1234.mail.yourcompany.com                u12345678.wl.mail.scitor.io
CNAME    s1._domainkey.mail.yourcompany.com         s1.domainkey.u12345678.wl.mail.scitor.io
CNAME    s2._domainkey.mail.yourcompany.com         s2.domainkey.u12345678.wl.mail.scitor.io

DNS propagation

DNS changes typically propagate within a few minutes, but can occasionally take a few hours. There’s no need to wait — you can re-run /verify-domain until it succeeds.

Cloudflare proxy

If your DNS is on Cloudflare, make sure the proxy (orange cloud) is off for these records — they need to be DNS-only (grey cloud). CNAME records cannot be proxied.

Step 3: Verify your domain

Once you’ve added the DNS records, verify that everything is set up correctly:

/verify-domain

Scitor will check each record and tell you which (if any) haven’t propagated yet. Re-run the command after a few minutes if records are still missing.

Step 4: Set your sender address

Once the domain is verified, set your custom sender address:

/set-from-address support@mail.yourcompany.com "Acme Support"

This sets:

From email: support@mail.yourcompany.com
From name: Acme Support

The email address must use the verified domain (or a subdomain of it). If you verified mail.yourcompany.com, you can use any local part like support@, help@, hello@, etc.

Step 5: Test it

Reply to an existing customer issue with /send and check that the email arrives from your custom address with the correct display name.

Removing a custom domain

To remove your custom domain and revert to the default Scitor sender address:

/delete-domain

This resets the sender address to no-reply@mail.scitor.io and removes the domain from our email infrastructure.

Why authenticate?

Domain authentication (DKIM via CNAME records) ensures:

Your emails are delivered (not flagged as spam)
Recipients see your company name as the sender (not Scitor)
Email clients show a verified sender badge
Compliance with major mailbox providers (Gmail, Outlook, Yahoo) bulk-sender requirements

Related commands

Command	Description
`/authenticate-domain <domain>`	Set up custom email domain (Pro)
`/verify-domain`	Verify DNS records for custom domain
`/set-from-address <email> "<name>"`	Set custom from address (Pro)
`/delete-domain`	Remove custom email domain

Was this article helpful?