SMTP (Simple Mail Transfer Protocol) is a universal email protocol that allows you to connect email providers not directly supported by Eve—essentially any provider that isn't Gmail or Outlook.
Use SMTP integration when:
You use a custom email domain hosted by providers like GoDaddy, Bluehost, Zoho, Namecheap, or other hosting services
Your company uses a proprietary or less common email system
You have specific email infrastructure requirements not met by Gmail or Outlook
Your organization doesn't allow OAuth connections but permits SMTP
You're using an email service provider (ESP) that doesn't have direct integration
Before connecting via SMTP, gather these details from your email provider (found in their support documentation):
Essential SMTP Settings:
SMTP Host/Server: The server address (e.g., smtp.yourprovider.com)
Port Number: Typically 587, 465, or 25
Username: Usually your full email address
Password: Your email account password or an app-specific password
Authentication Method: Typically SSL/TLS or STARTTLS
Encryption: Whether SSL or TLS is required
Here are typical settings for popular email providers:
Gmail (if not using OAuth):
SMTP Host: smtp.gmail.com
Port: 587 (TLS) or 465 (SSL)
Username: Your full Gmail address
Password: App Password (if 2FA is enabled)
Authentication: SSL/TLS or STARTTLS
Outlook/Office 365 (if not using OAuth):
SMTP Host: smtp.office365.com
Port: 587
Username: Your full email address
Password: Your account password
Authentication: STARTTLS
Yahoo Mail:
SMTP Host: smtp.mail.yahoo.com
Port: 465 (SSL) or 587 (TLS)
Username: Your full Yahoo email address
Password: App Password (if 2FA enabled)
Authentication: SSL/TLS
GoDaddy:
SMTP Host: smtp.secureserver.net (or smtpout.secureserver.net)
Port: 465 (SSL) or 587 (TLS)
Username: Your full email address
Password: Your email password
Authentication: SSL/TLS
Zoho Mail:
SMTP Host: smtp.zoho.com
Port: 465 (SSL) or 587 (TLS)
Username: Your full Zoho email address
Password: Your password or app-specific password
Authentication: SSL/TLS
Namecheap:
SMTP Host: mail.privateemail.com
Port: 587 (TLS) or 465 (SSL)
Username: Your full email address
Password: Your email password
Authentication: SSL/TLS or STARTTLS
Bluehost:
SMTP Host: mail.yourdomain.com (replace with your actual domain)
Port: 587 (TLS) or 465 (SSL)
Username: Your full email address
Password: Your email password
Authentication: SSL/TLS
HostGator:
SMTP Host: mail.yourdomain.com or gator####.hostgator.com
Port: 587 (TLS) or 465 (SSL)
Username: Your full email address
Password: Your email password
Authentication: SSL/TLS
Note: Always check your specific provider's documentation, as settings can vary based on your hosting plan or configuration.
Navigate to Integrations
Select "Connect SMTP Account" or "Connect Email via SMTP"
Enter your SMTP server details in the form:
SMTP Host: Enter the server address
Port: Enter the port number (usually 587 or 465)
Email Address: Your sending email address
Username: Usually the same as your email address
Password: Your email password or app password
Authentication Method: Select SSL/TLS or STARTTLS
Click "Test Connection" to verify settings
If successful, save and confirm connection
If unsuccessful, review error message and verify settings
Common Issues and Solutions:
"Connection Failed" Error:
Verify SMTP host address is correct (check for typos)
Confirm port number matches your provider's requirements
Ensure you're using the correct username format (usually full email address)
Check that your password is correct
Try alternate ports (switch between 587 and 465)
"Authentication Failed" Error:
Verify username is correct (typically your full email address)
Confirm password is accurate
If 2FA is enabled, generate and use an app-specific password
Check if your provider requires enabling "less secure app access"
Verify your email account is active and not locked
"SSL/TLS Error":
Try switching between port 587 (STARTTLS) and 465 (SSL)
Verify you've selected the correct authentication method
Ensure your provider supports the selected encryption type
Check if your network or firewall is blocking encrypted SMTP
"Relay Access Denied":
Confirm your email account has permission to send via SMTP
Check if your hosting provider requires whitelisting IP addresses
Verify you're using authenticated SMTP (not anonymous relay)
Contact your email provider to ensure SMTP sending is enabled
Finding Your SMTP Settings:
If you can't find your SMTP settings:
Search "[Your Provider Name] SMTP settings" in Google
Check your email provider's support documentation or knowledge base
Look in your current email client's settings (if you use Outlook, Thunderbird, etc.)
Contact your email provider's support team
Check your hosting control panel (cPanel, Plesk, etc.) if you have web hosting
App Passwords: If your email provider supports two-factor authentication (2FA), you'll likely need to generate an app-specific password rather than using your regular email password. This is more secure and prevents issues with authentication.
Password Storage: Eve encrypts stored SMTP credentials. However, you should:
Use strong, unique passwords
Enable 2FA on your email account when possible
Regularly update passwords
Monitor for unauthorized access
Less Secure App Access: Some older email systems require enabling "less secure app access" to allow SMTP connections from third-party applications. While this is sometimes necessary, it reduces security. When possible:
Use OAuth-based connections (Gmail/Outlook direct) instead
Use app-specific passwords if your provider supports them
Monitor account activity for suspicious access
Q: Should I use SMTP or the direct Gmail/Outlook integration? A: Always use the direct Gmail or Outlook integration when possible. These OAuth-based connections are more secure (you don't share your password), easier to set up, and provide better feature integration. Only use SMTP for email providers that don't have direct integration options, such as GoDaddy, Bluehost, Zoho, or other custom hosting providers.
Q: I have a Google Workspace (G Suite) email. Should I use Gmail integration or SMTP? A: Use the Gmail integration. Google Workspace accounts work with the Gmail OAuth integration, which is simpler and more secure than SMTP. The Gmail integration supports all Google Workspace accounts, not just personal Gmail addresses.
Q: What's the difference between port 587 and port 465? A: Both are SMTP ports, but they use different encryption methods:
Port 587: Uses STARTTLS (starts unencrypted, then upgrades to encrypted)
Port 465: Uses SSL/TLS (encrypted from the start)
Both are secure. Try port 587 first (it's more commonly supported), and if that doesn't work, try port 465. Some providers support both; others only support one.
Q: My email provider requires me to "enable less secure app access." Is this safe? A: "Less secure app access" is Google's term for allowing password-based authentication instead of OAuth. For Gmail, avoid this if possible—use the Gmail direct integration or generate an App Password instead. For other providers, this setting may be necessary to enable SMTP, but ensure:
You use a strong, unique password
You monitor account activity
You enable 2FA if available
You understand the increased risk
Q: Can I use SMTP to connect Gmail or Outlook instead of the OAuth integration? A: Yes, technically, but it's not recommended. The OAuth integrations are more secure and easier to maintain. If you're having trouble with OAuth, try troubleshooting that first before resorting to SMTP. SMTP should only be used when OAuth isn't available.
Q: What if I don't know my SMTP settings? A: Your email provider's support documentation always contains SMTP settings. Search for "[Your Provider] SMTP settings" or check:
Your email provider's help center or knowledge base
Your hosting control panel (cPanel, Plesk, etc.)
Your current email client's server settings
Contact your provider's support team directly
Most providers have standardized settings that are publicly documented.
Q: I'm getting "authentication failed" even though my password is correct. What's wrong? A: Common causes:
Two-factor authentication: If 2FA is enabled, you need an app-specific password, not your regular password
Less secure access disabled: Some providers require enabling third-party app access
Username format: Try your full email address as the username, not just the part before @
Account locked: Too many failed attempts may have temporarily locked your account
Special characters: If your password has special characters, ensure they're entered correctly
Q: Do SMTP connections work differently than Gmail/Outlook integrations? A: Functionally, no. Once connected, emails send the same way regardless of connection method. The difference is in the authentication process (OAuth vs. username/password) and initial setup complexity. SMTP requires more manual configuration but works with any email provider that supports SMTP.
Q: Can I connect multiple email providers via SMTP? A: Yes, if you're on the Pro Plan (which allows unlimited email connections). You can connect one email via Gmail OAuth, another via Outlook OAuth, and several more via SMTP from different providers. Each account is managed independently, and you select which one to use when creating campaigns.
Q: My SMTP connection worked initially but stopped sending. What happened? A: Common causes:
Password changed: If you changed your email password, update it in Eve's Integrations
Provider restrictions: Some providers limit SMTP connections or require periodic re-authorization
IP address changes: Some providers require whitelisting IP addresses
Account suspended: Check if your email account has been suspended or restricted
Sending limit exceeded: You may have hit your provider's daily sending limit
Check the integration status in Eve, and reconnect if necessary.
Q: Is SMTP less reliable than OAuth integrations? A: Not necessarily less reliable, but OAuth connections are more resilient to certain issues (like password changes). SMTP connections work well when properly configured. However, OAuth is generally preferred because:
More secure (no password sharing)
Easier to maintain (tokens refresh automatically)
Better error handling
Additional feature support
SMTP is perfectly reliable when it's your only option for a particular email provider.
