We're in the middle of some fast-moving changes to the Forem Admin experience, so we've paused documentation updates for the time being. You may find that the docs are now outdated in parts. If you have any questions, please visit forem.dev to request additional support. We thank you for your patience and hope you're liking the changes!
As a Forem Cloud client, you are provided with an email server managed by the Forem team. All settings are managed by us and the from and reply email addresses for all emails are set as firstname.lastname@example.org.
However, you can override this to use your own email server.
These settings are required for your Forem to send emails. If you wish to send invites (for example, for an invite-only Forem), email digests, activity notifications, you need to specify which email host will relay those messages for you.
NOTE: Once you submit your SMTP settings for your Forem, all users will be automatically logged out and required to confirm their email addresses to be able to log in again. Only the First User won't have to do this. Please ensure that your First User is still a Super Admin and that you still have access to that account before proceeding with these settings. Without this, you may possibly lose access to your Forem if the SMTP settings configuration fails.
When choosing your transactional email service, check that the rate limit (maximum number of emails you can send) allows for your Forem to send all the emails it needs to. Some providers, especially free ones, set a cap to minimize spam. If your rate limit is too low, emails from your Forem may not be sent, and this may impact the user experience of new or existing members.
In order to configure SMTP for your Forem, you will need to obtain an email service. Some suggested SMTP providers are
You may also have email service bundled with your domain or DNS provider (again, check your rate limits here).
Before you can configure your Forem for SMTP, many SMTP providers require you to set up domain authentication manually. Refer to your SMTP provider's documentation to confirm these steps, e.g.
Expand your Email Server Settings under
Remember: submitting these settings will lock out all users who haven't confirmed their email address (by requesting an email confirmation at the log in screen, which will be sent to the email address they supplied at registration). Ensure you have full access to your First User (user ID 1) complete with Super Admin permissions before proceeding.
Username specified for your SMTP service (not always the username for accessing your account). This varies from provider to provider. For some, this may be the username before the @ sign, or it may be your entire email address. For Sendgrid, this is always "apikey". Check with your SMTP host if you are unsure.
Password specified for your SMTP service (not always the password for accessing your account). Sendgrid users will need to generate an API key instead, and use the full API key as the password. Sendinblue users will need to request an SMTP password from Support before being able to use SMTP.
Address of the remote mail server, e.g. smtp.gmail.com or smtp.sendgrid.net
If your mail server specifies authentication type, you will need to make sure that this field reflects this. The default is usually "login" (which will send password Base64 encoded), with other options being "plain" (will send the password in the clear) or "cram_md5" (combines a Challenge/Response mechanism to exchange information and a cryptographic Message Digest 5 algorithm to hash important information).
If you need to specify a HELO domain, you can do it here. If not, leave this field blank.
The port that your mail server runs on. This could be 25 or 587 for unencrypted/TLS email, or 465 for SSL-encrypted email, so it's best to confirm these settings with your SMTP service provider.
The email address that all emails will be sent from.
The email address that users reply to.