SMTP Providers

Using SendGrid As The SMTP Provider

This help article provides a guide for integrating SendGrid as your SMTP provider within the platform. It details the necessary configurations and settings to enable seamless email delivery through SendGrid. The article covers the technical steps required to properly configure SendGrid, ensuring optimal performance and reliability of your email communications. For any advanced troubleshooting or specific queries, please refer to the detailed instructions provided within the article.


Step 1: Sign up for SendGrid
Sign up for SendGrid


Step 2: Go to Location Settings in your account
Click on Email Services > Add Service > Select SendGrid from the dropdown.


If you want to integrate SendGrid for all locations, you can set this up in the general settings view.



Step 3: Get your SendGrid API



Click on Settings > API keys > create API Key.

  • Type an API Key Name.
  • Make sure API Key Permissions is set to Full Access.
  • Click Create & View.

  • Copy the highlighted API Key created.

Step 4: Add your API key to the platform

  • Username: apikey
  • Email: Your SendGrid login email
  • Password: Paste the highlighted copied API key here
    Click Save.


Step 5: Setup 2FA with SendGrid



Step 6: Verify SendGrid email account as a single sender



Create a sender with your SendGrid login email.


Step 7: Integrate again by clicking Save



Now you will see SendGrid as your SMTP provider in the platform.


If you are getting an error when you send a test email in the conversation, click the ⚠️(red triangle) icon to view more details about the error in the conversation.


Error Example:
550 The from address does not match a verified Sender Identity. Mail cannot be sent until this error is resolved.


Important: When you mask the sender email, make sure the sender email matches with the SMTP-integrated email, or ensure the sender email is verified with SendGrid.

Limitation of using SMTP when emails are not sending

If you are using the SMTP provider to send emails and they're not delivering most of the time, the reason is usually because the sender email doesn't match with the SMTP email that you've configured.



Once you set up your SMTP provider, if you are getting an error when you send a test email in the conversation, you can click the ⚠️(red triangle) icon to view more details about the error in the conversation.



For the error displayed in the conversation, the platform will fetch the error received from the SMTP provider and display it. If you are already sending from the SMTP-integrated email, please open a support ticket with the SMTP provider so they can provide the delivery status on the email.


Learn more about why you can't use a free email address as the SMTP.

Why Can't I use My Free Email Address As The SMTP?

If you're encountering issues using your free email address as the SMTP (Simple Mail Transfer Protocol) server for sending emails, you're not alone. Many users face challenges when setting up email services with free email providers due to various restrictions and limitations. This article provides a detailed overview of why free email addresses might not be suitable for SMTP and offers insights into alternative solutions.


Why You Need Your Own Domain To Send Email

You might be thinking, "Why do I need my own domain to send email? Can't I just use my @gmail address?"


All marketing emails should be sent from a domain you own, not from a personal account at a provider domain, like @gmail, @hotmail, @yahoo, etc., or in some cases an ISP email.


In almost all cases we've seen, those addresses can issue a block whenever bulk email is sent from their domain. This is because the most important factor in email deliverability is domain reputation, and when you send mail from a Gmail account, you're actually using Gmail's reputation, not your own.


NOTE: Even if your provider does not currently block email, it is very likely that all email providers will do so in the near future. The best way forward is to create an email address at a domain that you own, so you can start building up your own domain reputation!


Think of it this way

When you send something in the mail, a carrier (UPS, DHL, Post Office) transports it for you. But it's still coming from you, the carrier isn't just going to pick it up off the street (hopefully), and the recipient is more likely to accept a letter coming from someone they know.

Email is much the same. The platform is the carrier, but it also depends on your sending reputation, and the domain email is how you build that trust.


How to get started:

Three ways to add email to your domain and start sending emails with that address:


  1. Where you bought your domain

Almost all domain providers will be able to provide you with an option to add email to your purchase. Then you'll have the name@domain.com address you need, and even if you don't set up the Inbox entirely, you can still set up forwarding to your normal Gmail or Yahoo address. Examples are sites like Google Domains, Namecheap, and Hover.


  1. Where you host your website

Many people buy their domain from the same place they host their website. BlueHost, HostGator, and GoDaddy all offer both domains and hosting, so they are popular all-in-one options. Squarespace and Wix make it easy to add email to your account with options in your dashboard.

NOTE: For either option, the best way to find out how to do this is simply Google "website host and email account" with your host/provider in the search bar.


  1. Google Workspace

