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.
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.