HomeGithubDiscordBlog

SMTP Settings

SMTP Email Setup for OpenAlgo

Gmail Configuration Options

Choose the configuration that matches your Gmail setup:

Personal Gmail (Recommended)

After migration, go to Profile → SMTP Configuration and use:

Google Workspace (Business Gmail)

For business domains (e.g., [email protected]):

Option 1: SMTP Relay (Recommended for Businesses)

Requirements:

  • Google Workspace Admin access

  • Server IP registration in Google Admin Console

Configuration:

Setup Steps:

  1. Admin Console Setup:

    • Go to Google Admin Console

    • Navigate to Apps → Google Workspace → Gmail → SMTP relay service

    • Click Add another to create new relay

    • Configure these settings:

    • Add your server IP address to allowed IP ranges

    • Save the configuration

  2. Find Your Server IP:

  3. Register IP in Admin Console:

    • In SMTP relay settings, add your server IP to IP addresses

    • Format: YOUR.SERVER.IP.ADDRESS/32 (e.g., 203.0.113.15/32)

Option 2: Personal Gmail Settings (Alternative)

If SMTP relay setup is complex, use personal Gmail settings:

App Password Setup (Required for Both)

For Personal Gmail:

  1. Go to Google Account Settings

  2. Enable 2-Factor Authentication (if not enabled)

  3. Select App passwords

  4. Choose Mail from dropdown

  5. Generate password and copy the 16-character code

  6. Use this password in OpenAlgo (NOT your regular password)

For Google Workspace:

  1. Go to Google Account Settings

  2. Admin may need to enable App Passwords:

    • Admin Console → Security → API controls → App passwords

    • Enable "Allow users to manage their app passwords"

  3. Follow same steps as personal Gmail above

  4. If App Passwords unavailable, ask your IT administrator

Advanced Google Workspace Configuration

Admin Console SMTP Relay Settings

For enterprise deployments, configure these advanced settings:

  1. Security Settings:

  2. Rate Limiting:

  3. Routing Settings:

Multiple Domain Support

If you have multiple domains in Workspace:

  1. Primary Domain Configuration:

  2. Additional Domains:

    • Add all domains to Admin Console → Domains

    • Enable SMTP relay for each domain

    • Use same SMTP settings with appropriate From Email

Troubleshooting Google Workspace

Common Error: "Mail relay denied"

Solution 1 - IP Registration:

Solution 2 - Authentication:

  • Verify App Password is correctly generated

  • Ensure 2FA is enabled on the account

  • Check username format (full email address)

Solution 3 - Fallback to Personal Settings:

Error: "Authentication failed"

  1. Check App Password:

    • Must be 16 characters without spaces

    • Generated specifically for "Mail"

    • Account must have 2FA enabled

  2. Admin Policy Check:

  3. Account Verification:

    • Ensure account is not suspended

    • Check for recent password changes

Testing Your Configuration

Step-by-Step Testing

  1. Save SMTP Settings in Profile → SMTP Configuration

  2. Click "Debug" to test connection and view detailed diagnostics

  3. Click "Send Test" to send test email to yourself

  4. Check your inbox (and spam folder)

  5. Try Password Reset to test end-to-end functionality

Expected Test Results

Debug Output (Success):

Debug Output (Common Issues):

Testing Different Scenarios

  1. Test from Different IPs: If using multiple servers

  2. Test Different From Addresses: Verify domain permissions

  3. Test High Volume: Check rate limiting behavior

  4. Test Failed Authentication: Verify error handling

Production Deployment Best Practices

Security Recommendations

  1. Use Dedicated Service Account:

  2. IP Whitelist Management:

    • Use static IP addresses for production servers

    • Document all registered IPs

    • Regular audit of IP permissions

  3. Monitor Email Logs:

    • Track successful/failed send attempts

    • Monitor for suspicious activity

    • Set up alerts for authentication failures

Performance Optimization

  1. Connection Pooling: Use persistent SMTP connections when possible

  2. Rate Limiting: Respect Google's sending limits

  3. Retry Logic: Implement exponential backoff for failures

  4. Queue Management: Handle high-volume email sending

Common Issues & Solutions

Personal Gmail Issues

  • Authentication Failed: Use App Password, not regular password

  • Connection Failed: Try port 587 instead of 465

  • 2FA Required: Enable 2-Factor Authentication first

Google Workspace Issues

  • Mail relay denied:

    • Register server IP in Admin Console

    • Verify SMTP relay service is enabled

    • Check authentication credentials

  • Admin restrictions:

    • App passwords may be disabled by admin

    • Less secure app access may be blocked

    • Contact IT administrator for policy changes

  • Domain verification:

    • Ensure domain is verified in Workspace

    • Check MX records are properly configured

    • Verify user account is active

Network & Firewall Issues

  • Port blocking: Ensure ports 587/465 are open outbound

  • Proxy servers: Configure SMTP through corporate proxy if needed

  • DNS resolution: Verify smtp.gmail.com resolves correctly

Alternative Email Providers

Microsoft 365 / Outlook

Business (Exchange Online):

Personal Outlook/Hotmail:

Yahoo Mail

Custom SMTP Providers

SendGrid:

Mailgun:

Enterprise Integration

Load Balancing

For high-availability setups:

  1. Configure multiple SMTP servers

  2. Implement failover logic

  3. Monitor server health

  4. Balance email load across servers

Compliance & Logging

  1. Audit Requirements:

    • Log all email send attempts

    • Track recipient information (hashed)

    • Monitor for compliance violations

  2. Data Retention:

    • Configure log retention periods

    • Implement secure log storage

    • Regular compliance audits

Monitoring & Alerting

Set up monitoring for:

  • SMTP connection failures

  • Authentication errors

  • Rate limit violations

  • Unusual sending patterns

Support & Resources

Google Support Links

OpenAlgo Resources

  • Built-in Debug: Use SMTP Debug function in profile

  • Log Files: Check OpenAlgo logs for detailed error messages

  • GitHub Issues: Report SMTP-specific problems

  • Documentation: /docs/PASSWORD_RESET.md for complete system overview

That's it! Your OpenAlgo can now send emails for password resets and notifications using your preferred email provider. Choose the configuration that best fits your organization's setup and security requirements.

PreviousTesting OpenAlgo in CloudNextTOTP Configuration

Last updated

Was this helpful?