Email Setup

Connect your support email to GitHub in minutes. Set up forwarding so incoming emails become Issues automatically, and configure a custom sender address so replies come from your company.

How email flows

Inbound:  customer → your support address → forwarding → Scitor → GitHub Issue
Outbound: /send comment → Scitor → email provider → customer

Tip

Customers should reply using the Reply-To address on the ticket email, not the visible “From” address. See I replied to a ticket email but nothing appeared on the issue.

Each repository gets a unique email address like abc123@parse.scitor.io. Emails sent to this address are processed and converted into GitHub Issues or Discussions.

Setting up email forwarding

Google Workspace (Gmail)

  1. Open Gmail settings → Forwarding
  2. Click Add a forwarding address
  3. Enter your Scitor email address (e.g. abc123@parse.scitor.io)
  4. Click Proceed → Google sends a confirmation email to your Scitor address
  5. The confirmation email appears in your repository as a new issue — open it and click the confirmation link (or copy the code into Gmail)
  6. Select Forward a copy of incoming mail to and choose your Scitor address
  7. Choose what to do with the Gmail copy (recommended: keep Gmail’s copy in the Inbox so you have a backup)
  8. Click Save Changes

Forwarding specific addresses only

If you only want to forward emails sent to support@yourcompany.com (not all inbox mail), use a Gmail filter instead: go to Filters and Blocked Addresses → Create a new filter → set the To field to your support address → Forward it to your Scitor email.

Microsoft 365 / Outlook

Option A — Mailbox forwarding (simplest):

  1. Open the Microsoft 365 admin center
  2. Go to Users → Active users → select the support mailbox
  3. Click Mail → Email forwarding
  4. Enable Forward all email sent to this mailbox
  5. Enter your Scitor email address
  6. Check Keep a copy of forwarded email (recommended)
  7. Click Save

Option B — Mail flow rule (more control):

  1. Open the Exchange admin center
  2. Go to Mail flow → Rules → Add a rule → Create a new rule
  3. Name the rule (e.g. “Forward to Scitor”)
  4. Under Apply this rule if, select The recipient is → choose your support mailbox
  5. Under Do the following, select Redirect the message to → enter your Scitor email address
  6. Click Save

Fastmail

  1. Open Fastmail Settings → Rules
  2. Click New rule
  3. Set the condition: To/CC → contains → your support address (e.g. support@yourcompany.com)
  4. Under Then, select Forward to and enter your Scitor email address
  5. Optionally check Continue processing other rules if you want Fastmail to also file the email
  6. Click Save

Tip

Fastmail can also forward all mail for an entire domain. Go to Settings → Domains → select your domain → Set up forwarding and add your Scitor email address.

Zoho Mail

  1. Open Zoho Mail settings → Forwarding and POP/IMAP
  2. Click Add email address under the Forwarding section
  3. Enter your Scitor email address and click Verify
  4. The verification email appears in your repository as a new issue — use the link or code in it to confirm
  5. Once verified, select the address and choose whether to forward all email or only specific email
  6. Click Save

For filtering specific addresses, go to Settings → Filters and create a rule that matches your support address, then set the action to Forward to your Scitor email.

Proton Mail

  1. Open Proton Mail Settings and go to the email forwarding section (guide)
  2. Add a forwarding rule with your Scitor email address as the destination
  3. Click Send confirmation email
  4. The forwarding invitation appears in your repository as a new issue — open it and follow the link to accept
  5. Once accepted, forwarding is active

Other providers

Most email providers support forwarding. Look for any of these in your provider’s admin panel or settings:

  • “Forwarding rules” or “Email forwarding”
  • “Mail routing” or “Mail flow rules”
  • “Filters” with a “Forward to” action

The key requirement: forward incoming email to your Scitor email address (shown at the top of your repository’s Scitor settings). Scitor handles everything from there.

Confirmation emails

Many providers send a confirmation email to the forwarding address before they start forwarding. It arrives in your repository as a new issue (labelled auto-generated when the provider marks it as automated, even if you’ve set inbound.auto_generated: drop), so you can open it and click the confirmation link. Close the issue once forwarding is confirmed. If the confirmation doesn’t show up within a few minutes, contact us and we’ll retrieve it for you.

Custom sender address

By default, outbound emails are sent from no-reply@mail.scitor.io. You can customize this with the /set-from-address command:

/set-from-address support@yourcompany.com "Your Company Support"

Domain verification required

To use a custom sender address with your own domain, you need to authenticate the domain first via /authenticate-domain. Without authentication, you can only use @mail.scitor.io addresses.

See the Custom Email Domain guide for the full setup — it’s a few DNS records and takes minutes. You do not need a separate email delivery service account; Scitor handles sending for you.

Reply threading

Scitor automatically threads email conversations so everything stays connected:

  • New email → Creates a new Issue or Discussion
  • Customer replies → Added as a comment to the existing Issue or Discussion
  • You reply with /send → Sent as email, customer can reply back

When the customer hits “Reply” in their email client, their response is automatically linked to the right issue — keeping the full conversation in one place.

Attachments

Scitor handles email attachments automatically:

  • Attachments are uploaded and linked in the issue body
  • Inline images (embedded in HTML) are preserved
  • File size limits follow your email provider’s limits (typically 25MB per email)

Was this article helpful?

Scitor — Turn GitHub into your support platform