• US: +1-800-476-7226

Software and services for the radio industry.

Email Settings

Modified: 2017/06/07 10:49 by admin - Uncategorized

Email Settings

RT sends two types of emails: The first are emails that you, the person signed in, send out; and the second are emails that you are sending out on behalf of someone else. For the emails that are being sent out that are from you, this is where you specify the display name and the return address that will be part of the actual email sent out. This is the "default" email information that is included whenever the necessary information is not available when sending the emails out by proxy.

No matter what type of email(s) you are attempting to send, RT requires that you have the ability to send these email(s) through an internet email server through your internet service provider. We've modeled the RT email settings window so that it is very similar to several other popular email clients.

From the Dashboard, navigate to Settings > Email.

The Email settings window appears:


RadioTraffic requires the following:

  • Server address, which looks like mail.internetprovider.com, and
  • Port number, which is normally 25 for in-house servers, or 587 for Gmail. The port number could be different based on your service provider's settings.


Encrypted Connection

At this time, RadioTraffic supports standard SMTP communication with the server and SMTPS (SMTP connections secured by SSL).

To enable SMTPS, check "Use SSL encrypted connection." You will also most likely have to use a different port number than 25. Check with you service provider for the specific port number and requirement for SSL.


Logon Information

Most email servers require that you have a valid account in order to send through them in order to prevent email abuse. The User Name and Password in this section is the user name and password that your internet email provider requires in order for you to connect to their email server.


Test Account Settings

The Test Account Settings provides a simple mechanism that allows you to verify your email settings by sending a test message through your service provider. This is kind of a two step process. Pressing the button will attempt to send an email using the settings provided. You will get a success or fail message in either case.

If it failed, double check your settings. If it succeeded, this means that RT was able to connect to the server using the settings provided and the server accepted the email. Using your regular email client, you can further verify if the message was sent successfully.


The above message is what you are expecting to see if everything works as desired.


The above message (or something similar) will be seen if one or more of the settings you provided are not correct. As part of the overall message displayed, it is important to note the third sentence could include any of the following:

  • The SMTP server requires a secure connection or the client was not authenticated. The server response was: 5.7.1 Authentication required.

    This suggests that either your username and/or password are incorrect (authentication) or the server requires a "secure connection".

  • The SMTP server requires a secure connection or the client was not authenticated. The server response was: 5.7.57 SMTP; Client was not authenticated to send anonymous mail during MAIL FROM

    Double check that your credentials are correct, and try actually signing into the account. It has been found that this problem can occur when the password of the account has expired. When the password for the account has expired, this error will be received until the process of forced change of the account password when signing in is completed.

  • Mailbox name not allowed. The server response was: Sorry, that domain isn't in my list of allowed rcpthosts.

    Many email servers limit the ability to send email from an email address other than the one that they provided you. In this example, the rcpthosts "file" mentioned suggest that this is an email service hosted possibly on a Linux server. Contact your provider for details on how to get the email address you are using placed into this file.

  • Mailbox name not allowed. The server response was: From address not verified - see http://help.yahoo.com/l/us/yahoo/mail/original/manage/sendfrom-07.html.

    Many email servers limit the ability to send email from an email address other than the one that they provided you. If you want to use a different "from address", it may be necessary to use the tools provided to you by your email provider to configure the "from address" so that the server allows you to send accordingly. Try visiting the web address provided as part of the error message to see details which usually includes instructions for configuring this.

  • The remote name could not be resolved: 'smtp.server.com'.

    This suggests that whatever you've provided for the server address is not correct or, in some circumstances, a network problem with any point between your computer and the email server.

  • Unable to connect to the remote server.

    This is the most generic of possible error responses, but usually suggests that server address does represent a valid server on the internet, but the port number provided is not "listening". Verify the port number and try again. It is also possible that, in some circumstances, a network problem with any point between your computer and the email server.

  • Mailbox name not allowed. The server response was: sorry, that domain isn't allowed to be relayed thru this MTA (#5.7.1)

    This message seems to be commonly related to an anti-spam protection that your email server has in place on their network. This protection is called "POP-before-SMTP" and is "for your benefit". Due to this protection, it is supposedly not be possible for a spammer to use your mail server to relay their unwanted messages. You can still use the SMTP service that comes with your account. When sending mail you first have to login to your email server, this usually happens when you check for new messages. For a certain period of time after you check for mail, you are authorized to send email through your mail server. As soon as you receive the same error message - simply login again to your mail server (check your mailbox for new emails) and you will then be able to send again. In order to do this, you will need to use the email software you use for checking email as our product does not actually "read your emails" (POP3); we are only able to send emails (SMTP).

  • Mailbox unavailable. The server response was: 5.4.5 Daily sending quota exceeded. r12sm28442891ioe.43 -gsmtp

    Many email providers/servers configure their accounts to prevent "too much email" being sent during particular intervals. This is to prevent "spam" by limiting accounts to sending less than a specified amount of email per interval (such as daily). If you are expecting to send a lot of email, contact the people responsible for your email server and discuss the options for increasing your "quota".

  • Mailbox unavailable. The server response was: Please turn on SMTP Authentication in your mail client.

    This error clearly indicates that the server requires a "secure connection".



