spaceholder
Go to FAQ Go to More Help

messageREACH Guide

The aim of this guide is to help you use messageREACH. It is organized by topic as follows:

Introduction

messageREACH distributes e-mail messages to as many recipients as you need to reach, thousands per message if desired. Following are a few of the key features of the messageREACH service:

Top of Page

System Requirements

For optimal performance, use either of the following Internet browsers to access messageREACH:

To test whether or not your browser is correctly set up for optimal messageREACH access. Take this browser test to find out. Caution: the test logs you off messageREACH.

Top of Page

Security

Security refers to the level of Internet security in effect when you send your messages, attachments, and/or pull files to messageREACH. Security also refers to the level of Internet security in effect when message recipients download your pull files. For details on the latter, see Pull File Security.


File (and Message) Upload via messageREACH

You can send your messages, attachments, and pull files to messageREACH via either the normal or secure method, as described below:


Use either of the following Web addresses, as appropriate:

When encryption is enabled you will see the secure symbol (a closed lock icon) at the bottom of the browser screen. messageREACH will match the security level provided by your browser (40 to 128-bits).

Top of Page

Job Lifecycle

Job lifecycle covers all the phases of your job, from the time that you submit it through the time that it expires. The various phases are: Queued, Setup, Posting, Posted, and Completion. Each phase is described below.


I. Queued

When you submit a job into the messageREACH system, a job number is assigned and it is queued for the next phase, setup.

Top of Page

II. Setup

In the setup phase, messageREACH prepares your job for delivery as follows:

Can't Find Your Job? If you attempt to display job status via the Status screen during the setup phase of the lifecycle, you may not be able to locate your job if either of the following conditions is true:
  • Your job may not yet be set up. Depending on job size, complexity, and the number of recipients, setup time will vary.
  • An error may have occurred that requires human intervention. Call Customer Service to inquire about this job.

Top of Page

III. Posting

In the posting phase, messageREACH creates an individual, customized message for every recipient. It then begins to send these messages to their Internet destinations.

Messages are customized as follows:

messageREACH then forwards each customized message to the Internet mail server that handles domain mail for the destination. Once every message is on its way to its target address, a posting report is generated, if you requested one. Posting information that appears in your reports is final; it does not change over the job’s lifetime.

Top of Page

IV. Posted

The job is considered posted after at least one delivery attempt is made to each address. Just because a message has been posted does not mean that it was delivered its final destination. It does mean it was delivered to a domain mail server for the recipient. However, it may then be passed to additional mail servers along the way to its target destination. A job remains in the posted phase until the job expires.

In the posted phase of the lifecycle, messageREACH does the following:


DSNs

A Delivery Status Notification (DSN) provides confirmation that the message was received at each point along its route to the target destination. As the message is passed along, delivery status is updated according to the DSNs that messageREACH receives. (You can view DSN summaries in your detail reports if this setting is enabled in your User Profile.) Final delivery status is ultimately reached when the message expires and the DSNs indicate that either the recipient’s mail server received the message, or that delivery failed.

While DSNs are helpful, they can also be misleading. Multiple DSNs are frequently received for a single message. A delivery may appear to be succeeding over time, only to generate a final delivery status that indicates a delivery failure. This could occur, for example, if the recipient changed his/her e-mail address.

Similarly, temporary failures could suggest that delivery will not succeed, only to result in a successful delivery if temporary problem conditions (such as if a recipient’s mailbox is full) are resolved. A history of these varying statuses is not kept. An interim report only reflects the currently known delivery status, and this is only displayed if DSN reporting is enabled in your User Profile.

Sometimes, no DSNs are returned for a particular message, so status for that address is unknown. Finally, it is important to understand that DSNs can arrive out-of-sequence, suggesting that a problem exists when it does not and vice-versa. The good news is that mature Internet mail-handling practices and procedures will one day provide more certainty. Meanwhile, standards are evolving and the number of compliant systems increases every year.


Delivery

When messageREACH gets notice that a receiving domain has delivered the message to a recipient’s mailbox, the message is considered delivered to that destination. The delivery is indicated in your completion report. Delivery status is also included in your interim reports if DSN reporting is enabled in your User Profile.


MDNs

Once a message is delivered, it is difficult to know when or if this mail is actually read. In an attempt to get this information, messageREACH can request a "return receipt,” called a Message Disposition Notification (MDN). The purpose of an MDN is to return a notice when the recipient opens the message. However, responding to MDN requests is up to the recipient and/or the recipient’s mail provider. Either may choose not to approve the reply since some recipients consider it a privacy breach and mail domains often do not honor the request. Therefore, messageREACH does not request MDNs unless you specifically request them in your User Profile.

Top of Page

V. Completion

Your job is considered complete once its expiration date is reached. By default, jobs expire as follows:

JOB DEFAULT EXPIRATION
Without pull files or send-a-friend link 3 days
Without pull files and with send-a-friend link 7 days
With pull files 14 days, unless you requested a different default in your User Profile

For each pull file job that you submit, you can override the 14-day default if you wish. On the Job Submission form, select the number of days that pull files will remain accessible before they expire. To extend job expiration beyond 14 days, please contact messageREACH Customer Service.

Once a job completes, the following occurs:

Top of Page

Preparation: Before You Send a Message

Preparing your message means you must decide which format or formats to use for the e-mail body of the message, as well as getting attachments and pull files ready. You can personalize your message by using inserts, you can provide mailto links, and you can create your own links for pull files. The following topics are covered below:

Top of Page

Your Message: What Gets Sent?

Messages sent via messageREACH, like typical e-mail, are encoded in MIME format. This means that they can include multiple types of data as attachments (binary, graphics, audio, video, etc.), and that they conform to the Internet standard for electronic mail.

Messages you send through messageREACH consist of message body text, supplied by you, and any attachments or pull files you include. messageREACH adds the following:

messageREACH includes attachments in the order you added them when you submitted the job. Attachments are placed beneath the body text in a separate part of the message. (Depending on your mail program, they may appear beyond the text area of the message, but still within the message window.)

Pull file links are either positioned after the trailer text or ahead of the removal instructions at the end of the message. Alternatively, pull links are placed at locations you can specify, if you wish, in your message body text.

Top of Page

Message Body Preparation

The message body is the body of an e-mail message. That is, it is the plain text message or HTML file content displayed by the recipient’s mail program upon opening the mail item. The message body is located immediately after the To, From, and Subject fields.

messageREACH allows you to provide the message body in any of the following ways:

Although you can prepare a text file from the messageREACH Job Submission form, you will want to prepare most files in advance, especially if you are sending multipart/alternative. Follow the guidelines in the sections that follow.

If you will be using Dynamic Content to customize each message for each recipient, please read about formatting a Dynamic Content Message Body File.

Top of Page

Plain Text Files

Your message body text, like all text associated with your message, should belong to the same character set. On the Job Submission form, indicate the character set that you are using by choosing it from the Character Set drop-down list box. See Character Set for more information.

To create a plain text file, use a word processor and then save the file as a Text Only type of document, using the .txt extension. As a suggestion, you can use Microsoft Notepad or Wordpad to create the text; save the file as a Text Document.

Top of Page

HTML Files

Newer-style e-mail programs are capable of displaying HTML files in the message body. HTML is used extensively on the Internet. Unlike plain text, HTML lets you control text placement and elements such as a choice of fonts, colors, text styles, tables and underlining (underlining is NOT RECOMMENDED). HTML can also display images.

Creating HTML Files

To create an HTML file, you can generate a file with a word processor and then save it as an HTML type file. Use either the .html or .htm extension to identify the format as HTML.

Alternatively, if you are on a Windows platform, you can download the intelliSEND Wizard and use it to create HTML files. It lets you easily add graphics, pull files, attachments, clickTO's, and more. IntelliSEND requires: Microsoft Windows 95, 98, 2000, NT 3.0 or newer, or Windows Me; Internet Explorer 5.0 or newer; 5 MB hard disk space; 16 MB RAM for Windows 95/98/2000; 32 MB RAM for Windows NT 3.0 or newer.

