Out of the box, you can start sending emails to your customers straight away using discussions – no need to configure servers or sign up for third party email services.

We use our own email servers to handle discussion message delivery.

Our team of experts continually monitor the health and performance of our servers to help make sure that your emails reach their destination.
We’re considered a trustworthy sender, with our own dedicated mail sending IP address and a very high email delivery rate.
Where there’s a problem sending an email, we add a comment to the discussion thread to let you know what went wrong.
We support email open tracking, so we can let you know how many times your email was opened.

Because we handle sending discussions using our servers, emails come from the address notifications@app.current-rms.com. They always show your user name as the sender.

Use your own servers

If you like, you may change this so that Current RMS uses your company’s email servers to send messages. This means that the emails can come from your company’s domain. For example, if your website is abcpartyrentals.com, discussions could come from hello@abcpartyrentals.com.

In order to make this change, you’ll need to be comfortable managing your company email server settings. Setting up or troubleshooting email server settings is beyond the scope of our support service. If you’re not sure, we recommend that you use our email servers.

Keep in mind

When you use your own servers:

we can’t troubleshoot where messages don’t go through,
we don’t get notified about problems, and
we can’t track opens.

You’re responsible for making sure that your email servers are up and running. If there’s a problem with them, your discussions might not go through. You can always switch back to sending discussions using Current RMS in System Preferences.

G Suite users (Gmail)

If you use Gmail for your work email as part of G Suite (previously Google Apps) then you can set up an SMTP relay.

Before you begin

You must be on a paid plan, not the legacy free plan.
You must use two-factor authentication on your Google account.

A note on less secure apps

Google considers any service that doesn’t include a “Sign in with Google” option as a ‘less secure app.’ We offer “Sign in with Google” as an option to sign in to your Current RMS account, but it doesn’t affect email server settings.

Email servers are configured a little differently. We have to supply a username and password.

To protect your security, we don’t ask for your actual Google password. Instead, we use a one-time app password that you may revoke at any time. When sending emails, we also use SMTP authentication and TLS encryption.

Let users manage less secure apps

Go to your G Suite admin console. From there, go to Security > Less Secure Apps.

Check “Allow users to manage their access to less secure apps” and click Save.

It may take up to 24 hours for your security settings to apply, but in our experience it usually takes about 10 minutes.

Set up SMTP relay

Head back to the homepage for your G Suite admin console. From there, go to Apps > G Suite > Gmail.

Choose Advanced Settings, then find "SMTP relay service" in the list and click Configure.

In the SMTP relay service settings window in G Suite:

Enter a description at the top, e.g. “Send discussion emails from Current RMS.”
Choose “Only addresses in my domains” from the Allowed Senders dropdown box.
Check the “Require SMTP authentication” box.
Check the “Require TLS encryption” box.
Click Add Setting on the SMTP relay box.
When you’re all done, click Save at the bottom of the Advanced Settings screen.

It may take up to 24 hours for your SMTP relay settings to apply, but in our experience it usually takes about 10 minutes.

On your Google security settings page:

Make sure you’ve enabled two-factor authentication.
Click App passwords.
On the next screen, choose “Other” from the drop-down and enter “Current RMS email”.
When you're done, click Generate.
Copy this app password and keep it safe. You’ll need it for the next step.

In your Current RMS system:

Go to System Preferences, then scroll down to “Email Settings.”
Select “Custom” from the Email Service dropdown box.
Enter smtp-relay.gmail.com and 587 as the SMTP sever and SMTP port.
Choose “Login” from the SMTP Authentication Type box.
Enter your Google Account email address as the SMTP user name.
Paste your app password as the SMTP password.
When you're done, click the Send Test Email button.

You may receive a security notification email from Google saying there was a new login that you need to confirm. If this is the case, check the email and confirm if you’re happy. Then, send another test email.

Office 365 users

If you use Microsoft Outlook as part of Office 365, Microsoft 365, or Exchange Online then you can set up an SMTP AUTH client submission.

Before you begin

Microsoft imposes sending limits on their SMTP service. This is set at 30 emails per minute and a maximum of 10,000 recipients per 24 hours.
You may only send emails from your mailbox’s email address. All discussion emails from Current RMS will come from this address.

In your Current RMS system:

Go to System Setup, then scroll down to “Email Settings.”
Select “Custom” from the Email Service dropdown box.
Toggle “Send from default address” to YES.
Enter your mailbox email address as the default from address.
Enter smtp.office365.com and 587 as the SMTP sever and SMTP port.
Choose “Login” from the SMTP Authentication Type box.
Enter your Microsoft Account email address as the SMTP user name.
Enter your Microsoft Account password or a generated app password if you use two-factor authentication.
When you're done, click the Send Test Email button.

Other email providers

There are lots of email service providers available, so we can’t provide instructions for all of them.

Look for SMTP server settings on your email service provider’s settings page to get server names, ports, and authentication information.

When you have that information, head to System Preferences and enter it under the “Email Settings” heading.

You might wish to check your email provider’s knowledge base or guides for more information, or chat with a member of their support team if you’re not sure.

Test email

If all goes well, you should receive an email to let you know.

If the test email fails, we’ll send an email using our email servers to let you know. In most cases, we can let you know the problem so you can troubleshoot. Some email servers don’t supply this information, so we can’t pass it on.

How do people reply?

Emails sent will come from your domain and SMTP servers. However, the reply-to address is still a Current RMS email address that’s unique to that particular discussion.

When a discussion recipient clicks reply, email apps use the reply-to address so the reply will come into the right place in Current RMS as normal.

If you’re a participant in the discussion, we’ll send you a copy of the reply.

What if there’s a problem?

Where we’ve tried to send an email via your email server and it fails, we’ll keep trying in intervals until we get through.

Where an email fails the first four attempts, we’ll send you an email to let you know that we’ll try again in an hour.

Remember we don’t have access your email servers, so we can’t help troubleshoot. If you’re not sure, switch back over to our email servers in System Preferences.

Common questions

Will this work with my email provider?

SMTP is a standard, open protocol for sending emails so it should be widely compatible. We recommend reaching out to your email provider’s support team for more information.

Why didn't a customer get my email?

If you’re using your own email servers, we route all discussion emails via your servers. This means that we can’t check on the status of a message from our side like we can when you use our servers.

Check your email server logs to see the status of any emails sent. If you’re not sure, talk to your email provider’s support team.