Email setup
Forgejo can be set to send emails such as a registration confirmation, either with Sendmail (or compatible MTAs like Postfix and msmtp) or by connecting to an SMTP server.
Using SMTP
Directly use SMTP server as relay. This option is useful if you don't want to set up MTA on your instance but you have an account at an email provider.
[mailer]
ENABLED = true
FROM = forgejo@example.com
PROTOCOL = smtps
SMTP_ADDR = mail.example.com
SMTP_PORT = 465
USER = forgejo@example.com
PASSWD = `mysecurepassword`
Restart Forgejo for the configuration changes to take effect.
To send a test email to validate the settings, go to Forgejo > Site Administration > Configuration > SMTP Mailer Configuration.
To enable users to receive email notifications for pull requests or issues, you can set ENABLE_NOTIFY_MAIL=true in the configuration.
For the full list of options check the Config Cheat Sheet.
[!note] Note Authentication is only supported when the SMTP server communication is encrypted with TLS or
HOST=localhost. This is due to protections imposed by the Go internal libraries against STRIPTLS attacks. TLS encryption can be through:
- STARTTLS (also known as Opportunistic TLS) via port 587. Initial connection is done over cleartext, but then be upgraded over TLS if the server supports it.
- SMTPS connection (SMTP over TLS) via
SMTP_PORT=465and/orPROTOCOL=smtps. Connections to the server use TLS from the beginning, also known as Implicit TLS. It is recommended by RFC8314.
Using Sendmail
Use sendmail command as mailer.
[!note] Note For Internet-facing sites consult the documentation of your MTA for instructions to send emails over TLS. Also set up SPF, DMARC, and DKIM DNS records to make emails sent be accepted as legitimate by various email providers.
[mailer]
ENABLED = true
FROM = forgejo@example.com
PROTOCOL = sendmail
SENDMAIL_PATH = /usr/sbin/sendmail
SENDMAIL_ARGS = "--" ; most "sendmail" programs take options, "--" will prevent an email address being interpreted as an option.