Skip to main content

The msg_gen.conf file contains the configuration relevant to message generation. This file is included from within ecelerity.conf.


Restart the ecelerity process if you make any changes to the msg_gen.conf file. Running the config reload command will not suffice.

The following is an example msg_gen.conf file:

httpsrv { }
HTTP_Listener {
  Listen ":2081" {}
substitution_engine {}

scriptlet "scriptlet" {
  script "rest_templates" { source = "" }
  script "rest_users" { source = "" }
  script "rest_transmissions" { source = "" }
  script "open_track" { source = "" }
  script "click_tracker" { source = "" }
# One entry for each Platform node
cassandra_client {
  uri = ("name=cassandra_db;host=;port=9160"

engagement_tracker {}

msg_gen {
  engagement_tracking_host = ""
  cluster_cfg = true
  quorum = 2
  # a node stanza for each Platform node
  node node1.lan {
    mta_id = 1
    votes = 1
  node node2.lan {
    mta_id = 2
    votes = 1

For a discussion of scopes and fallbacks, see “Configuration Scopes and Fallback”.

For a summary of all the non-module specific configuration options, refer to Configuration Options Summary .

Modules and their configuration options are discussed in the Modules Reference .

The following are the modules configured in the msg_gen.conf file:


This module configuration includes a uri entry for each Platform node in your cluster. Do not change this setting.


This module handles the creation of open-tracked and click-tracked links and the corresponding parsing of the links when an open or click event occurs. See “engagement_tracker – HTTP Engagement Tracking”.


To use the REST API, this listener module must be loaded. By default, the HTTP_Listener listens on port 2081. See Configuring Inbound Mail Service Using HTTP .


To use the REST API, this HTTP server infrastructure module must be loaded. See “httpsrv – HTTP Server”.


Handles message generation. See “msg_gen – Message Generation”.


The scriptlet module defined in msg_gen.conf supplements the scriptlet module defined in ecelerity.conf. The various script scopes point to the scripts needed to support message generation. Note that the scriptlet module instance name, scriptlet, is the same as the scriptlet instance name in the ecelerity.conf file. All instances of the scriptlet module must use the same instance name. For more information, see “scriptlet - Lua Policy Scripts”.


This module handles substitution in the templates. It has no configuration options.

Was this page helpful?