Skip to main content

How can I resolve email connectivity issues on lemlist and ensure a stable connection?

How to Troubleshoot Email Connectivity Issues on lemlist

Updated this week

Ensuring stable email connectivity is crucial for effective campaign management on lemlist. This guide outlines general troubleshooting steps, provider-specific scenarios, and key considerations to address common issues effectively.

Email connectivity issues may arise due to incorrect configurations, authentication errors, or limitations set by your email provider. This guide provides step-by-step solutions for resolving issues and maintaining a stable connection with lemlist.


General Troubleshooting:

1. Verify SMTP/IMAP Configuration

Incorrect SMTP or IMAP settings often cause connection errors. Double-check the following:

  • SMTP Settings: Ensure the SMTP host and port match those provided by your email service. SSL/TLS must be enabled.

  • IMAP Settings: Verify IMAP host and port for receiving emails align with provider configurations.

  • Authentication Credentials: Confirm email address and password entered are correct and consistent between SMTP and IMAP.

2. Enable Necessary Email Permissions

Your email provider might restrict outgoing emails. Ensure permissions allow third-party tool access to send emails.

3. Rule Out Connectivity Blocks

Check local network settings, firewalls, or email providers that may block SMTP/IMAP connections due to security policies. Clear your browser cache and cookies, and ensure the latest browser version is used.

4. Manage and Test Connections

Relink your email provider:

  1. Unlink the provider in SETTINGS β†’ SENDING SETTINGS β†’ Trash icon. (Pauses campaigns temporarily.)

  2. Reconnect the provider with updated settings.

  3. Test the newly saved connection to confirm functionality.


Common Error Troubleshooting

1. 'Invalid Grant' Authentication Errors

This error arises due to expired OAuth tokens or revoked permissions between Gmail and lemlist. Steps to resolve:

  1. Deactivate the email in SETTINGS β†’ SENDING SETTINGS β†’ Trash icon. This action pauses associated campaigns.

  2. Reactivate the email following deactivation.

2. Connection Timeout

Resolve by verifying:

  • No IP restrictions prevent your email service from connecting to lemlist servers.

  • Host and port configurations are correct with SSL encryption enabled.

  • Confirm temporary server-side outages with your email provider.


Provider-Specific Guidance

1. Zoho Mail

For a stable connection with Zoho Mail:

  • Enable IMAP: SETTINGS β†’ Email Accounts β†’ Configure IMAP β†’ Check IMAP Access.

  • Use prescribed IMAP and SMTP server details: - IMAP: imappro.zoho.com (Port: 993) - SMTP: smtp.zoho.com (Port: 465)

  • Generate an app-specific password if using Two-Factor Authentication (2FA).

2. Lark

For Lark-specific connectivity issues:

  • Manually enter the correct settings into the IMAP/SMTP fields. Avoid copy-pasting.

  • Enable all required fields, ensure SSL encryption, and fill configuration fields accurately.

  • Confirm the validity of account credentials directly on the Lark settings.


Google vs. SMTP Providers

1. Benefits of Google Authentication:

  • Seamless OAuth Integration simplifies email setup.

  • Higher deliverability and built-in authentication tools (SPF, DKIM, DMARC).

2. SMTP Pros:

  • Compatible with any third-party service provider.

  • Requires manually-defined settings but supports broader compatibility.

  • Ideal non-Google email alternatives when Gmail is unavailable.


Advanced FAQs

Incompatible Providers:

SMTP Providers Not Supported by lemlist
Unfortunately, the following SMTP providers are not compatible with lemlist:

  • SendGrid

  • Mailgun

  • Sendinblue

  • Mailjet

  • O2switch

  • Amazon SES

  • Postmark

  • Cloudmark

  • HostGator

If you’re using one of these providers, you’ll need to choose a different email provider.

Connection Check

If your emails connect via SMTP/IMAP, ensure proper hostname/port mappings and valid provider support for protocol connections.

Did this answer your question?