Skip to main content

SMTP Configuration (Business License)

SMTP configuration is required for your WhautoMail Business License deployment to send important emails such as login verification codes, password resets, invite emails, and key account notifications. Without a working SMTP setup, users and admins will not receive these messages, which impacts both security and user experience.

This guide explains which SMTP details you need from your email provider (SMTP host, port, username, password, and encryption type) and how to apply them to your WhautoMail environment.

Once configured correctly, your self-hosted WhautoMail instance will be able to reliably deliver system emails and notifications.

Step 1: Choose an SMTP Provider​

  • You can use a commercial provider (e.g., SendGrid, Mailgun, Amazon SES, Gmail) or your own mail server.

Step 2: Gather SMTP Details​

  • Host (SMTP server address)
  • Port (usually 587 for TLS, 465 for SSL, or 25 for non-secure)
  • Username (email address or SMTP user)
  • Password (SMTP password or app password)
  • TLS/SSL requirement

Step 3: Configure WhautoMail​

In your installation folder, locate the web-server.env file. This file contains the environment variables required for your WhautoMail deployment, including SMTP settings.

Make sure to update the following section in web-server.env with your SMTP provider details:

# SMTP Configuration (Required for Signup verification, team member invites and notifications) - Any SMTP server will work E.g. AWS SES, MailGun, SendGrid, etc
SMTP_HOST='your_smtp_host'
SMTP_PORT='your_smtp_port'
SMTP_USERNAME='your_smtp_username'
SMTP_PASSWORD='your_smtp_password'
DEFAULT_FROM_EMAIL='Product Support <support@example.com>'
SUPPORT_EMAIL='support@example.com'
  • Replace the values in single quotes with your actual SMTP details.
  • DEFAULT_FROM_EMAIL is the name and email that will appear as the sender for outgoing emails.
  • SUPPORT_EMAIL is the address users can reply to for support questions.

Any SMTP server will work, including AWS SES, MailGun, SendGrid, Gmail (with app password), or your own mail server.

Security Best Practices​

  • Use app-specific passwords or API keys if supported by your provider.
  • Never share your SMTP credentials publicly.
  • Enable 2FA on your email provider account.
  • Use secure ports (465 or 587) and always require TLS/SSL.

Troubleshooting​

  • Check your SMTP provider’s logs for rejected connections or authentication errors.
  • Ensure your server’s firewall allows outbound connections to the SMTP port.
  • Some providers (e.g., Gmail) may require you to enable access for less secure apps or generate an app password.

Refer to your SMTP provider’s documentation for detailed steps and troubleshooting tips.