Setting Up SMTP Relaying in Rocketship

Setting Up SMTP Relaying in Rocketship

By default, Rocketship sends emails from our domain, using your helpdesk email as the Reply-To. Some customer email servers flag this as spam. If you see deliverability issues, you should enable SMTP Relaying.

How It Works

When you enable SMTP Relaying, Rocketship will send emails through your own email server (or a third-party service), not ours. This improves deliverability and ensures emails come directly from your domain.

Important:
SMTP Relaying is disabled by default. You must set it up manually if you want to use it.

Where to Configure It

Go to:
Admin Portal → Account → SMTP Relay

You will need to provide:

  • SMTP Host (e.g., smtp.mailgun.org)
  • SMTP Port (usually 587)
  • Username
  • Password
  • Encryption Type (TLS recommended)

What Providers You Can Use

You can either:

  • Use a third-party SMTP provider like:
    • Mailgun
    • SendGrid
    • Postmark
    • SMTP2GO

We recommend using third-party providers because they are usually easier to configure, cheaper at low volumes, and offer better tracking and logging.

Notes

  • Third-party providers usually require you to verify your domain before you can send emails.
  • Rocketship will immediately begin using your SMTP Relay settings once you save them.

Logging and Reports

You can view your Mail Logs via Reports -> Mail Log.

    • Related Articles

    • Handling Errors in Rocketship: Best Practices

      Rocketship can occasionally encounter errors across various modules like dispatching, scheduling, or appointment booking. Catching and resolving these quickly is essential, and Rocketship provides built-in workflows to help. Example Error Scenario In ...

    • Can I migrate my Rocketship Settings to a new tenant?

      Unfortunately, no, you can’t migrate from one tenant to another. To understand why, consider that we integrate with Autotask, and link to various Autotask entities and picklist items. When considering two Autotask tenants, the probability that the ...

    • Restricting Access to Rocketship

      You may not want all of your team to have access to Rocketship. For example, perhaps you have a dedicated sales or accounting employee that does not schedule, or get scheduled, via the helpdesk. In Rocketship, access to screens and features is ...

    • Rocketship Background Jobs Schedule

      This KB documents the frequency of jobs that we run in the background. Autotask Synchronization This section highlights how often we synchronization with any changes made directly in Autotask (i.e., not in Rocketship). You can force a synchronization ...

    • Troubleshooting Autotask Connections in Rocketship

      This article describes steps to take when the Autotask API connection fails. You will be alerted to Autotask API connections via Rocketship Admin, the Autotask Ticket Insights, and the WorkBoard when we are experiencing issues with your Autotask API ...