Miscellaneous Options

Option | Description
MAX_EMAIL_LIST_SIZE | Integer. Emails are sent using a shell command line, which may have a limited length. If this (MAX_EMAIL_LIST_SIZE) is set to a fairly low value (in characters), then when large distributions are generated, they will be split into multiple emails, each with a smaller list of recipients.
DEFAULT_SUBJECT | Specifies a default subject line that will be used if the template being processed does not specify one. Most templates will set the subject line, as this allows variables (such as item names) to be show in the subject itself.
DEFAULT_SUBJECT_MULTIPLE | When multiple emails are merged together in a digest structure, this variable specifies what the default subject will be.
MULTIPLE_TEMPLATE | This names a special template that is a "container" that holds the individual pieces of a merged (digest) email. It can be customized to achieve certain formatting effects. The supplied version, multiple_notifications.tplt, uses a simple HTML splitter bar between individual email bodies. Consult this example for further information.
ENVELOPE | This names a special template which is used like an envelope, wrapping up the email body just prior to posting. The supplied example, html-envelope-outer.tplt adds the necessary HTML syntax to the top and bottom of the email, to make a valid HTML message. It could be customized to add customer-specific branding to all Dimensions CM emails.
EMAIL_SLEEP | In some configurations, SMTP servers cannot respond quickly enough to a large number of emails, such as may be generated by dmemail. This could, for example, be the result of an anti-spam policy implemented by the SMTP server. This parameter specifies a value in seconds which is used as a delay between sending messages. By default, this figure is set to 30. If you do not have any such spam policy in place, it is highly recommended that you lower this to a figure of 1 or 2.
EMAIL_DIRECTORY | Emails are first created as files, in this directory. If this option is not specified, the default at DM_TMP will be sent.
DIGEST | This option controls the way emails are digested: 0 - No digesting for super-fast processing of an email backlog. This directly sends each row. 1 - (Default) The current behavior based on digest flag against user subscription. 2 - Forced mode - all messages will be digested, to produce only one email per user no matter what. This could be used to ease the burden on the mail server in a backlog situation.
DIGEST_THRESHOLD | This option sets the limit for the number of messages to be digested. Numeric value, default 10000. If the number of rows to be processed is larger than this, then dmemail refuses to work unless DIGEST=0 is in effect. This limit can be overridden when large runs are required.
FILTER_SQL | This option specifies a "sql where clause component" that will be used to select rows from the MAILS2PROCESS table. An administrator can use this to great effect to test out situations on a live system without sending thousands of mails. Here are some examples: dmemail - "filter_sql=obj_uid=12345" dmemail - "filter_sql=create_date between xxxx and yyyyy" dmemail - "filter_sql=rel_class = 7" The full SQL generated is shown in the log when debug=y. Here is a typical test: dmemail - process_files=n delete_files=n "filter_sql=obj_uid>12345"
PURGE_ROWS | Value: Y or N If set to Y, then rows that are ignored by the filter used above, are purged from the table. If the FILTER_SQL specified a condition that requested only recent rows, then this would delete all the older rows. This works by inverting the condition specified with FILTER_SQL.
NO_STOPFILE | Value: Y or N Specifying this in the config file will allow the command-line program to use scheduling mode, just as if it had been started from the Dimensions pool process. The syntax is: dmemail -dmpool For this to work, you need to set up the dm.cfg variables that control scheduling.
ALLOW_MISSING_SYMBOLS | If set to Y, then the email template will expand, even if some variables are not defined. This is very useful for processing a batch of emails which have a known minor problem (such as a missing description). In place of the symbol, text will be generated as in the following example: Template before expansion: Request: %DMTEST. Email after expansion: Request: [symbol DMTEST is not defined]

Related Topics

Database Processing

Processing Options

Debugging Options

Locating Email Templates