Content Editor

The content editor allows you to edit the message content of your mail job.

The editor consists of the main panel that displays the actual editor and an additional panel with various sections on the right.

In this panel on the right, each section can be opened and closed separately, so that you only need to see the content of those sections that are currently of interest to you. Simply click on a section header to open/close this section.

The source code editor for a HTML message has two modes:

In Preview Mode you view the HTML message as it actually appears. In Code Mode you edit the HTML message by editing the underlying HTML code directly. You can switch between preview and code mode at any time with the icons at the top left of the editor toolbar.

In this editor, for a standard HTML message that is not based on a template, the panel on the right contains the following sections:

Fluid Design Widgets

This panel section shows the available fluid design widgets that you can use in the HTML content.

Fluid design (often also called "responsive design") is a design principle under which the HTML content is created in such a fashion that it looks nice and readable on a variety of email clients, both with large and small screens, on computers or handheld devices.

To add a fluid design widget to your HTML content, place the cursor at the target location, then open the widget gallery dialog by clicking the Open the Widget Gallery link and insert the desired widget via this gallery. As a shortcut, you can also click on one of the widget icons below the link, to open the gallery dialog already with the desired widget section selected.

You have the choice between several different widget types. These widgets can also be nested into each other. See here for more details about the available widget types and how to use the fluid design widgets.

Merge Fields

This panel section shows all available merge fields. Click on a merge field name to insert it into the editor at the current cursor position.

Drop-Ins

This panel section is available if drop-in content is currently enabled. It lists all user-defined and system drop-ins. (Except for the social media sharing system drop-ins, see "Social Media" section below).

Click on a drop-in name to insert it into the editor at the current cursor position. Hover the mouse pointer over a drop-in name to see a short description of what this drop-in will do. See also here.

Attachments

This panel section shows all attachments that are part of the message. You can add any number of file attachments to your message, or none at all.

To edit the current attachments, click the Change link in that section. This opens a dialog where you can upload new attachments or download or remove attachments that were added previously.

Note: The LISTSERV Maestro Administrator may limit the size of uploaded files, or limit the size of email messages. Exceeding these limits by including large or multiple attachments will cause a delivery error.

Social Media

This panel section allows you to integrate social media sharing and publishing into your email. See here for more details.

Social Media Sharing

By embedding the social media sharing icons (or similar links) into your message, you enable the recipients to easily share your message with other people, on various social media.

You can either include the full {{*SocialMedia}} system drop-in or one of the specific ShareURL drop-ins.

Click on a drop-in name to insert it into the editor at the current cursor position. Hover the mouse pointer over a drop-in name to see a short description of what this drop-in will do.

Twitter Publishing

If you have given LISTSERV Maestro access to your Twitter account, then LISTSERV Maestro can automatically publish a message for you on Twitter, at the same time as the mail job is being delivered to its normal recipients. To enable this Twitter access, go to the Social Media Settings page.

With Twitter access enabled, you can click the corresponding Change link here in the panel section in the content editor to enter the message you want to publish on Twitter. The message must contain the {{MessageURL}} placeholder. This placeholder will be replaced with a URL that points to a version of your email that can be viewed in a browser. The currently configured Twitter account is also shown. This account will be used to publish the message, unless a different account is configured before the delivery time of the mail job. LISTSERV Maestro will always use the Twitter account which is configured at the moment of delivery to publish the message. If no Twitter account is configured at the moment of delivery, then the job will still be delivered, but the Twitter message will not be published.

Content Options

On this panel section you can define various options for the content

Images

Define how the images in the HTML content shall be sent with the email content. You have two options:

As URLs: The images are included as URLs that load the images from the LISTSERV Maestro server when the email is viewed, i.e. the images are loaded from the server on-demand by the email client of the recipient.
As Attachments: The images are included in the email itself, as attachments. The email client of the recipient can show the images without the need for an internet connection to access the LISTSERV Maestro server, but the email data that needs to be transferred is considerably larger.

Note, that this choice does not apply to images that are defined with an external image reference URL, i.e. with a URL that points to an image on an external server. These images are always sent with their original external URL.

See here for a more in-depth explanation of the differences between linked images (="as URL") and inline images (="as attachment"), which also explains the main advantages and disadvantages of each type.

Language

Define the character encoding to be used to encode the email message.

If LISTSERV Maestro is being used in a single language environment, either with plain English or with one of the common (West) European languages, then the safest choice is always the ISO-8859-1 (Latin 1) encoding. It contains all 26 common characters (both in upper and lower case), numerals 0 - 9, all the common punctuation characters and the more common special characters such as '@', '+', '*', and others. In addition, it contains many of the uncommon characters required for most West European languages, such as 'ö', 'å', 'ç' and others.
See here for more information.

Drop-Ins

Enable or disable drop-in content for the given job.

If drop-in content is enabled, then you must define non-empty opening and closing tags.
See here for more information.

Alternative Text

Define if the HTML message shall include a plain text alternative (recommended) or not.

Automatic CSS Inlining

Define if automatic CSS inlining shall be applied to the HTML content of the mail job. The CSS inlining will be applied just before delivery of the job.

If the mail job's content is based on a template, then this setting is defined by the template and cannot be changed here. In this case, the CSS inlining (if enabled) will be applied to the HTML code of both the template and the user supplied editable blocks.

Automatic Email Format

Define if the full HTML message, including the plain text alternative, shall be sent to all recipients, or if the email format for each individual recipient shall be defined automatically, based on a certain condition.

If the condition is true for a recipient, then this recipient will receive the full HTML message, including the plain text alternative. If it is false, then the recipient will receive a plain text message instead, that contains only the text alternative.

This can, for example, be used to let recipients choose the type of email they prefer (HTML or plain text).
The condition must be specified in the standard LISTSERV condition syntax, similar to what is used in a LISTSERV conditional block of the type ".BB ... .EB". See the LISTSERV documentation if more information is required.

Preferably, the condition should also contain at least one merge field from the recipient data so that the condition is a variable condition whose true/false result varies from recipient to recipient. Otherwise, the condition would evaluate to the same true/false result for all recipients; all of them receiving the same content type anyway, defeating the purpose of having a condition in the first place.

Example:

Assume that the recipient data contains a merge field named MAIL_TYPE and that a value of "html" in that field means that the recipient has opted to receive HTML email. If any other value is found, then the recipient wants to receive only plain text email. The condition you specify would be the following:

&MAIL_TYPE = html

(This setting is only available for HTML content with a plain text alternative.)