SugarCRM SupportHelp ArticlesEmailConfiguring Your SMTP Server to Work With SugarCloud

Configuring Your SMTP Server to Work With SugarCloud


A lot of useful functionality (e.g., notifications, emails, campaigns) depends on Sugar being configured with an outbound email server (SMTP). Setting up an SMTP server in Sugar is as simple as navigating to Admin > Email Settings, choosing "SMTP" as the mail transfer agent, and entering the server information. A fully working setup, however, may require additional configuration on the email server. This article provides the list of appropriate IP addresses to add to your allowlist when configuring your outbound email server or LDAP authentication (for instances that use SugarIdentity). 

Note: If you are sending from Sugar through an Exchange server, ensure that you have configured your SMTP Exchange server to accept "Basic Authentication".

Restricted IPs

Outbound Email Server

Some email service providers restrict access to their servers to a predefined range of IP addresses. This means that the email server will only talk to a certain set of machines. You will need to speak with your system administrator, IT team, or email service provider to find out if access to your email server is restricted.

If your email server is restricted, you will need to determine which geographic location your instance is hosted in SugarCloud. Please refer to the Identifying Your SugarCloud Stack section of the Using the Case Portal article to confirm the geographic location. Once the location is confirmed, have the appropriate IP addresses added to your allowlist according to the following chart:

Note: These IP addresses only apply to instances hosted on the SugarCloud service.

SugarCloud Stack Location IP Addresses
SugarCloud AU
SugarCloud CA
SugarCloud DE
SugarCloud EU

SugarCloud SG
SugarCloud UK
SugarCloud US

Connections from your SugarCloud server will be made from these IP addresses. Please be aware that these IP addresses may change in the future.

LDAP Authentication

SugarIdentity can be configured to accept Lightweight Directory Access Protocol (LDAP) authentication if your organization has implemented LDAP or Active Directory authentication. If the Active Directory authentication server is behind a corporate firewall and your instance uses SugarIdentity, you need to make sure that the appropriate IP range is open on your firewall to allow communication with the Active Directory server. A rule will need to be created allowing the LDAP bi-directional communication for the necessary IP range. This can be the standard LDAP port 389 or you can use LDAP over SSL. Please add the appropriate IP addresses to your allowlist according to the following chart:

Cluster Region Outbound IP Addresses us-west-2 ap-southeast-2 eu-west-1 eu-central-1 ca-central-1 eu-west-2 ap-southeast-1


Error Messages

When encountering this issue for the outbound email server, your Sugar log is likely to show the following error message:

[FATAL] SMTP -> ERROR: Failed to connect to server. Code: 111 Reply: Connection refused

A similar message may be displayed with the error code of 1.1.0. The cause of both is the same: the outbound email server is not accepting the request coming from Sugar, usually because the server is restricted to accepting requests from only a certain range of IP Addresses. These messages are relayed from your SMTP server back to Sugar and can be viewed in the Sugar logs. For more information, please refer to the article Troubleshooting Outbound Email Using Sugar Logs.

Last modified: 2022-02-24 01:17:07