The three buttons located in the bottom right portion of the dialog allow you to commit or cancel any changes that you've made. Buttons are enabled/disabled depending on the current change state and/or validity of the changes.


Press the OK button to save your change(s) and close the dialog.


Press the Cancel button to abort any change(s) made and close the dialog.


Press the Apply button to save your change(s), keeping the dialog open for further review/change(s).


Additional Information




  • SMTP Server:smtp.gmail.com
  • Port: 587
  • Use SSL: Checked

Enable Access

In order to allow RT to communicate with http://gmail.com, you will need to allow RT access by doing the following:

Option A

  • Go to User Account Settings.
  • Go to the "Sign-in & security page.
  • Scroll all the way down the page till you see this:
  • Allow less secure apps: (Turn this ON)

Option B

Navigate to here and turn ON access for less secure apps. (This suggestion provided by one of our clients; so please review/proceed with caution.)

Option C

  • Log into https://gmail.com.
  • Navigate to Email Support.


  • Click "How to generate an App password."
  • Click the "App passwords" link in the first item.
  • https://gmail.com requires your password again. If you are using two-step verification, it will also require that code.
  • Once you are successfully logged in, you will see a list of Apps with permission to use the https://gmail.com account.


  • To add RT, navigate to the Select app drop-down and choose Other (Custom name) and type in a meaningful name to represent the RT service (ie. "RadioTraffic.com").
  • In the Select device drop-down, choose Windows Computer.
  • Click Generate.
  • This will take you to another page that will display a 16-character password. Write this down.
  • In the RT Email Setting window, enter this password, and click Test Account Settings button to make sure you completed the set up properly.



  • SMTP Server: smtp.live.com
  • Port: 587
  • Use SSL: Checked



  • SMTP Server: smtp-mail.outlook.com
  • Port: 587 (recommended) or 25
  • Use SSL: Checked



Office 365

  • SMTP Server: smtp.office365.com
  • Port: 587 (recommended) or 25
  • Use SSL: Checked

NOTE: The account being setup needs to also be enabled as one of the "Exchange Online" licenses. To verify this:

  • Log into the Office 365 admin center.
  • Navigate to USERS->Active Users.
  • Select the end user account, then click EDIT on the right panel.
  • Click Licenses, then click the drop-down icon after your Office 365 plan name.

    (The above instructions are from a Microsoft support question asked here.

Additional Information



  • SMTP Server: smtp.mail.yahoo.com
  • Port: 587
  • Use SSL: Checked



Many internet service providers (ISPs) and/or corporate firewalls disable (block) the ability to send emails using computer(s) on network(s) or domain(s) they do not control. Please check with your ISP and/or corporate IT personel regarding what these settings should be.