Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.






A comma-separated list of FEJ SMTP client IDsY


The SMTP server to connect toY


The SMTP server port to connect toY


The SMTP user name to connect withY


The SMTP user's password. Optional if SMTP supports user access without a password.N


Protocol for connection to the SMTP server. 'smtp' supported.N


Default email's subjectY


Default email's 'To' comma-separated listY


Default email's 'Cc' comma-separated listN


Default email's 'Bcc' comma-separated listN


FEJ groups for routing to this SMTP endpointN


An instance of the email converter interface, as a reference to the Spring bean name, to convert incoming MessageEvent to email fields.N


Implementation class of the email converter interface to create a converter instance on endpoint initialization. 

By default, an implementation based on Apache Velocity templates is used.





mail.smtp.fromEmail address to use for the SMTP MAIL command. This sets the envelope return address.
mail.smtp.authIf true, attempt to authenticate the user using the AUTH command.
mail.smtp.socketFactory.portSpecifies the port to connect to when using the specified socket factory.
mail.smtp.socketFactory.classIf set, specifies the name of a class that implements the interface. This class will be used to create SMTP sockets.
mail.smtp.starttls.enableIf true, enables the use of the STARTTLS command (if supported by the server) to switch the connection to a TLS-protected connection before issuing any login commands. If the server does not support STARTTLS, the connection continues without the use of TLS; see the mail.smtp.starttls.required property to fail if STARTTLS isn't supported.
mail.smtp.starttls.requiredIf true, requires the use of the STARTTLS command. If the server doesn't support the STARTTLS command, or the command fails, the connect method will fail.
templatePath to the Velocity template file for the default email converter interface. See more at Template converter properties.

The full list of properties could be found here.

NOTE: The FIX session can be started or stopped only if scheduling is applied. Otherwise, the session will be inactive. Refer to the Configuring Scheduler section where the session start procedure is specified.


Using templates for emails

If a custom implementation for the email converter interface is not defined, the SMTP endpoint uses a the default one, which is based on Apache Velocity. Velocity is a Java template engine with simple but powerful syntaxessyntax.

This converter may transform either a MessageEvent with FIX messages inside or an AppEvent if it was routed to an STMP endpointThe converter puts the received MessageEvent object and all its header fields to the template context as shown in the table below:

Variable nameVariable typeDescription
eventMessageEventoriginal Original MessageEvent for converting to email.

Predefined header field. Contains the The source AppEvent instance (like NewSessionEvent) in case, if it was sent from a business rule to an STMP routed to SMTP endpoint.

email.templateStringPredefined header field. Custom template name. Can be set via the MessageEvent#setHeader() field. 
email.subjectStringPredefined header field. Custom email subject. Can be set via the MessageEvent#setHeader() field. 

The path to the template should be defined with the template property in the configuration of the SMTP endpoint configuration. In the case where If the template is placed into the conf directory, the path can be relative: