8 Email Setup

RStudio Connect has a number of features that depend on sending emails. Some examples include delivering content via email, sending administrative notifications, reporting job failures or even additional security.

Note: Versions of RStudio Connect before 1.7.4 allowed the email settings to be configured via the dashboard interface. These email settings were moved to a migration file and they should be transferred to your configuration file at your earliest convenience. See more about configuration migration in appendix section A.2.

8.1 Post-install behavior

RStudio Connect installs with all email features disabled until an email provider is configured properly. Specifically, this is what to expect:

  • Built-in password authentication will not be able to send emails to users with new account confirmation or password reset links. An administrator will be responsible for obtaining these links from the user profile page in the dashboard and pass them along to the user via other means.
  • Notifications such as licensing limits, user requests for more privileges, or content errors will only be written to the logs.
  • Content delivery via email will be disabled.

8.2 Configuring an email provider

RStudio Connect supports two options for sending emails: smtp or sendmail. These options can be configured via the setting Server.EmailProvider.

  • Sendmail is a mechanism for sending emails using the existing setup of the Linux installation that hosts RStudio Connect. Different Linux distributions have their own implementation compatible with Sendmail. Refer to your server’s documentation to configure it.
  • SMTP allows RStudio Connect to establish a direct connection to an email server for sending emails. In the RStudio Connect configuration file, you must provide the host and port of your SMTP server, user credentials if this server requires authentication, indication of whether the connection will be encrypted, and what encryption method will be used. All these options are described in the appendix section A.4. Please note that the SMTP settings are reloadable. This means that RStudio Connect does not need to be restarted to use new settings. See more about reloadable settings in appendix section A.1.4.

Note: The SMTP.Password can be encrypted to avoid credential leakage. See the appendix section A.1.3 for details.

8.2.1 Testing the email settings

You can see and test your current email settings from the RStudio Connect dashboard in the Admin>Settings panel. By sending a test email from this page you can confirm that the email features will work properly.

8.3 Configuring other email settings

There are a few other settings that should be configured in order to send emails from RStudio Connect.

It is expected that emails sent from RStudio Connect come from a known email address within your organization. This address must be configured using Server.SenderEmail.

Emails sent from RStudio Connect will be prefixed with “[RStudio Connect].” If you wish to change this prefix use the setting Server.EmailSubjectPrefix.

When delivering content via email, initially there will be no option to send to all users. If there is need to do so, please enable that by using the setting Server.MailAll.

By default RStudio Connect will send emails to recipients as BCC (blind carbon copy) so recipients will not have knowledge of each others’ email addresses. In some situations the email provider of the recipients will detect that a number of users received a BBC copy of the same email and that will trigger the spam detection. If you see this behavior, the setting Server.EmailTo should be configured with a “no-reply” email address from your organization.

Note: If you need additional privacy of the email addresses within your own organization, the setting Server.HideEmailAddresses can be used to to hide all email addresses in the dashboard. Users will not be able to see each others’ emails. Only administrators will be allowed to see all emails.

License-related emails can be configured using the settings from the Licensing section of the configuration file. See appendix section A.8 for details.