Welcome Guest! Log in
Stambia versions 2.x, 3.x, S17, S18, S19 and S20 are reaching End of Support January, 15th, 2024. Please consider upgrading to the supported Semarchy xDI versions. See Global Policy Support and the Semarchy Documentation.

The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…

Stambia DI for Email

    Stambia Data Integration allows to work with mail servers to produce fully customized Processes sending or receiving mails.

    A Mail Metadata is available to define all the mail server's credentials and communication properties that can then be used in processes to send or receive mails.

    Read more: Stambia DI for Email

    Sending emails with Gmail SMTP servers

      Two ways of authenticating

      Gmail's SMTP servers support two ways of authenticating.

      1. The classical user/password authentication

      2. The OAuth2 authentication https://developers.google.com/gmail/oauth_overview#protocol


      Currently, Stambia's SMTP metadata supports the classical user/password authentication.


      Allowing "less secure apps" in the Google account

      By default, a Google account allows only Google apps to connect to their services with username/password.

      In order to use third party Email clients with username/password, the Google account owner has to enable the "Allow less secure apps" setting. 

      Stambia is - in a way - a third party Email client, so this requirement applies.

      In order to enable this setting, please follow Google's instructions.


      Configuring Stambia's SMTP metadata

      The "Outgoing server (SMTP)" node should be configured like this:

      • Name: GmailSmtp (for example)
      • Host: smtp.gmail.com
      • Port: 465
      • User: <google-user-account>@gmail.com
      • Password: <google-user-password>
      • Use secure protocol: SSL


      Using the SMTP metadata with a SendMail action

      Simply drag and drop the SMTP metadata on the SendMail action. The hostname, port, user, password, and SSL mode will be automatically inherited from the metadata.

      Set the required MAIL_FROM and MAIL_TO parameters, and the action should work fine.




      Suggest a new Article!