Configure SMTP for outbound emails

NOTE: We are in the process of modifying the file structure and configuration for many Bitnami stacks. On account of these changes, the file paths stated in this guide may change depending on whether your Bitnami stack uses native Linux system packages (Approach A), or if it is a self-contained installation (Approach B). To identify your Bitnami installation type and what approach to follow, run the command below:

 $ test ! -f "/opt/bitnami/common/bin/openssl" && echo "Approach A: Using system packages." || echo "Approach B: Self-contained installation."

The output of the command indicates which approach (A or B) is used by the installation, and will allow you to identify the paths, configuration and commands to use in this guide. Refer to the FAQ for more information on these changes.

To configure outbound email, follow these steps:

Edit the ERPNext site_config.json file. Add or update the SMTP configuration in the file. Here is an example of how to configure a Gmail account. Replace the DB_PASSWORD placeholder with the correct database password and the USERNAME and PASSWORD placeholders with your Gmail account username and password respectively.

NOTE: Depending on your installation type, the ERPNext site_config.json file will be located in the following paths:

  • Approach A (Bitnami installations using system packages): /opt/bitnami/frappe-bench/sites/erpnext/site_config.json
  • Approach B (Self-contained Bitnami installations): /opt/bitnami/apps/erpnext/htdocs/frappe-bench/sites/erpnext/site_config.json

Your file should look like this:

    "db_name": "bitnami_erpnext",
    "db_password": "DB_PASSWORD",
    "mail_server": "",
    "mail_login": "",
    "mail_password": "PASSWORD",
    "use_ssl": 1,
    "mail_port": 587,
    "auto_email_id": ""

NOTE: Remember to use double quotes around the values and a comma after every line except the last one. All the parameters should be enclosed between curly braces as shown above.

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 December 21, 2022