Pepipost  Integraiotn + Drupl Logo

Developer : Pepipost

Last updated : 26-05-2016

SugarCRM and Pepipost integration is fast and easy!

Setting up an SMTP server in SugarCRM is super simple! Just navigate to Admin > Email Settings, choosing “SMTP” as the mail transfer agent, and enter the server information. If you’re a Pepipost and a SugarCRM customer, let’s get into the details!

Step 1
To send emails from SugarCRM using Pepipost, use the SMTP Authentication Support module.

Companies looking to integrate SugarCRM with Pepipost to deliver their email marketing campaigns requires just a few settings changes within their SugarCRM account. Just navigate to the following on the SugarCRM site: Admin > Email Settings.

Note: you must be an administrator to make these changes on SugarCRM.


Step 2
Choose “Other” as the Email provider > Enter required server info as follows:
SMTP Hostname: ssl:// or tls://
SMTP Username: [your Pepipost account’s username]
SMTP Password: [your Pepipost account’s password]
SMTP Port: [25, 2525, 587 or 465. We recommend port 587 to avoid any rate limiting that your server host may apply.]


Note: Before sending a test/live email, your domain needs to be verified and approved by Pepipost. You may not use a free email account to do testing.


Once these changes have been made on the Email Settings page in your SugarCRM account, all outgoing mail from the application will be routed to Pepipost. At that point, we take over and deliver your email.

SugarCRM outlines this process in more detail in the SugarCRM support documentation, including some additional information on IP address restrictions, email throttling and restricted From: addresses. Find out more on the SugarCRM support site.

Ready to get started?

Get started with up to 30,000 emails/month free!

Pepi thinking

Start typing and press Enter to searchi

Fill out your information below, and we will send you a PepiAlert, that will describe your domain’s email deliverability situation. Please note that your email address must match the domain, or the domain must be owned by the company matching the email address. We have the right to refuse the request, if we can’t verify the information.

*All fields are required