awssilverstripe

Configure SMTP for outbound emails

To configure SMTP settings using an external SMTP server, follow these steps:

  • Add the lines indicated below to the /opt/bitnami/silverstripe/app/_config/email.yml file and update the placeholders to reflect the settings for the SMTP server:

      SilverStripe\Core\Injector\Injector:
        Swift_Transport:
          class: Swift_SmtpTransport
          properties:
            Host: SMTP_HOST
            Port: SMTP_PORT
            Encryption: SMTP_PROTOCOL
          calls:
            Username: [ setUsername, ['SMTP_EMAIL'] ]
            Password: [ setPassword, ['SMTP_PASSWORD'] ]
            AuthMode: [ setAuthMode, ['login'] ]
    

    Here’s an example using Gmail. Replace USERNAME and PASSWORD with your Gmail account username and password respectively.

      SilverStripe\Core\Injector\Injector:
        Swift_Transport:
          class: Swift_SmtpTransport
          properties:
            Host: smtp.gmail.com
            Port: 587
            Encryption: tls
          calls:
            Username: [ setUsername, ['USERNAME@gmail.com'] ]
            Password: [ setPassword, ['PASSWORD'] ]
            AuthMode: [ setAuthMode, ['login'] ]
    
  • Browse to http://SERVER-IP/silverstripe/dev/build and click the “Run the action” button to rebuild the database.

For more information, refer to the official documentation.

To configure the application to use the SMTP service provided by Amazon Simple Email Service (SES), refer to the guide on using Amazon SES.

NOTE: Amazon EC2 blocks SMTP port 25 by default on all Amazon EC2 instances, and you must manually request removal of this restriction to use this port.

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 March 18, 2021