Configure SMTP for outbound emails

Before running the commands shown on this page, you should load the Bitnami stack environment by executing the installdir/use_APPNAME script (Linux and MacOS) or by clicking the shortcut in the Start Menu under “Start -> Bitnami APPNAME Stack -> Application console” (Windows). On OS X VMs, the installation directory is /opt/bitnami and OS X VM users can click the “Open Terminal” button to run commands. Learn more about the Bitnami stack environment and about OS X VMs.

To configure SMTP settings using an external SMTP server, you have to add the lines indicated below to the installdir/apps/discourse/htdocs/config/discourse.conf:

smtp_address = "SMTP_HOSTNAME"
smtp_port = SMTP_PORT
smtp_domain =
smtp_user_name = 'SMTP_USER'
smtp_password = 'SMTP_PASSWORD'
smtp_enable_start_tls = true

Restart the servers:

$ sudo installdir/ restart

SMTP configuration for Gmail

Warning: If you use Discourse extensively, we recommend to use your own SMTP server for sending emails. The current Gmail sending limit is 500 emails per 24 hours.

An example for Gmail is as follows. Replace USERNAME and PASSWORD with your Gmail account username and password respectively.

smtp_address = ""
smtp_port = 587
smtp_domain =
smtp_user_name = ''
smtp_password = 'PASSWORD'
smtp_enable_start_tls = true
smtp_authentication = login

To configure the application to use other third-party SMTP services for outgoing email, such as SendGrid, refer to the FAQ.

NOTE: If you are using Gmail as the outbound email server, your application’s attempts to send outgoing emails may be blocked by Gmail if it considers the authentication attempts to be suspicious. When this happens, you will receive a Gmail security alert at the corresponding Gmail address. To proceed, you will need to manually confirm the validity of the authentication attempt before Gmail will permit the application to send outbound emails. For more information on this and other Gmail issues related to outbound email from your application, refer to our Gmail SMTP troubleshooting page.

Last modification July 29, 2019