Did you know you can still use Gmail with your domain email? It's true! You can use Google Workspace to manage your domain email address, plus Google Docs, Sheets, and more! Click here to sign up and get started. Plans begin at $6/month.

Using Zoho as your SMTP Provider

Configuring Zoho as Your SMTP Provider 


This article provides a step-by-step guide for integrating Zoho Mail as your SMTP provider within the platform. SMTP (Simple Mail Transfer Protocol) is essential for sending emails reliably from your account, and using Zoho's SMTP server can help ensure smooth email delivery. In this guide, you'll find detailed instructions on setting up Zoho as your SMTP provider, including configuration settings and troubleshooting tips. Whether you're setting up Zoho for the first time or need to adjust your current settings, this guide will help you achieve seamless email communication through the platform.


Outgoing Server Settings for Personal Email Users (Personal users with an email address, username@zoho.com):

  • Outgoing Server Name: smtp.zoho.com
  • Port: 465 with SSL or Port: 587 with TLS
  • Require Authentication: Yes


Learn more about why you can't use a free email address as the SMTP.


Outgoing Server Settings for Organizations with domain-based email (Organization users with a domain-based email address, you@yourdomain.com):

  • Outgoing Server Name: smtppro.zoho.com

  • Port: 465 with SSL or Port: 587 with TLS

  • Require Authentication: Yes

  • User Name: Enter your Zoho username or your complete Zoho Mail address. If your domain is hosted with Zoho, then your email address will be in the format you@yourdomain.com.

  • Email Address: Enter your Zoho Mail address. If your domain is hosted with Zoho, then your email address will be in the format you@yourdomain.com.

  • Password: Enter your Zoho account password. (You might require an application-specific password if Two-factor Authentication is enabled).

Using Google/Gmail/Google Workspace as your SMTP Provider

This comprehensive guide walks you through creating app-specific account passwords with 2-step verification, focusing on Gmail SMTP integration. It is particularly useful for users in the Philippines who face connection difficulties.


Please Note:

Please use a VPN when trying to connect to Gmail SMTP for Users in the Philippines

 

  1. Go to Google.com.

  2. Click on your icon on the top right.

  3. Make sure you choose the correct Google Account that you want to integrate with.

  4. Click on Manage your Google Account.

  5. Click on Security.

  6. Scroll down further to locate the section Signing in to Google.

    Make sure 2-step verification is enabled. You must turn on 2-step verification to see the App Passwords option.

    If 2-step verification is missing, the option to allow users to turn on 2-step verification is off in Google Admin. Please contact the Google Workspace admin to follow this article to enable the option.

  7. Once 2-step verification is enabled, click on App passwords.

    Make sure the right email is selected from the dropdown. Type the password and click on Next.

  8. Scroll down to find App Passwords >.

  9. Type an App Name, e.g., SMTP integration > Click on Create.

  10. Drag to copy the app password and paste it as the password when integrating Gmail SMTP.

  11. On the top left:

    • A. Search for your account if you want to integrate Gmail SMTP for a location.
    • B. Switch to your account view if you want to integrate Gmail SMTP across all locations in settings.
  12. A. Search for your account if you want to integrate Gmail SMTP for a location.

    Once you are in your account 
    Click on Settings at the bottom left.


  13. Scroll further on the sidebar menu to click on Email Services.

  14. Click on Add Service on the top right.

  15. Click on the dropdown to select the provider > Select Gmail.

    Paste the copied App Password that we generated just now in the Password field.

  16. Enter your Gmail login email and click Save; done!

How to enable 2-step verification:

  1. Go to Google.com.

  2. Click on the 9 dots menu here on the top right.

  3. Scroll down to click on Admin.

    Go to the Main menu on the top left, click on Security > Authentication > 2-step verification.

    Ensure the option to Allow users to turn on 2-Step Verification is enabled.

    Refresh the Manage your Google account page to see if 2-Step Verification shows up now.



