Configure Email



BRC provides an SMTP server based on AWS SES. This page explains how to configure the SMTP server for your Bloomreach Cloud stack to enable your Bloomreach Experience Manager implementation to send email messages.


To enable the applications deployed in your Bloomreach Cloud stack to send email messages, you need credentials and the host configuration string for the SMTP server. You can use your own SMTP server, or BloomReach can provide this.

To use a SMTP server provided by BloomReach, please create a support ticket with the domain to send the mails from. BloomReach will ask you on behalf of AWS to put some entries into your DNS to prove you own the domain. It is best not to wait too long with entering these entries. After the confirmation, BloomReach will upload a mail configuration file to your stack. This configuration file will contain the following properties:

Common (both smtp and smtps):
brc.mail.transport.protocol=... (default is smtp)
brc.mail.debug.auth=... (default is false)
brc.mail.debug=... (default is false)

SMTP properties:
brc.mail.smtp.auth=... (default is true)
brc.mail.smtp.ssl.checkserveridentity=... (default is false) (default is *)
brc.mail.smtp.ssl.protocols=... (default is TLSv1 TLSv1.1 TLSv1.2)
brc.mail.smtp.starttls.enable=... (default is true)
brc.mail.smtp.starttls.required=... (default is false)

SMTPS properties:
brc.mail.smtps.auth=... (default is true)
brc.mail.smtps.ssl.checkserveridentity=... (default is false) (default is *)
brc.mail.smtps.ssl.protocols=... (default is TLSv1 TLSv1.1 TLSv1.2)
brc.mail.smtps.starttls.enable=... (default is true)
brc.mail.smtps.starttls.required=... (default is false)

When deploying a distribution, you need to select the option to copy this configuration file for production usage.
Stack running BRC 12.5.0 or later: Make sure that the file name for copied config is:
Stack running older version of BRC: Using the config file as Java System Properties (this is less secure).

Note that you can only send emails from the verified domain. This means that the fields "From", "Source", "Sender", or "Return-Path" addresses must use the verified domain.


Your custom code can use the Java system properties as in the example below. Notice the brc.mail.* entries, these are populated through Java system properties from the configuration file. This example is based on the AWS Java SMTP example and provided for learning purposes. For production usage we recommend reading the configuration file as system properties are exposed in the CMS admin console.

// returns info message or exception message
private String brcMail() throws MessagingException, UnsupportedEncodingException, NamingException {
    // Replace [email protected] with your "From" address.
    // This address must be verified.
    final String FROM = "[email protected]";
    final String FROMNAME = "Customer";

    // Replace [email protected] with a "To" address.
    final String TO = "[email protected]";

    final String SUBJECT = "BRC Test";

    final String BODY = String.join(
            "<h1>BloomReach Cloud Email Test</h1>",
            "<p>This email was sent with BloomReach Cloud using the ",
            "<a href=''>Javamail Package</a>",
            " for <a href=''>Java</a>."

    // retrieve Session object from JNDI
    Context initCtx = new InitialContext();
    Context envCtx = (Context) initCtx.lookup("java:comp/env");
    Session session = (Session) envCtx.lookup("mail/Session");

    // Create a message with the specified information.
    MimeMessage msg = new MimeMessage(session);
    msg.setFrom(new InternetAddress(FROM, FROMNAME));
    msg.setRecipient(Message.RecipientType.TO, new InternetAddress(TO));

    // Create a transport.
    Transport transport = session.getTransport();

    // Send the message
    String result;

        // Connect to Amazon SES

        // Send the email.
        transport.sendMessage(msg, msg.getAllRecipients());
        result = "Email sent!";
    catch (Exception ex) {
        System.out.println("The email was not sent.");
        System.out.println("Error message: " + ex.getMessage());
        result = ex.getMessage();
        // Close and terminate the connection.
    return result;

Enterprise Forms

If you plan to use Enterprise Forms, you also need to deploy the mail configuration file together with your distribution. When deploying, make sure that the file name for copied config is: It is critical to configure enterprise forms to use a sender email address that has been verified. When deploying using mail configuration file, a mail/Session container variable is automatically configured in your environment using the properties mentioned above. 
Note that using Enterprise forms will have an impact on the Blue/Green deployments; during the content freeze, data that is stored in the 'old' repository will get lost if you do not migrate the data to the new repository.

Gmail SMTP example

Note: For using Gmail as mail sender, one can setup App password for Google account. More details here: Sign in with App Passwords

Example configuration file:

brc.mail.smtp.username=... (Gmail address)
brc.mail.smtp.password=... (Gmail app password)

Office365 SMTP example

Note: For using SMTP, one needs to enable SMTP AUTH on mailbox. More details here: Enable or disable authenticated client SMTP submission

Example configuration file:

brc.mail.smtp.username=... (Office365 account address)
brc.mail.smtp.password=... (Office365 account password)

Note: For Office365 SMTP, one needs to setup valid From address field to be a valid Office365 mail account address. To do that, go to CMS Console. In the treeview browse to:


Update parameter values for eforms-from-name and eforms-from-email.

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?

    We rely on cookies

    to optimize our communication and to enhance your customer experience. By clicking on the Accept and Close button, you agree to the collection of cookies. You can also adjust your preferences by clicking on Manage Preferences. For more information please see our Privacy policy.

    Manage cookies
    Accept & close

    Cookies preferences

    Accept & close