Skip to main content

Set up an alias or SMTP

How to Send lemlist Campaigns Using Gmail Aliases πŸ“§

Updated today

Learning Objective

By the end of this tutorial, you'll know how to set up email aliases (both Gmail and external SMTP providers), configure them in lemlist, and launch campaigns from multiple email identities while maintaining proper deliverability and reply tracking.

Why This Matters

Email aliases enable you to manage multiple professional identities from a single inbox, whether for different roles, brands, or campaign purposes. This flexibility allows you to personalize your outreach strategy, segment your campaigns by sender identity, and maintain separate professional personas without managing multiple email accounts. Users typically see 15-20% better response rates when using role-specific aliases that match their outreach context.

Prerequisites

Before starting this tutorial, make sure you have:

  • Connected your primary email account to lemlist (see Connect my email provider to lemlist)

  • Admin access to your email settings (Gmail, Outlook, or other provider)

  • Basic understanding of creating campaigns in lemlist (see Getting Started guides)

  • Verified your primary email's domain authentication (SPF, DKIM, DMARC recommended)

Core Lesson: Step-by-Step Workflow

Phase 1: Set Up Your Email Alias

Option A: Gmail Aliases Setup

Step 1: Access Gmail Settings

Go to Gmail β†’ Click the βš™οΈ gear icon β†’ "See all settings"

This opens your full Gmail configuration panel, where you can manage sending addresses.

Step 2: Add Your Alias Address

  1. Navigate to the "Accounts" tab

  2. Under "Send mail as," click "Add another email address"

  3. Enter the alias email address

  4. βœ… Important: Check the box "Treat as an alias"

  5. Click "Next step"

This tells Gmail to handle this address as an extension of your main account, maintaining unified inbox management.

Step 3: Verify Your Alias Gmail will send a verification email to the alias address. You must have access to this mailbox to confirm.

  1. Check the alias inbox for Gmail's verification email

  2. Click the verification link or enter the confirmation code

  3. Return to Gmail settings to confirm the alias appears under "Send mail as"

πŸ’‘ Tip: If verification fails, ensure you have proper access to the alias mailbox and that forwarding rules aren't blocking Gmail's verification email.

Option B: External SMTP Provider Setup (Outlook, Custom Domain, etc.)

Step 1: Enable SMTP/IMAP on Your Provider Before connecting to Gmail, ensure your email provider supports:

  • SMTP for sending (usually ports 465 or 587)

  • IMAP for receiving (usually port 993)

  • SSL/TLS encryption

Check your provider's documentation for specific server addresses and ports.

Step 2: Add External Email to Gmail

  1. In Gmail Settings β†’ "Accounts" tab β†’ "Send mail as"

  2. Click "Add another email address."

  3. Enter your external email address

  4. Uncheck "Treat as an alias" (for external providers)

  5. Click "Next step."

Step 3: Configure SMTP Settings

Enter your provider's SMTP details:

  • SMTP Server: mail.yourdomain.com (or provider-specific)

  • Port: 465 (SSL) or 587 (TLS)

  • Username: Your full email address

  • Password: Your email password (or app-specific password)

  • Secured connection: SSL or TLS (match your port)

Step 4: Complete Verification

Similar to Gmail aliases, you'll receive a verification email. Complete the verification to activate the alias.

⚠️ Google Workspace Users: If you see the error "You must send through outlook.com SMTP servers," your admin needs to enable "Allow per-user outbound gateways" in Google Workspace Admin β†’ Apps β†’ Google Workspace β†’ Settings for Gmail β†’ End User Access.

Phase 2: Configure Aliases in lemlist

Step 1: Access lemlist Email Settings

  1. Click your profile icon (bottom left corner) β†’ Settings

  2. Navigate to "Sending Settings"

  3. Find your connected email account

  4. Click the βš™οΈ Settings button next to your email