FAQs:

  • Q: What is the benefit of using an app-specific password for Gmail SMTP integration?
    • A: An app-specific password provides an additional layer of security and allows the app to access your Gmail account without you needing to input your password each time.
  • Q: What is the significance of 2-step verification in the context of Gmail SMTP integration?
    • A: 2-step verification provides extra security to your account. When you set up an app-specific password, Google requires that you have 2-step verification enabled to ensure your account is protected.
  • Q: Why is it recommended to use a VPN while connecting to Gmail SMTP users in the Philippines?
    • A: A VPN can help bypass regional restrictions and add an extra layer of security when connecting to Gmail SMTP. It might be particularly beneficial for users in certain regions like the Philippines.
  • Q: Can I use the same app-specific password for multiple applications?
    • A: No, Google recommends creating a unique app-specific password for each application to enhance your account's security.
  • Q: What should I do if the 2-step verification option is not showing up on my Google account?
    • A: If the 2-step verification option is not appearing, it could mean the feature is turned off in your Google Admin settings. You would need to contact your Google Workspace admin to enable the option.
  • Q: I have enabled 2-step verification and created an app-specific password, but my integration still isn't working. What can I do?
    • A: Ensure you have entered the app-specific password correctly during integration. If you're still having issues, it's best to contact Gmail support.
  • Q: Can I still use my regular Gmail password once I've set up an app-specific password?
    • A: Yes, you can. An app-specific password does not replace your regular password but is used for specific apps to access your Gmail account.

Setting Up SMTP Providers

We have direct integrations with both Google and Outlook, if you're sending through these providers please use those integrations not SMTP.

We also have built in bulk sending using LC Email as well.

If you choose to use SMTP you do so at your own discretion, while we offer support it will be done on a best effort basis. SMTP is considered an advanced use case for experts and not how most people should be sending email through support.

A List of SMTP and IMAP Server: 
https://www.arclab.com/en/kb/email/list-of-smtp-and-imap-servers-mailserver-list.html 


Sender Email Address Configuration Limitation when Using Your Own SMTP Provider:

If you are using an SMTP provider, make sure the sender email you mask here matches the email you integrated with. If the sender's email does not match with the SMTP integrated email, or if the sender's email is not verified with your SMTP provider, it will fail to deliver.


To test if the integrated SMTP integration works: 


When sending an email, we will need to update the sender's email address so it matches the integrated SMTP email.


In manual conversation, the sender email is set to be the user login email. We will need to set the email below to match the SMTP integrated email. By default, it will show your login email here:


Daily limits on how many emails can be sent: 

Your SMTP provider may have daily limits on how many emails can be sent. Gmail, for example, has a limit of approximately 100-150 emails per day when connected to the server from a remote email client.


Workflow/Email Statistics

We will not be able to fetch delivered/bounced stats to display them. SMTP integration will show opened and clicked only. We highly recommend setting up Mailgun or LC Email to show statistics. 



Common issues when setting up SMTP providers:

  1. Make sure Email Re-Billing is disabled while we make changes to the default provider
  2. Please try to use the gmass tool with the same input and see if that works: https://www.gmass.co/smtp-test  



Help docs on setting up SMTP providers:

  • Google: Using Google/Gmail/GSuite as your SMTP Provider

            Setting alias for Google SMTP

  • Yahoo: Yahoo temporarily disabled their SMTP and there's no ETA on when it will be available again.
  • Sendgrid: Using SendGrid As The SMTP Provider
  • Zoho: Using Zoho as your SMTP Provider



In regard to setting up Amazon SES:

  • Use the correct server name listed on the SMTP Settings page

  • Use port 465

  • Use the IAM Username & Password you created (and hopefully saved because you can't view it again)

  • Use the Amazon AWS Root User Email Address


Amazon SES Quick Start: 

https://docs.aws.amazon.com/ses/latest/DeveloperGuide/quick-start.html 

Managing Your Amazon SES Sending Quotas: 

https://docs.aws.amazon.com/ses/latest/DeveloperGuide/manage-sending-quotas.html

Moving Out of the Amazon SES Sandbox: 

https://docs.aws.amazon.com/ses/latest/DeveloperGuide/request-production-access.html 


In regard to setting up Outlook / Microsoft Office 365:


It is common to get the error "Authentication unsuccessful" even though the two-step verification is OFF. Microsoft changed its security. Now a third-party app requires SMTP Authentication to be enabled. Here is the guide to enabling SMTP > https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-microsoft-365-or-office-365 


If the above article is not helpful, please reach out to Outlook support to get the account authenticated.



FAQs:

Q: The "Add Service" button is missing in the Email Services > SMTP services tab, how do I fix this? 

    A: Switch to your account View > your accounts > Click on the three dots > Manage Client


Click on Advanced Settings > Make sure the "Disable the Add Email Service button in the account Email Services Settings" is off.


Q: How many SMTP service providers can we have on an account? 

    A: An account can have multiple SMTP service providers. However, the same SMTP credentials                 cannot be added more than once, so using the same email ID with different integrations is not             allowed. Additionally, the same provider (e.g., Gmail) cannot be added twice.