You can also use an HTML editor to generate HTML files. Information on this type of software—available in every price range—is available on the Internet. A search on "HTML editor” provides a good starting point.

See Placing Pull Links in an HTML File for information on adding pull links.

Including Images

Please see More Help: Adding Images to an E-mail Message.

Top of Page

HTML-Lite

HTML-Lite refers to a subset of HTML; it provides some of the features of HTML, but not all of them. AOL Version 5 and earlier supports the "HTML-Lite" features listed in the chart below.

FEATURE HTML HTML-Lite
Text formatting, such as bold, italics, and underscores (Note: Underscores should be exclusively used to denote clickable links. Also, newer versions of HTML will not allow underscores.) Yes Yes
Proportional fonts and font sizes, e.g., Century Schoolbook, Lucida Handwriting, Arial; depending on the fonts you specify and those that are available to each recipient Yes Yes
Colored text, Colored backgrounds Yes Yes
Aligned text: left, right, center, justified Yes Yes
Links to Web addresses, displaying either the full path (e.g., http://www.messagereach.com) or path hidden by hyperlink text (e.g., "Click here") Yes Yes
Links to images and graphics from your server or the messageREACH server Yes No
Numbered lists, bulleted lists Yes No
Tables Yes No

Regardless of the HTML you may use in your messages, messageREACH correctly positions and formats removal instructions and a leader, trailer, or inserts, if you use any of these for your messages.

Similarly, pull file references can be placed in the text, HTML, and HTML-Lite message sections at the locations you specify. Alternately, they may be placed at the bottom of each section, or this feature can be disabled.

Top of Page

AOL's mail reader (Version 5.0 and lower) supports the following HTML tags, with some caveats as noted below:

HTML START
and END Tags
FUNCTION NOTES
<HTML>
</HTML>
Identifies everything between the tags as an HTML document  All start tags are enclosed in <brackets like this>. End tags have a forward slash after the left bracket </like this>.
<BODY>
</BODY>
Identifies the body of the document  
<BR>
no end tag
Breaks the flow of text to a new line Same result as adding a carriage return (CR) line feed (LF) to a word processor document
<P>
</P>
Identifies a paragraph  
<B>
</B>
Applies bold formatting  
<I>
</I>
Applies italics  
<U>
</U>
Applies underlining In HTML documents, it is best to use underlining exclusively to indicate clickable links.
<SUP>
</SUP>
Identifies superscript text  
<SUB>
</SUB>
Identifies subscript text  
<P ALIGN=CENTER>
</P>
Centers text between screen margins Alignment persists until the next P ALIGN statement
<P ALIGN=RIGHT></P> Aligns text at right margin Alignment persists until the next P ALIGN statement
<P ALIGN=LEFT>
</P>
Aligns text at left margin Alignment persists until the next P ALIGN statement
<P ALIGN=JUSTIFY>
</P>
Justifies text between screen margins Alignment persists until the next P ALIGN statement
<A HREF="xxx"> Alias
</A>
Creates a clickable link to a specified Web address "xxx" = actual Web address, and Alias = link text. For example:
<A HREF=www.xyx.com>Click here</A>
<A HREF="yyy"> Alias
</A>
Creates a clickable link that opens user's e-mail program and a new mail item addressed to the mailto address "yyy" = actual e-mail address, and Alias = link text. For example:
<A HREF="mailto:abc@123.com>Click here </A>
<BIG>
</BIG>
Formats text in a large font  
<SMALL>
</SMALL>
Formats text in a small font  
<FONT SIZE=2 PTSIZE=8>
</FONT>
Sets point size at 8 if using AOL. For full HTML, omit the PTSIZE specification. For example, <font size=2>. Effective until next font statement
<FONT SIZE=3 PTSIZE=9>
</FONT>
Sets point size at 9 if using AOL. For full HTML, omit the PTSIZE specification. For example, <font size=3>. Effective until next font statement
<FONT SIZE=3 PTSIZE=10>
</FONT>
Sets point size at 10 if using AOL. For full HTML, omit the PTSIZE specification. For example, <font size=3>. Effective until next font statement
<FONT SIZE=4 PTSIZE=11>
</FONT>
Sets point size at 11 if using AOL. For full HTML, omit the PTSIZE specification. For example, <font size=4>. Effective until next font statement
<FONT SIZE=4 PTSIZE=12>
</FONT>
Sets point size at 12 if using AOL. For full HTML, omit the PTSIZE specification. For example, <font size=4>. Effective until next font statement
<FONT SIZE=5 PTSIZE=14>
</FONT>
Sets point size at 14 if using AOL. For full HTML, omit the PTSIZE specification. For example, <font size=5>. Effective until next font statement
<FONT SIZE=5 PTSIZE=16
</FONT>
Sets point size at 16 if using AOL. For full HTML, omit the PTSIZE specification. For example, <font size=5>. Effective until next font statement
<FONT SIZE=5 PTSIZE=18>
</FONT>
Sets point size at 18 if using AOL. For full HTML, omit the PTSIZE specification. For example, <font size=5>. Effective until next font statement
<FONT SIZE=6 PTSIZE=20>
</FONT>
Sets point size at 20 if using AOL. For full HTML, omit the PTSIZE specification. For example, <font size=6>. Effective until next font statement
<FONT SIZE=6 PTSIZE=22>
</FONT>
Sets point size at 22 if using AOL. For full HTML, omit the PTSIZE specification. For example, <font size=6>. Effective until next font statement
<FONT SIZE=6 PTSIZE=24>
</FONT>
Sets point size at 24 if using AOL. For full HTML, omit the PTSIZE specification. For example, <font size=6>. Effective until next font statement
<FONT SIZE=7 PTSIZE=26>
</FONT>
Sets point size at 26 if using AOL. For full HTML, omit the PTSIZE specification. For example, <font size=7>. Effective until next font statement
<FONT SIZE=7 PTSIZE=28>
</FONT>
Sets point size at 28 if using AOL. For full HTML, omit the PTSIZE specification. For example, <font size=7>. Effective until next font statement
<FONT SIZE=7 PTSIZE=36>
</FONT>
Sets point size at 36 if using AOL. For full HTML, omit the PTSIZE specification. For example, <font size=7>. Effective until next font statement
<FONT SIZE=7 PTSIZE=48>
</FONT>
Sets point size at 48 if using AOL. For full HTML, omit the PTSIZE specification. For example, <font size=7>. Effective until next font statement
<FONT SIZE=7 PTSIZE=72>
</FONT>
Sets point size at 72 if using AOL. For full HTML, omit the PTSIZE specification. For example, <font size=7>. Effective until next font statement
<h1>
</h1>
Applies Heading 1 formatting Large, bold, indented heading
<h2>
</h2>
Applies Heading 2 formatting Small, indented heading
<h3>
</h3>
Applies Heading 3 formatting Italicized heading
<FONT FACE="BOOKMAN">
</FONT>
Changes text to the specified font face Can be included with Font Size and PTSize commands
<FONT COLOR="#FF0000">
</FONT>
Changes text color to the specified color Colors can be specified using their Red, Blue and Green (RGB hexadecimal) values. For example, black is the absence of color: #000000; white is all colors: #FFFFFF; #FF0000 is red, #00FF00 is green, etc.
<BODY BGCOLOR="#FFFF00">
</FONT>
Changes background color to the specified color Same as above

Additional Notes:

  1. The table above is neither complete nor a wholly accurate representation of the HTML supported by AOL.

  2. Other standard HTML tags, including comments, are not supported by AOL version 5.0 and under. For example, if you add comments in the source HTML code, both the HTML tags and the comments, which look like this: <!— comments go here —> are incorrectly displayed to the user.

  3. Forms and table tags are not rendered in AOL version 5.0 and under.

  4. Tags for ordered (numbered) lists and unordered (bulleted) lists are not supported in AOL version 5.0 and under.

AOL versions 7+ support full HTML. However, there is no way to know which mail reader an AOL recipient is using unless you test. See more help. The same is true for CompuServe recipients with an address of the type *@cs.com.

Top of Page

Multipart/Alternative

Multipart/alternative means that instead of simply sending the message body in a single format, you can send it in multiple formats, Text and HTML.

Recipients of multipart/alternative only see the format that their mail programs can display, although some e-mail programs may display both the HTML and the text versions in different sections of the message. Multipart/alternative eliminates the need to create separate address lists for different users who have different mail capabilities.

If you include both a plain text and html version of your document, messageREACH will automatically generate the Multipart/Alternative message body for every delivery, except for the AOL and Compuserve US destinations. Those destinations will receive the HTML-Lite version (if available), or the plain text version, unless you specifically request the format using the "eformat" field.

Since HTML-Lite does not support tables, you may use workarounds—such as adding spaces in an HTML-Lite message to simulate column spacing in a table. However, such HTML-Lite oddities do not display as expected in true HTML-enabled mail programs. The spaces, in this case, would be removed. What appears to be a column format in an AOL mail viewer will not have the extra spaces in a true HTML reader. Therefore, be sure to provide an HTML version of your file for HTML-enabled recipients.

The chart below informs you of what each of your recipients will likely see, depending on the message body versions you send and the recipient's e-mail capabilities.

Top of Page

IF YOU SEND AOL USERS SEE OTHERS SEE NOTES
Text Text Text Recommended. Plain text to all.
Text
HTML
HTML-Lite
HTML-Lite Text or HTML Recommended. HTML-Lite to AOL users; plain text and/or HTML to others.
Text
HTML
Text Text or HTML Not recommended for AOL users since only messageREACH links will be clickable. If you included other links, they will not work for AOL users.
Text
HTML-Lite
HTML-Lite Text or HTML-Lite HTML-Lite to AOL users; plain text and/or HTML-Lite to others. HTML-Lite is not recommended for true HTML-enabled users, who may not see the file as it appears to AOL users.
HTML HTML HTML Recommended for lists of only HTML users. Plain text recipients get HTML code, which most users will find unreadable; also, HTML may not display correctly to AOL users.
HTML-Lite HTML-Lite HTML-Lite Recommended only for lists of AOL users. Plain text recipients get HTML-Lite code, which most will find unreadable; HTML-Lite may not display correctly to others.
HTML
HTML-Lite
HTML-Lite HTML Recommended only for lists of AOL and HTML users. Plain text recipients get HTML-Lite code, which most will find unreadable.

Top of Page

Plain text is the default alternative if the recipient's mail program cannot display either of the HTML formats. Sending multipart/alternative assures you that at least the text version of your messages can be read by your recipients. Sending HTML-Lite assures you that AOL users will still be able to see an HTML-style message.

When you create multiple versions of your message, the content can be similar or completely different for each version, depending on the information you need to communicate and how you want it to appear. For example, you might arrange information in a table for HTML-enabled users. However, you might simply list the information without using a table for other recipients since plain text and HTML-Lite cannot display table formatting. Or, keep the message body simple and send more complex pages as either attachments or pull files. See HTML and HTML-Lite for more information on these formats.

Top of Page

SMS Message Body Text

You can type your SMS text message right into the text box provided or you can cut and paste your message from a word processing program or a text editor like Notepad. You will see the number of characters in your message appear in the counter to the top right of the text entry box.

SMS text messages can be personalized using inserts.

The standard SMS message size is 160 characters. If your message is larger, it will automatically be broken down into smaller 160 character segments as needed. Each segment will be delivered to the recipient.

Choosing the Delivered Message Body Format

As explained above, messageREACH normally delivers the message in the input format (if only one format is input) or multipart/alternative if both plain text and HTML are input, and HTML-Lite to AOL and CS domains (if HTML-Lite is input).

While this covers most situations with completely readable results, it is not perfect because:

  1. Multipart/alternative is larger than sending text or HTML alone
  2. It forces HTML-lite to AOL and CS domains even for those destinations that have version 6 or 7 which can read full HTML. Such recipients can also read images, therefore giving you the ability to know the message was opened.

MessageREACH lets you choose the delivery format if your address list contains a field with the keyword of eformat. Valid values for this field are: text, HTML, HTML-Lite, default (or null - no value). For values of default (or null), messageREACH contines to deliver multipart/alternative to all address except the AOL and CS domains, and HTML-Lite to the AOL and CS domains. But for destinations with listed values of text, or HTML or HTML-Lite, messageREACH delivers only that format - again this assumes you have input all 3 message body types.

How do you know what format to deliver to each destination?

The best way is to ask each recipient what format they would prefer when they opt-in.

Top of Page

Using Inserts to Personalize Your Message

You can personalize the message body text — or any attachment or pull file that's in text or HTML format. By using inserts, each recipient gets a copy of the message (or attachment or pull file) with data inserts that were specifically tailored to that person. Note the restrictions in the chart below:

Maximum Insert Fields
Maximum Characters Per Insert
999

  • 255 - for message text and attachments (recommended)
  • 180 - for pull files (maximum allowed)

A line of text is limited to approximately 990 characters, the maximum line length that messageREACH can generate. Lines exceeding this limit may be truncated. Most e-mail readers normally wrap lines for the current screen size. Since inserts are included within each line, the 255 character maximum per insert is recommended. There is a 180 character maximum on inserts for pull files.

If you need more than 180 characters, you either need a new feature, or break the field into multiple inserts.

Where To Add Inserts

To add inserts to an attachment or pull file, add them directly to those files. To add inserts to body text, you can do so when you create the job or when you prepare your files to be included with the job, as follows:


How To Add Inserts

Insert numbers correspond to the numbered INS# data in an associated address list. (See Inserts for help on adding insert data to a list.) You can repeat insert numbers within the same message if you wish to position the associated text in multiple places.

Example

Enclose the insert number—preceded by the uppercase letter I (for "Insert”)—in parentheses, as in the following example:

I personalized this message to you, (I3), by using inserts. I am pleased to announce your 40% raise; your new salary is (I4). Congratulations!

You can add inserts wherever each insert is desired. messageREACH replaces the inserts with the corresponding data you defined in the list. For example, the recipient named Joy Baker might get this version of your message:

I personalized this is message to you, Joy Baker, by using inserts. I am pleased to announce your 40% raise; your new salary is $150,000. Congratulations!

Note that inserts affect line lengths; they may cause unexpected line breaks. Also, some mail programs may wrap text at odd points due to the way carriage returns are added by the sending or receiving system.

Top of Page

Providing Mailto: Links

Recipients cannot directly reply to you using their mail program’s reply feature (although messageREACH receives such replies and forwards them to you). Nonetheless, you have the option of providing a direct "mailto:” link within the message body text.

When a recipient clicks a mailto: link, their e-mail program displays a new mail item for composing a message. The destination address associated with the link automatically appears in the To: field, so the mail can be sent directly to you.

How to Create a Mailto: Link

The syntax varies, depending on whether you are adding a Mailto: link to a plain text message body or an HTML file. Follow the directions below.

Plain Text File

To include a mailto: link in a plain text message body, type "mailto:” followed by the complete e-mail address. Do not add any spaces between mailto:and the address. Do not underline the text; the recipient's mail program will do that. For example:

For more information, send mailto:me@mycompany.com

Most e-mail programs will correctly display the text as a link.

HTML and HTML-Lite

To include a mailto: link in an HTML or HTML-Lite message, type the entire <a href command that follows (see below), substituting your e-mail address for each instance of youraddress@somewhere.com:

<a href="mailto: youraddress@somewhere.com">youraddress@somewhere.com</a>

For example, using this syntax with an actual e-mail address may look similar to the following:

<a href="mailto: myaddress@work.com">myaddress@work.com</a>

It displays a link that looks similar to this: mailto: myaddress@work.com


 

Note: In HTML (versus plain text), you can optionally add a space between "mailto:" and the address. (Remember: No space is allowed when creating mailto:links in a plain text file.)




Top of Page


Pull File Types

There are 3 different types of "Pull Files" that messageREACH can generate and report on. They are:

Standard Pull File
This is the conventional pull file that represents any file you want to give the recipient the opportunity to download via their browser rather than sending the file as an attachment. There is no restriction on the file type or file size. The syntax required in the message body is [pull name=filename.ext]. Each destination gets a unique web URL to pull the file. Each time a recipient clicks on the link to pull the file, this fact is reported separately in the detail or pull report.

Click-TO file
This is the standard link that redirects the recipient to your requested web location. This is reported separately on the detail or pull report. Each destination gets a unique web URL for each Click-TO address. Each time a recipient clicks on the link to visit that address, this fact is reported separately in the detail or pull report.

Job-level untrackable pull file
This is a link to the requested pull file, but the link is the same for every destination. MessageREACH can only report the total number of pulls for such files. The syntax required in the message body is [untrack-pull name=filename.ext]

Why use untrackable pull files?
Usually when sending HTML messages you will use one gif or jpeg image which is automatically pulled into the message when the recipient opens the message. This gives you the HTML open information. If you have additional images in your message, having separate tracking is a waste of space in the detail/pull files (2 extra columns for each file). Using the untrack-pull filename means these images will not appear in the detail/pull file, but will show the total pulls in the summary section. See Reports.


Top of Page


Preparing Your Own Links for Pull Files

(Optional) messageREACH automatically adds pull file links into your message body. The links are added at the end of the message, just before the removal instructions. However, if you wish, you may specify the link names yourself and position them at locations you indicate in your message body.

To specify link locations in a plain text message body, see Placing Pull Links into a Plain Text Message. You can specify both the link locations and the link text if you use HTML for the body; see Placing Pull Links into an HTML File.

Top of Page

Placing Pull Links into a Plain Text Message

Use the following syntax to specify pull file link locations in a plain text message:

[pull name=filename.ext]

messageREACH will complete the links for you when you submit the job. Do not use spaces on either side of the equal sign, i.e., between "name” and the equal sign or between the equal sign and your file name.

To add the file size to a link (if desired), use the following syntax:

([pullsize name=filename.ext])


NOTICE THE SYNTAX USED IN THE FOLLOWING EXAMPLE:

This is my message body text. Download the sales report by clicking this link [pull name=filename.ext], which displays the full URL path to my file. Adding the file size is optional. I can add it here: ([pullsize name=filename.ext]), although it is usually better to position it after the name of the file, like this: [pull name=filename.ext] ([pullsize name=filename.ext]).


IT PRODUCES THESE RESULTS: (Please ignore any unusual text-wrapping; line breaks would not ordinarily appear before and after each link.)

This is my message body text. Download the sales report by clicking this link
http://pull.messagereach.com/1-D627/54444/salesreport.html which displays the full URL path to my file. Adding the file size is optional. I can add it here:
(389 Kb) although it is usually better to position it after the name of the file, like this:
http://pull.messagereach.com/1-D627/54444/salesreport.html (389 Kb)

Top of Page

Placing Pull Links into an HTML File

In addition to specifying the locations for your pull file links, HTML allows you to substitute your own link text for the pull file's URL path. (messageREACH adds the URL, but the URL can be hidden by your link text, if desired.)

The instructions vary for placing a pull link into the source code of an HTML file, depending on the software you are using. See the general guidelines immediately below. Then see the more specific instructions that follow, depending on the text editor or word processor you are using.

Top of Page

General Guidelines

Regardless of the application software you use to insert pull links, follow these general guidelines:

  1. To ensure that your links can be easily read by your recipients, do not use spaces in your pull file names. For example, instead of my file.doc, use myfile.doc or my_file.doc. Otherwise, the spaces are automatically replaced with characters that your recipients will find confusing. For example, my file.doc produces my%20file.doc, which is less readable than my_file.doc

  2. To specify the location of the pull file's URL reference within an HTML <a> statement, use the following syntax:
    [pull name=filename.ext].
    Do not use spaces on either side of the equal sign, i.e., between "name” and the equal sign or between the equal sign and your file name.

  3. To add the file size to a link (if desired), use the following syntax:
    ([pullsize name=filename.ext])

To add the pull links to an HTML file, you can use an HTML text editor or other application software. Instructions follow, including how to use Microsoft Word 97, Microsoft Outlook, Netscape Messenger, or Microsoft Word 2000 to add the links.

Top of Page

Adding Pull Links with an HTML Editor

If you know how to write or edit an HTML file, use the syntax in the following example to insert a link:
<a href=”[pull name=myfile.html]”>Download myfile</a> ([pullsize name=myfile.html])

When using the syntax above, replace myfile.html with the name and extension of your pull file. Then, instead of "Download myfile”, substitute the name of the file, or the specific text you wish to use for the link text.

If you used this sample link in your HTML body text (and submitted a pull file called myfile.html), the link text displays as follows in the recipient’s e-mail program:
Download myfile (1.76 Kb)

The file size, of course, depends on the size of the pull file; messageREACH will display the correct file size. Leave out the syntax for the pull size if you prefer not to display the file size to your recipients.

Top of Page

Adding Pull Links and Saving as HTML in a Word Processor or E-Mail Program

Adding the syntax for a pull file is essentially the same whether you are creating the HTML file in a word processor or e-mail program. The following instructions are general enough that you can apply the concepts regardless of the application you are using. However, the following steps are particularly appropriate if you are using Microsoft Word 97, Word 2000, Netscape Messenger, or Outlook Express Version 5. (Outlook Express users: Previous versions of Outlook will not create HTML; however version 5 is available free from Microsoft.)

Follow these instructions:

  1. Create the body text in the application you choose. Ignore the To, From and similar heading fields if you are using an e-mail program to create the HTML file.
    Note to Outlook Express 5 users: In the Format menu, click the HTML selection to be sure it is active. It is active when a marker appears to the left of the selection.)

  2. Add the link text to the body by typing the desired text wherever you want it to appear. This text will substitute for the pull file’s URL path. For example, you can simply name the file, or type additional text for the link such as: "Click here for the xyz file.”

  3. Select (highlight) the link text by clicking the first character and dragging your mouse as you continue to hold down the mouse button.

  4. From the Insert menu, choose Hyperlink (or simply "Link”). If you are using Word, you are asked if you wish to save the file before inserting the hyperlink. Saving the document at this point is optional; save it as a Word document if you wish. You will later save it as an HTML file.

  5. In the link field—which may be labeled Insert, Link, Link to file, URL, or a similar name—type the link syntax as described in the General Guidelines section of this topic.

  6. Click OK. The link text is displayed as an underlined hyperlink in the body text of your document.

  7. Repeat steps 2-6 to create additional links.

  8. Choose Save As (or Save As->File) from the File menu.

  9. In the Save As Type field, choose the HTML option (or .html, or .htm) from the drop-down list. You may need to scroll through the list to find it.

This file is now ready to submit with your messageREACH job.

Top of Page

Address List Creation

This help topic describes address list creation and formatting. messageREACH lists contain the e-mail addresses of your recipients, and each list must be properly formatted. Although not mandatory, adding a reference (for example, a recipient’s name) to each address in a list helps you easily identify the recipients. A list frequently contains other information as well; see List Contents for details.

Currently, if you wish to submit a list at the same time that you submit a broadcast, the list must be in CSV file format (that is, Comma Delimited—also called Comma Separated Value). At other times, you can upload lists in either a CSV or CDL format. Details about both list formats follow.


CSV: A Database Export File

CSV format is used as a portable representation of information typically stored in a database. When you export data from a database, each row (each line) in the resulting CSV file represents one entry or record in the list. Cell data, that is, each field in a record, is separated by commas. Commas may be followed by spaces and/or tabs, but these are optional, and messageREACH ignores them. If a field includes a comma, the whole field must be surrounded with double quotes so that the comma is not mistaken for a field delimiter.

Most database software provides online help for saving information in CSV format. It is often as simple as selecting a .csv extension in the Files of Type field in a Save As window. However, the column headings must match those required by messageREACH so that your data is properly applied.

Top of Page

CSV List Contents

Your CSV file must use the column headings (field names) understood by messageREACH. They are described in the following chart:

COLUMN HEADING DESCRIPTION VALUES USAGE
Addr A recipient’s e-mail address or the name of a list stored at messageREACH A valid e-mail address or list name Required
Ref A unique reference supplied by you for each address in the list. Typically, it names the recipient to help you easily identify the recipient's address. Up to 20 printable characters, including spaces, from the Latin-1 character set (ISO-8859-1) Optional, but recommended to help you easily identify each address
Type messageREACH descriptor for the type of address Internet for an e-mail address; List for a list name; SMS for an SMS Message Required if the list contains one or more ‘list’ addresses; Optional if entire list consists of e-mail addresses
INS# (or INS_# ) Insert text Any characters from the character set you select for your list Optional
Password The password used by this recipient to retrieve pull files that you have protected by password Any ASCII characters Optional, unless you have required a password for this recipient.
Eformat The preferred email format of the message body the recipient will receive. Leaving the field empty or setting it to "default" will send a multipart message body rather than just a single message body if it would do so normally. text, html, html-lite, or default Optional. It can be left blank for some recipients and filled in for others.


Top of Page

CSV Formatting

Once exported from a database, a valid CSV file includes column headings on the first line, with corresponding data on each line beneath the column headings. (For more information on CSV and CSV export files, see Address List Creation.) The CSV column headings do not have to graphically align with the data that follows. However, the order of the data in each row must match the order of the columns. Also, the number of items on each line must match the number of columns. If a row has no data in a particular column, an extra comma must be used to indicate that the column has no data.

Sample Email CSV List

The sample CSV list displayed below consists of five lines. The first line contains the column headings for eight columns; the remaining lines contain the data for each column.

Here is the sample list:

Ref,Addr,INS_1,INS_2,INS_3,INS_4,INS_5,INS_6
JB,jbach@music.org,J.S. Bach,Z Systems,12 Fugue Blvd,Suite 1,Santa Fe,NM
Penney,Layne@xyz.com,Penney Layne,XYZ Company,101 Abbey Rd.,,London,England
Miles D,miles@daevis.com,,,100 Park Av,New York,NY,
Ruby Smith,rs@abc.com,ABC Systems,123 Main Street,Suite 100,"New York, NY",

The eight columns in this sample are as follows:

Line 3 above begins with Ref column data: "Penney." Proceeding to the right on line 3, the Addr column has this data: "Layne@xyz.com", followed by INS_1, INS_2 and INS_3 data. However, there is no data for the INS_4 column (the data field between "Abbey Rd." and "London"). A placeholder—a comma—was added in lieu of the missing field data. This ensures that messageREACH puts the data that follows into the correct column. Therefore, "London,” correctly corresponds to INS_5, and "England" corresponds to INS_6 not to INS_4 and INS_5 respectively.

Similarly, on the next line, the INS_3, INS_4 and INS_8 fields have no data, so placeholders are added: the extra commas.

To include a comma within a single column of data, enclose the data in quotes as in "New York, NY" on the last line above. Notice that INS_8 on this line has no data—indicated by the placeholder comma. INS_7 contains both the city (New York) and the state (NY). "New York, NY" is enclosed in quotes since it includes a comma as part of the actual data. The quotes distinguish the comma used within this field from the commas used between fields of data. In summary, to include both New York and NY, with a comma in between, use quotes around the data as follows: "New York, NY".

Sample SMS CSV List

At minimum, the CSV file must include columns for “TYPE” and “ADDR”. You should have the “TYPE” column filled with the text “SMS” if you are sending to a wireless device. If you are sending to an email address, the "TYPE" must be INTERNET.

The other column must be ADDR that either includes the SMS phone number or the email address.

The SMS phone number can include dashes (-); they will just be stripped out before sending.

The SMS phone number CANNOT include spaces or parenthesis.

It is important to note that the SMS phone number should be entered in the format required to dial based upon your locality. In other words, if the you are an US user and want to send to Europe, the SMS address would be configured like “01146xxxxxxx”. If you are a US user and you want to send to a US destination, the address needs to be configured as "215555XXXX". If the you are a European user, the SMS address would be configured as “001xxxxx” for international dialing.

The following is a sample csv file of a US-based list:

TYPE, ADDR
SMS,5619262738
SMS,011441904564010

The following is a sample csv file of a mixed US-based list:

TYPE, ADDR
SMS,5619262738
SMS,703-615-3304
SMS,011441904564010
INTERNET,l.henry@xpedite.com
INTERNET,juicemon@jamminnectars.com

Please note:  If an e-mail address is entered with an SMS type setting, that entry will be ignored.

 

Top of Page

List Names

Follow these specifications when naming your lists:

The exclamation point " ! " and the pound sign " # " are reserved for a special use in list names. See List Names Preceded by " ! ” or " # ’ for more information.


List Names Preceded by " ! ” or " # ’

After you upload lists to messageREACH, you will notice that when you choose lists from the List Selector window, an additional character may precede the list name. messageREACH adds the character to distinguish between two types of lists: user-level or customer-level lists.

User-level list names are preceded by an exclamation point. For example, "!mylist” indicates that "mylist" is a user-level list. Customer-level lists are distinguished by a pound sign " # " preceding the list name. For example, "#myOtherList" indicates that "myOtherList" is a customer-level list.

Whether the lists you upload to messageREACH are automatically classified as a user-level or customer-level lists is determined by the list default in your User Profile setting. When you send jobs and type list names directly into the List field, you do not need to use a list prefix—unless you happen to also have (and wish to use) a user- or customer-level list that has the same name!

Top of Page

Inserts

Inserts allow you to customize your messages for each recipient. To do this, you enter specific data for each recipient to correspond with each insert number in a list. Then, when you create the message you wish to send, indicate the locations for each insert number. (See Using Inserts to Personalize Your Message for more information.) The insert numbers are replaced by the text you assigned for each recipient in the outgoing message.

Insert Character

Inserts should be based on the language your recipients understand. Choose from among the supported languages or character sets. See Character Set for more information. On the Job Submission form, indicate the character set you used.

When you send a message that includes inserts, the insert text is converted (if possible) to the character set you selected on the Job Submission form.


Top of Page

Comma Delimited (CDL) Format

A list to be uploaded via List Services may be in CDL format. This format displays each field enclosed in quotes and separated with commas. Each line has the same number of fields, with the first line containing the field name.

A example of a valid List CDL File is the following:

"Ref","Addr","INS_1","INS_2","INS_3","INS_4","INS_5"
"1","jsmith@aol.com","John Smith","ABC Systems", "123 Main Street","Suite 100","New York, NY"
"2","bob@abc.com","Bob Jones","ABC Company",,"101 Broadway","New York, NY"
"3","rgreen@revlon.com","Ralph Green","Revlon","100 Park Ave.","","New York, NY"

Note that for the record with Ref = 2 above, the INS_3 field is missing - there is no value between the commas.
For the record with Ref =3, the INS_3 field has a null value between the double quote (which is accepted).

Top of Page

List Services

List Services displays links for managing your lists. Open List Services from the List Services link in the left panel of the main messageREACH window. Then click a link to access the available list services described below.


Directory of Lists

The Directory of Lists displays the names of all your available lists. For information about a character that may precede a list name, see List Names. The Directory of Lists also provides links to list content and to the upload, download, and remove functions. You can do all of the following:

Note that the modification time reflects the date and time that the list was last updated.

Top of Page

List Display

List Display lets you view the selected list. The displayed list is organized into columns that correspond to your list headings.

  1. List Name: Type the list name - the name you provided when the list was uploaded to messageREACH. (You do not have to enter a leading "!" or "#" symbol.)

  2. Click Display.

Note: You can also view the contents of any list by clicking the list name in the Directory of Lists.


List Download

List Download allows you to retrieve a copy of a selected list from messageREACH. Downloaded lists are formatted in organized columns as described in the List File Contents section of this guide.

  1. List Name: Type the list name - the name you provided when the list was uploaded to messageREACH. (You do not have to enter a leading "!" or "#" symbol.)

  2. Enable the radio button that corresponds to the file type, either CSV or CDL.

  3. Click Download.

  4. In the Save As window, choose a location for the download file, then click OK. The file is downloaded to the specified location.

Top of Page

List Upload

Use List Upload to send address lists to messageREACH. Lists must be text files in either CDL format or CSV format. See List File Contents for file format information.

  1. List Name - Type a name for the list you wish to store at messageREACH.

  2. Insert Character Set - Specify the character set of your inserts.

  3. Enable the radio button that corresponds to the file type, either CSV or CDL.

  4. Enable the Strict Checking checkbox if you want messageREACH to validate that all rows have the same number of data fields.

  5. File Name - Type the exact path and filename for the list you are uploading, or click Browse and locate the file.

  6. Click Upload to send the file to messageREACH. You are notified regarding upload success or failure.

Once the list has successfully uploaded, you can use it for message delivery. (Indicate the list or lists you wish to use on the Job Submission form.)

Top of Page

List Removal

List Removal instructs messageREACH to delete the named list. Once deleted, the list is no longer available for use with messageREACH unless you upload it again.

  1. List Name: Type the list name - the name you provided when the list was uploaded to messageREACH. (You do not have to enter a leading "!" or "#" symbol.)

  2. Click the Delete the list button to remove the list. You are not given a confirmation notice; the list is simply deleted. You are notified regarding the success or failure of the list deletion.


Removal Report

Click this link, then enter an e-mail address for the report and click the button. A removal report will be sent right away.

Top of Page

Email Job Submission

The Overview section, immediately below, outlines the sequence of steps for sending a message (submitting a job) from the messageREACH Web site. Details about filling out the job submission form are located in the Details section that follows the Overview.


OVERVIEW

To access the job submission form if it is not already displayed, click the Job Submission link in the left pane of the messageREACH Web site. Then, follow the steps below to send a message. (See Details for more information about these steps.)

  1. Check User ID

    Be sure your User ID is displayed to the left of the form. Some browsers and Internet servers may cache this page from a previous system user. Or, if your browser is Netscape Navigator(R) and you are accessing messageREACH through a proxy server, your ID may not appear at all. To resolve this problem, see "Why isn’t my User ID displayed...” in the messageREACH FAQ.


  2. Provide one or more addresses (Lists, Local List, Additional Addresses) to which the message will be sent

    You must specify at least one address for your message; the address (or list name) is indicated in any of the first three fields on the form: Lists, Local Lists, Additional Addresses. The address can be one or more lists stored at messageREACH, one locally-stored list, one or more individual addresses, or any combination of the above.

    Note: If you are registered for Subscription Management, you will not see the above list boxes. Instead you will see a box to enter one or more subscription management query names, or you can use the browse button to view and select the query names. When using Subscription Management queries, you are not permitted to send to other lists or ad-hoc addresses. If you want to "test" a message to view its results prior to actually sending it to a query list, you should set up a "test" query that has for its selection, only your test addresses.


  3. Indicate whether or not to Skip Duplicate Addresses

    Choose Yes or No to turn on or turn off duplicate-address processing. Choosing yes will cause duplicate email addresses to be skipped so those recipients will only receive one copy of the message. All other entries of the same address will show "DUP" in the posting column instead of "Post" indicating the message to this address has been discarded.


  4. Optionally provide a Subject, Customer Reference, and/or Billing Code

    You can enter text for the e-mail Subject field for the out-going message. You can also enter a customer reference and/or a billing code.


  5. Indicate whether or not to enable the automatic Send-a-friend feature

    Choose Yes or No to turn on or turn off the Send-a-friend feature. Send-a-friend provides recipients with a way to send a copy of your message to their friends, who may then opt to be included on your distribution list.

    If you change the drop-down box to YES, a send-a-friend link will be added at the end of the message text, before any trailer or remove block text. The send-a-friend link will be preceded by:

    Plain text version:
    "To send a copy of this message to your friend(s) click on the following link: URL Link"

    The HTML and HTML-Lite version:
    "To send a copy of this message to your friend(s) click here."

    Note: This is the automatic send-a-friend feature. You can insert a send-a-friend link anywhere in the message body, using your own introduction text by using the (mr_sendafriend) token. If you do, you should not change the drop-down box to YES - because then multiple send-a-friend links will be in the message body.

  6. Indicate whether or not to enable the HTML Open Tracking feature

    This feature allows you to track whether an HTML recipient has "opened" your message or viewed it in the preview pane of the receiving e-mail software.


  7. Provide text for the body of your message

    Click the Select Message Body Files button to choose one or more message body files, or click Edit Or Create Body Text to create a new text file. If you choose to send the body of your message in multiple formats (i.e., multipart/alternative), each recipient automatically sees an HTML version if their mail program can display it; otherwise, they see the plain text version if you have sent multipart/alternative. See Message Body Preparation for more help.


  8. Specify Attachments and Identify Pull Files, Pull Security, and Pull Expiration

    Attachment files are delivered to all recipients with the message body. Pull files are not automatically sent; instead, the recipient can optionally download them from the messageREACH server. See Attachments, or (Pull) Files to be Stored for details.

    NOTE: You can use any combination of up to 290 attachments, pull files, and messageREACH Click-TO links in a single message. If you include links to images stored on the messageREACH server, be sure to count them as pull files.


  9. Schedule Future Delivery if Desired

    Your message is sent right away if you leave the default "No" setting set to "No". Otherwise, choose "Yes" and indicate the delivery date and start time.

    Note: You should not schedule a job more than 24-48 hours in advance. The reason for this suggestion is that the job is prepared at input time for all the destinations, and put on hold until the scheduled time. If during this time, a recipient of a previous message asks to be removed, that address will be blocked for future messages, but not the one(s) already in the system that are scheduled for delivery.


  10. Select Report Options

    Choose the types of reports you wish to automatically receive, if any.


  11. Click Submit

    Your job is submitted to messageREACH when you click the Submit button.


Top of Page

DETAILS

Each of the fields on the messageREACH Job Submission form is described in detail beneath the corresponding field heading below. (See Overview for general information.)

Top of Page

Pull Files: What Recipients See

This topic describes how recipients can access your pull files. Most modern e-mail software recognizes hyperlinks and properly displays the links to your pull files. The recipient then clicks a link to access the associated file.

When a pull link is clicked, the following events occur:

Top of Page

Job Status

For job status information, access the messageREACH Status Request form by clicking the Status link in the left panel of the main messageREACH window. The Status Request form allows you to check the status of jobs currently in progress as well as those jobs that were completed within the last 60 days. Note: Although status is displayed for up to 60 days, the resubmit function is only available for up to 2 days after the job ends.


Report Parameters

You can select the activity period for the search. The period can range from any jobs submitted in the past hour to those submitted up to an allowed maximum number of days.


Report Filters

You can narrow a search by entering the billing code or the customer reference you assigned to the job (or enter both), or by simply entering the job number that was provided when you submitted the job. You can also specify the order of the display: from oldest to newest or the reverse.

After selecting the search parameters and/or filters, click the Submit Query button. A delay occurs while messageREACH searches for jobs matching your query. During busy periods, the query may take several minutes to complete.

Top of Page

Activity Summary

The Activity Summary form displays summary information for each job, whether completed or still active. It lists the customer reference, billing code, list names, number of items (destinations), when messageREACH received the job, when delivery attempts were started, the current job status, and the job priority you assigned. Finally, if the job is still active, the Optional Action column displays a Cancel link (which lets you cancel the job if need be). For both active jobs and completed jobs, a link to Resubmit the job is displayed. This link lets you resend the job.


Canceling Jobs

Clicking the Cancel link opens a confirmation screen. If you confirm that you want to cancel the job, a request is sent to messageREACH to cancel the job as soon as the request is received. If the deliveries have not begun (such as in a scheduled job where the start time has not been reached), then it is possible to cancel the job before any deliveries are posted. If the job has begun, you can only cancel the deliveries that have not yet been posted.


Resubmitting Jobs

The resubmit request form allows you to submit a new job based on an existing job. The new job will have the same message body text and attachments or pull files as the original job, but all other job options can be changed.

If a "Job Group" link appears in the Job Number column, you submitted the original request as a job group. The resubmit option is not available for entire job groups. However, you can resubmit any of the components (the "children" of the job group), by clicking the Job Group link. The individual jobs in the group are displayed, and you can then click Resubmit for each "child" job you wish to resubmit.

Top of Page

Reports

messageREACH reports include posting reports, interim reports, completion reports and CSV reports. In addition, the specific report types are: Summary, Detail, Pull, Exception, and Bad Address reports. All these reports are described in this help topic. Also covered is How to Get a Report, and an analysis of Report Content.

Send-a-friend reports are simply Detail or Summary reports. They report on the new job created when recipients use the Send-a-friend feature to forward your message to their friends. In accordance with our anti-SPAM policy, the addresses of the send-a-friend recipients are not disclosed unless those individuals choose to be added to your list.

NOTE: Removal Reports are covered in the Address List topic; these reports are accessed via List Services. An HTML version of the Summary section of the report is now available. Contact messageREACH Customer Service to request the default report template be changed to the HTML version.


Report Definitions

The following terms are used in connection with various report types:

Posting Report An interim summary report that is automatically sent after job posting—if you requested a posting report when you submitted the job. (See "Posting” in the Job Lifecycle topic for posting information.)
Interim Report A report that is generated after the job is set up and prior to job expiration. The delivery information that may be included—if DSNs are requested in your User Profile—is subject to change as the job progresses and additional information becomes available. (See "DSNs” in the Job Lifecycle topic for posting information.)
Completion Report Provides a final accounting of job specifics. It is only available after a job expires. Even if all deliveries are done, a job is not "complete” until it expires since information may still be forthcoming. For example, pull files can be downloaded until the job expires. (See "Completion” in the Job Lifecycle topic for related information.)
CSV A file in Comma Separated Values (CSV) format includes the specifics that correspond to the report type you requested: the Detail, Pull, Exception, or Bad Address information. (See "CSV File Information” for details.)

Top of Page

Report Types

The basic types of reports are described in the chart below:

Summary Summarizes all known job information, including the numbers of items posted, canceled, pending, and blocked, and a pulled file count, if applicable. A summary completion report also includes counts for each of the following: items delivered, not delivered, and unconfirmed. Interim reports include delivery statuses only if your User Profile requests DSNs.

Posting status does not change once it’s reported. Delivery information, however, varies during the job’s posted phase. See "Posting” and "Posted” in the Job Lifecycle topic for more information.
Enhanced Summary As above, a summary of all known job information is included in an attached PDF or Excel file. Also includes graphical representation of the report data. Charts clearly show the percent of the list that has been posted, percent assumed delivered and bounced, open rate, etc.

Note:You must register to receive enhanced summary reports. See your salesperson for details. Custom enhanced summary reports will also be available. If other templates have been created for your account, you will see the names of the report(s) in the drop down selection box.
Detail
Provides summary information plus a CSV file containing details on posting and delivery statuses (once known) for every message destination. For each address, the CSV file includes the posting time, delivery time if known, pull file access details, if applicable, and failed address indicators, if any. Detail reports include all known information about every aspect of the job. The Pull, Exception, and Bad Address report types, described below, are subsets of the detail report.
Pull Provides summary information plus a CSV file containing details regarding pull file access. The CSV file lists the reference and e-mail address of the recipients who downloaded each file, and the time and date each file was downloaded.
Exception Provides summary information plus a CSV file that lists all exceptions to successful delivery. It displays the message addresses and the problem, whether due to a temporary or permanent condition.

Messages are not posted to addresses that are invalid (INVD), blocked (BLOC), or canceled (CANC). However, bad address (BADR) determinations can only be made after posting. A bad address is undeliverable, such as if an address no longer exists, for example. A CSV file is not created if all deliveries were successful.
Bad Address Provides summary information plus a CSV file containing the addresses of all deliveries that failed (and will always fail) because the addresses are either invalid or blocked. You should remove all bad addresses from your lists. A CSV file is only generated if bad addresses were included in the job.

Note: If the CSV file is larger than 1 megabyte in size, it is not delivered as an attachment. Instead, the e-mail report contains a link to a CSV pull file for download. The file is available for 5 days after the e-mail notice is delivered.

Top of Page

How to Get a Report

When you submit your message for delivery, you can request that reports are automatically sent to you. Otherwise, you can request specific types of reports on-demand, that is, at any time during the lifetime of your job. (See Job Lifecycle for job lifecycle information.)

Getting Automatic Reports

When you send a message for delivery via messageREACH, you choose whether or not you wish to automatically receive reports, and if so, what kinds of you reports you want. At the bottom of the Job Submission form, indicate which of the following you would like to receive:

These reports are sent to the report destination registered in your User Profile.

Getting Reports On-Demand

You can get a report at any time during a job’s lifetime by clicking the Status link in the messageREACH window. The report is sent to the destination address that you specify.

Top of Page

Report Content

The e-mail body of a typical report is displayed below, followed by an explanation of each field. After that is a sample CSV file and a description of its data columns.

A Typical Report Body (HTML Version)

Displayed below is the e-mail body of a typical report. This report is labeled an Interim Summary Report, but all report types display the common information found here (except as noted). In addition, reports other than Summary reports provide the specifics you requested in an accompanying CSV file.

messageREACH Interim Detail Report

Attention:

John Smith

Job Number:

00547185

Sent By User:

jsmith

User's Filename:

C:\Training\Newsletter sample\Newsletter.txt

Entered System:

10/31 15:58 EST

Report Generated:

10/31 16:06 EST

Customer Reference:

Sample newsletter

Billing Code:

 

Posting Status:

DONE

Expiration:

11/14 15:58 EST

List(s):

list.csv

Subject:

Newsletter for (I1)

<< Shows job details including list name(s) and times



Posting Summary

 

Number

Percent

Posted

4

80.00

Cancelled

1

20.00

Pend

0

0.00

Blocked

0

0.00

Error

0

0.00

Total

5

 

Of the 4 items posted, there are:

Assumed Delivered

3

75.00

Soft/Hard Bounce

1

25.00

<< Shows number of addresses posted and percent of total assumed delivered and bounced



HTML Open Confirmation

Assumed Delivered

3

   

Unique Opens

Unique Opens (%) of Assumed Delivered

Total HTML Opens

Total HTML (%) of Assumed Delivered

1

33.33

2

66.67



Click-TO File Summary

File Name

Size

Total Pulls

Total Pull (%)

Unique Pulls

Unique Pull (%)

mr.htm

862

1

33.33

1

33.33

Total Pulls

 

1

 

1

 



Top of Page

Report Body Explained (for plain text sample report)

The Posting Summary indicates a count for each status described below:

Posted - Delivery has been attempted at least once to the indicated number of addresses. Though some deliveries may have already succeeded, posted status more likely indicates that these messages are on their way to their target destinations. these destinations.

Cancelled - Invalid addresses; delivery is not attempted to these destinations.

Pend - Pending; delivery has not yet been attempted to these destinations.

Blocked - Recipient has requested removal from distribution; delivery is not attempted to.

Error - An error has occurred to these destinations.

The other report body fields are explained below.

messageREACH Interim Summary Report (The report type you requested) Attention: Marilyn (Names the report requester if report was requested on-demand; otherwise, names Report recipient from User Profile) Job Number: 00015734 (A messageREACH-assigned job identifier) Sent By User: xsi/user_name (Identifies the user who submitted the job) Entered System: 04/27 14:54 EDT (When job arrived at messageREACH) Report Generated: 04/27 14:56 EDT User's Filename: F:\msgfile\body.htm (File name of message body if the body was not typed in.) Customer Reference: mycref Billing Code: mybillingcode Posting Status: DONE (DONE indicates the job is posted; other possible statuses: Pending, and In Progress) Subject: Here's the latest information Attachment File Summary: (Attachment information only appears if your job included attachments) File Name Size ------------------------------ -------- att1.htm 193 att2.txt 132 Pull File Summary: (Pull information only appears if your job included pull files) Total pulls show the total number of pulls for the specified file, counting each pull even if multiple pull requests come from the same destination. This can happen frequently for images automatically pulled into a message as it is placed in a preview pane in an email client. Unique pulls count only 1 pull event per destination. Total Total Unique Unique File Name Size Pulls Pull % Pulls Pull % -------------------- -------- -------- ------ ------- ------ pull1.html 68 4 133.33 3 100.00 pull2.html 201 2 66.67 2 66.67 Total Pulls 6 5 % calculations are based on the number of pull events divided by the total posted LESS soft/hard bounces. Note: Total pull percentages can be higher than the number of destinations for small lists, because of multiple pulls from the same destinations. Posting Summary: Percent Posted 3 60.00 Cancelled 0 0.00 Pend 2 40.00 Blocked 0 0.00 Error 0 0.00 Total 5 Of the 3 items posted, there are: Percent of posted Delivered 0 0.00 (Only appears if DSN is on) Assumed delv'd 3 100.00 Soft/Hard Bounce 0 0.00

Top of Page

CSV

The CSV format provides a database representation of the addresses and information on which it is reporting. You can open this file using a spreadsheet application, such as Microsoft Excel. Otherwise, a text representation of the file is set up as follows:

The first row contains the column headings. The headings as well as all the data values are separated by commas. No spaces are used between different comma-separated values, and commas are used as placeholders wherever data is not included in a specific column.

Top of Page

Sample CSV File Opened in Excel

The CSV part of the report can be viewed in a spreadsheet application such as Microsoft Excel. There, it is formatted as follows:

Item Number Ref Address Posting Delivery Receipt Read Receipt Total Pulls Filename.wav #Filename.wav File.pdf #File.pdf
1 Lorraine Doe recipient_1@aol.com POST SUCC READ 1 01/29 11:35 1 -0- 0
2 Buffalo Bob bsmith@yahoo.com CANC -0- -0- 0 -0- 0 -0- 0
3 JD janedoe@msn.com POST SUCC READ 2 01/27 16:06 1 01/2 16:08 1
4 Joe Bones joeb@mailserver.edu POST BADR -0- 0 -0- 0 -0- 0
5 Carolyn Wu c.wu@some.com BLOC -0- -0- 0 -0- 0 -0- 0
6 Elaine elaine@another.org POST SUCC DEND 0 -0- 0 -0- 0
7 Mickey Johnson 999-55-1212 INVD -0- -0- -0- -0- 0 -0- 0
8 DC2 toyou@home.com POST SUCC DELD 0 -0- 0 -0- 0
9 DC2 toyou@home.com DUP -0- -0- 0 -0- 0 -0- 0

Note that Read Receipt information is only displayed if your User Profile is set to show MDNs.

Top of Page

CSV File Information

As you saw in the example above, the CSV file organizes the job information into columns. These columns are similar for each report type; they are explained below, with the differences noted:

Item Number – A messageREACH-supplied count of each destination address, beginning with the number 1

Ref – A unique reference supplied by you for each address in the list; typically, it names the recipient to help you easily identify the recipient's address

Address – A message destination, that is, a recipient’s e-mail address or the name of a list to which the message was sent

Posting – A status indicating whether or not delivery is underway to this address. Possible posting statuses include:

Delivery Receipt – Displays an abbreviated representation of the most recent DSN activity that occurred (if any). Possible status indicators include:

Read Receipt – Displays an abbreviated representation of the most recent MDN activity that occurred (if any). NOTE: Information only displayed if your User Profile is set to show MDNs. Possible status indicators include:

Total Pulls – Number of times the recipient downloaded the pull files. NOTE: Column only displayed if pull files were submitted.

One column for each Pull file – Each column header names a pull file if one or more were submitted with the job. The first file download date and time are included for each address unless a recipient did not download the file.

One additional column for each Pull file - starting with # – shows the number of pull events for each file. It is possible for this number to be greater than one. For example, for images automatically pulled into an HTML message, the pull event will occur each time the recipient opens the message, or the message is visible in the reader

Top of Page

Replies, Removals, and Removal Reports

What happens when a recipient uses his or her e-mail reply feature to respond to messageREACH e-mail? That is the subject of this help topic. Removal Reports are also covered.

Replies

When messageREACH receives replies that do not include the word "remove” in the subject line, the replies are automatically forwarded to you. They are sent to the e-mail reply address specified in your User Profile.


Remove Requests

Removal instructions are included for each recipient at the end of every messageREACH message. By following the instructions, recipients who no longer wish to receive mail from you (via messageREACH) will be blocked from further distributions. To do this, recipients can reply to the message by placing the word "remove” in the Subject line, or they can click the mailto: link, or click the Web link and follow the instructions.

messageREACH sends one additional message to the recipient confirming the removal. Most blocking takes effect by the end of the day that the request is received, or within 24 hours. Removal requests are honored whenever they are received—even if this occurs after the associated job expires.

Addresses for removal are recorded in a messageREACH "block” list. Block lists are associated with specific users. Therefore, a recipient can be removed from your lists, although the same recipient can continue receiving mail sent by another messageREACH user if that is their choice. (Please ensure that each recipient is indeed interested in receiving the types of mail you intend to send; also check the validity of a new address prior to using it.) If a recipient requests removal from your distributions and later agrees to be included again, messageREACH Customer Service will help you with the reinstatement.

A User Profile option allows you to receive copies of your recipients' remove requests if you wish. Note that each remove request will be copied to the e-mail address that you specify. This address can be different from the reply address.


Removal Report

Although recipients who request list removal are blocked from your distributions, you should also remove their addresses from your lists to help speed up your message processing and keep your costs down. A removal report includes a CSV file that provides the removal addresses and the corresponding time when messageREACH received each request.

To get a removal report, click List Services on the messageREACH site. Then click Removal Report, supply an e-mail address for the report, and click the button to send the request. Refer to the report when you delete these addresses from your lists.

Top of Page

Vacation Notice Processing

Vacation notice processing Some destinations use a function classified as an "Autoresponder" when they are out of the office or on vacation. Typically these email clients "reply" to every message received with a fixed text, such as "I am out of the office and will read my email on my return." This is meant to politely tell you that the message was received but will not be read or answered for a while.

When you send a broadcast to thousands of recipients, you could have dozens of such autoreplies. MessageREACH analyzes each reply, and if it finds such an autoresponder message, it does not forward them to your email mailbox.

NOTE: Not every autoresponder is recognized since there is no standard for such responses, so you may still receive a number of autoreply messages.

Top of Page