Step 2: Load and Verify Your Aliases

  1. Open the "Email address aliases" section

  2. Your verified aliases should appear automatically

  3. If aliases don't show:

    • Click "Refresh" to sync with Gmail

    • Wait 2-3 minutes for propagation

    • If still missing, disconnect and reconnect your Gmail account

Step 3: Enable IMAP for Reply Tracking

For proper reply detection with aliases:

  1. Ensure IMAP is enabled in your email provider

  2. Set up forwarding rules so replies to aliases reach your main inbox

  3. In lemlist, verify IMAP connection status shows as active

This ensures lemlist can track opens, clicks, and replies across all your aliases.

Phase 3: Launch Campaigns with Aliases

Step 1: Create or Open Your Campaign

Navigate to your campaign and go to the "Sequence" section where you design your outreach flow.

Step 2: Select Your Sending Alias

  1. In the Sequence editor, find the sender options (βš™οΈ icon)

  2. Click the dropdown to see all available aliases

  3. Select the appropriate alias for this campaign

  4. The selected alias will show as "Sending from: [[email protected]]"

Step 3: Personalize Based on Alias Identity Match your messaging to the selected alias persona:

  • Adjust the signature to match the alias role

  • Update sender name if needed

  • Ensure reply-to address matches the alias

  • Consider role-specific messaging angles

πŸ’‘ Example: If using [email protected], focus on value propositions. If using [email protected], emphasize collaboration opportunities.

Step 4: Test Before Launch

  1. Send a test email to yourself

  2. Verify the "From" field shows your alias

  3. Check that the replies route correctly

  4. Confirm tracking pixels work

Practical Application / Real-Life Example

Example: Multi-Department Outreach Strategy

Scenario: B2B software company using aliases for targeted outreach

Aliases Setup:

Campaign Performance:

  • Sales alias: 18% reply rate for product demos

  • Partnership alias: 24% reply rate for collaboration proposals

  • Events alias: 31% open rate for webinar invitations

Try It Yourself Checklist:

  • Create role-specific aliases (sales, support, partnerships)

  • Design unique signatures for each alias (manually)

  • Segment your prospects by the most relevant sender

Troubleshooting & Pitfalls

Issue: Aliases not appearing in lemlist

  • Root cause: Gmail sync delay or verification incomplete

  • Fix:

    • Verify the alias shows as confirmed in Gmail settings

    • Disconnect and reconnect Gmail in lemlist

    • Clear browser cache and refresh lemlist

Issue: Replies not tracked for alias emails

  • Root cause: IMAP not configured or forwarding rules missing

  • Fix:

    • Enable IMAP in your email provider settings

    • Set up forwarding from the alias to the main inbox

    • Verify IMAP credentials in lemlist settings

    • Check that forwarding preserves email headers

Issue: "Must send through provider's SMTP servers" error

  • Root cause: Google Workspace security restriction

  • Fix:

    • Contact your Google Workspace admin

    • Enable "Allow per-user outbound gateways."

    • Location: Admin console β†’ Apps β†’ Google Workspace β†’ Gmail settings

    • Alternative: Use auto-forwarding instead of SMTP

Issue: Daily sending limits unchanged with aliases

  • Root cause: Misunderstanding of alias functionality

  • Fix:

    • Remember: All aliases share your main account's sending quota

    • Gmail limit remains 100 emails/day total across all aliases

    • To increase volume, add separate email accounts, not aliases

Issue: Emails sent from the wrong alias

  • Root cause: Default sender not updated in campaign

  • Fix:

    • Always verify sender selection before launching

    • Check each sequence step if using multiple senders

    • Set campaign-level default sender in settings

Knowledge Check

Before launching your first campaign with aliases, confirm:

  • Can you explain why aliases don't increase your daily sending limit?

  • Did you verify that replies to your alias will be tracked properly?

  • Have you tested sending from each alias before going live?

  • Which personalization approach matches each alias's role?

  • Do you understand the difference between a Gmail alias and an external SMTP setup?

Did this answer your question?