New Feature: Include CC Addresses

JangoMail has added the ability to specify a CC (carbon copy) address that will be visible to message recipients. You may also use personalization coding in this CC field as you compose your messages.

The CC feature allows you to specify an address that will receive a clear (address IS visible to the email's direct recipient) copy of the message as it is sent out. It is found under Advanced Options as you compose in the Send E-mail tab.



For example, you send a personalized message that starts: Dear Kim, Dear Joe, Dear Susie, etc. Kim, Joe, and Susie each receive their individual emails, showing the appropriate personalization. At the same time, the address given in the CC field also receives 3 emails: copies of the separate messages for Kim, Joe, and Susie.

You may want to specify a single address to receive the CC. This can be used to create an arachive for businesses with compliance needs, for example.

You can also use our personalization coding to send the CC email to an address stored in each record in your database. For example, addresses might have a particular representative assigned to them. The email can be copied to a customer's specific representative, while the message itself may be "From" the main corporate headquarters.

From Address: announcements@browniekitchen.com
CC Address: %%repemail%%
(where data associated with each address record contains a field called "repemail")

Then, Kim, Joe, and Susie would each see that their own representatives were copied on the messages as well -- also a good reminder of that direct contact information should the recipients have any questions.

Note: When using the CC feature, JangoMail is generating two emails for every one recipient address. This will double your email sending volume for pricing purposes. If you use this feature along with our BCC feature, then you will be tripling your volume for pricing purposes.

New Feature: Add Personalization to the BCC field

JangoMail has added the ability to use personalization coding in the BCC field as you compose your messages.

The BCC feature allows you to specify an address that will receive a blind (address not visible to the email's direct recipient) copy of the message as it is sent out. It is found under Advanced Options as you compose in the Send E-mail tab.

For example, you send a personalized message that starts: Dear Kim, Dear Joe, Dear Susie, etc. Kim, Joe, and Susie each receive their individual emails, showing the appropriate personalization. At the same time, the address given in the BCC field also receives 3 emails: copies of the separate messages for Kim, Joe, and Susie.

Previously, you could only specify a single address to receive the BCC. This was often used for businesses with compliance needs that required an archive of messages sent.

Now, you can use our personalization coding to send the BCC email to an address stored in each record in your database. For example, addresses might have a particular representative assigned to them. The email can be "signed" from the representative in the message body:

Regards,

%%repname%%
%%repemail%%

Now, these representatives can also receive a behind-the-scenes copy of what "they" sent out via the JangoMail system, so that they won't be surprised with direct responses from their clients. If this data is stored in a field called "repemail" for each record, just put %%repemail%% in for the BCC.

Note: When using the BCC feature, JangoMail is generating two emails for every one recipient address. This will double your email sending volume for pricing purposes.

New Feature: Specify an SMS Text Message

JangoMail has added an SMS Text Message feature to our Messages composition page. Now you can send a specific message to an SMS address, instead of the HTML or Plain Text message types. Be courteous to your recipients receiving messages by text and build a message tailored to them.

You will find the new field on the Messages composition screen, under the SMS tab. Specify a message here for any text users. If an email address is in one of the listed SMS email gateway domains, then this SMS Text Message will be sent from your JangoMail account instead of the standard HTML/Plain Text multipart message.

If the SMS Text Message field is not set, and a recipient's domain is an SMS email gateway domain, then the email message will be assembled as normal, including the HTML Message, Plain Text Message, and any attachments.

A full list of SMS email gateways is available at http://en.wikipedia.org/wiki/SMS_gateway.

The following properties are ignored when an email message to an SMS email gateway is assembled:

• Open Tracking
• Click Tracking
• Wrapping
• Plain Text Message
• HTML Message
• Attachments
• Triggers

New Feature: Calendar/Time controls added to Send E-mail page

JangoMail has made it easier to get the format right when entering date/time information for scheduling emails to be sent in the future or on a recurring schedule.

We have introduced new calendar and time controls for these fields to help you get it right the first time.

How do you use the new tools? Look to the right of the scheduling fields for the calendar and clock symbols.



Click on the calendar to set the date.



Now, click on the clock to set the desired time.



You'll wind up with the right format each time.

New API Methods and Enhancements

JangoMail has launched some new API methods, and some enhancements to earlier methods.

Retrieve Complaint Data

JangoMail now allows you to pull the data behind the "Complaints" column of your General Job Statistics report via the API. This reflects addresses that have used their "this is spam" reporting tools via their ISP, which JangoMail receives via feedback loop.

• Reports_GetComplaintsByCampaign_Dataset retrieves list of complaints for the given Job ID. Returns a .NET DataSet.
• Reports_GetComplaintsByCampaign_String retrieves list of complaints for the given Job ID. Returns a String.
• Reports_GetComplaintsByCampaign_XML retrieves list of complaints for the given Job ID. Returns an XML document.

Check Job/Campaign Status

Once you send, your campaign goes through three stages:

• Preprocessing -- where the message is prepared for sending, removing duplicates, bounces, unsubscribes, etc. prior to sending.
• Sending -- where the message is personalized and launched from our network of senders.
• Complete -- where your campaign has fully completed sending.

These states are shown in the JangoMail interface under Reporting, and you can now confirm the current status of any campaign by API as well.

GetMassEmailStatus returns the current status for the given job/campaign ("Preprocessing", "Sending", or "Complete").

Enhancements to the "Send..." Methods

The CustomCampaignID can now be specified in the "Options" parameter of the "Send" methods (SendMassEmail, SendMassEmailPrevious, SendMassEmailPrevious2, SendMassEmailRaw). For example, Options can now include the following parameter: CustomCampaignID=FinalMailer.

Attachments will now validate during sending. This will alert you if you specify an attachment in the "Options" parameter that does not exist on the server. Previously, such a campaign would still go through, but missing the attachment, and the method would return a SUCCESS message. Now if the attachment doesn't exist, an exception will be thrown and no campaign will be sent or saved.

Enhancements to AddGroupMember and EditGroupMember

JangoMail has a new setting to prevent duplicates from being added to a Group. With the API, the AddGroupMember and EditGroupMember methods reflect this change as well. Both will now throw exceptions if the Group is set to disallow duplicates and you:

• attempt to either add an already existent address, or
• edit an address such that it would match an already existent address.

For the full web-based reference on all available methods and their signatures, including the new methods and enhancements, click here.

New Feature: Prevent Duplicates in Groups

JangoMail now allows you to prevent duplicate addresses from being added to a Group.

To turn this setting ON, go to Groups and E-mail Addresses and select your Group. Click the "Enable/Disable Duplicate Members" button in the right hand pane.

With this setting enabled, if you attempt to add an address to a Group that already contains that address, it will prevent the new entry. The method of adding a Group member will not affect this setting.

Manual entries will display an error, and imports will skip addresses already in the Group. If you are using a web site sign up form, the user will get an error if they are already in the Group, preventing a second entry for that email address.

Note the difference between this and a Scrub (Scrub Group Members), for a Scrub does not prevent duplicates from being added--it just clears duplicate entries (by email address) when executed.

Note: If you enable this setting on a Group that already has duplicates, the existing duplicates are NOT deleted unless you run a Scrub.

New Feature: Creating Multiple Logins for Your Account

JangoMail users now have the option to create alternate login credentials (username and password) for their accounts.

Creating additional logins will allow additional people access to the same account. Creating additional logins does NOT create new JangoMail accounts, and all logins have the same permissions as the main username/password on an account.

You may find this useful if you have multiple people accessing the same account. With different logins assigned to each employee,if one employee leaves, that one login can simply be deleted without affecting the others using the account.

There are a few limits to these logins. The additional logins do not have API access, the ability to initiate mass emails through an external email client, or the ability to FTP to the JangoMail server. Only the administrator's login can utilize these functions.

How do I get started?

Login with the current username and password, and go to the My Account section in the upper right of the interface.

Select the Other Logins tab.

Click Add New Item to add a new login. You may choose to restrict access to certain pages on the Access Restrictions tab.

The list of login credentials will then be available in your account for your ongoing maintenance (add, edit, delete).

 

Enhancement to Reporting: Filter by CampaignID

We have now expanded the General Job Statistics Report's filtering abilities, making it easier for you to locate a specific email campaign. Now, you can use the CampaignID filter to locate specific jobs quickly by searching for the campaign's unique numeric identifier.

Bug Fix: Foreign Characters and Personalization

We have now deployed fixes for two bugs related to handling foreign characters in personalization.

Using the API for "on the fly" personalization

Using our ability to do "on the fly" personalization with the API in the SendMassEmail method, we were not properly encoding personalization when it involved a non-English character set.

With this correction, you can now submit personalization field values that DO use the non-English character set, provided that it is specified in the CharacterSet option.

Now, your Options attribute can contain parameters like:

Options=
ToOtherRowDelimiter=¦,ToOtherColDelimiter=c,
ToOtherFieldNames=FirstName¦LastName¦EmailAddress¦
Headline,CharacterSet=UTF-8

This would allow you to then use the following to create a merged message with non-English characters:

ToOther=
John,Smith,john@smith.com,揭秘神舟七号飞船气闸舱¦David,Gary,david@gary.com,揭秘神舟七号飞船气闸舱¦Sheila,Panther,sheila@panther.com,揭秘神舟七号飞船气闸舱

Subject=
Hello %%FirstName%%Message=Hello %%FirstName%% %%LastName%% -- today's headline is %%Headline%%

Using foreign characters in stored Group data

When storing data in a JangoMail Group, foreign characters inserted into a group member's field previously had turned into neutral placeholders when saved. Now JangoMail can correctly store foreign characters in Groups too and use that for personalization.

Update to ASP script file for web servers

This notice applies to you if you use JangoMail's "Connect to Internet Web Site Database" feature to pull email address data in real-time from your web site's database.

We've updated the web server script file that is used to allow JangoMail to connect to your web / database platform. This update applies to those customers using one of these three platforms:

• Active Server Page web site / Any ODBC compliant database
• Active Server Page web site / Microsoft SQL Server Database
• Active Server Page web site / Microsoft Access Database

This update does not apply to the PHP / MySQL platform, because the w_4.php file has never used the EnDeCrypt algorithm used in the w_x.asp files.

What is the update?

The update eliminates the EnDeCrypt encryption algorithm that was previously used in the w_x.asp files. The EnDeCrypt algorithm present in the w_x.asp files is an outdated encryption/decryption mechanism that we have deprecated in favor of using standard SSL (Secure Sockets Layer) security with the https protocol.

If you retrieve the appropriate w_x.asp file now from the Extract From My Database tab of JangoMail, the new w_x.asp file will no longer contain the lines of code that perform the decryption. If you have made your own custom modifications to the script file on your web server, you can update the file manually. Or, you can retrieve the updated file from JangoMail directly.

After the updated file is in place, you must click a button at the top of the Extract From My Database tab which will tell JangoMail to stop encrypting data using the EnDeCrypt algorithm when passing information to your web server.

To update your w_x.asp file manually:

1. Comment out or delete the lines that perform the EnDeCrypt decryption.
2. Deleting the RC4Initialize subroutine and EnDeCrypt function.
3. Comment out or delete the two array declarations, "Dim sbox(255)" and "Dim key(255)"
4. Click the button that appears at the top of the Extract From My Database page to update your JangoMail account so that data is no longer encrypted with EnDeCrypt before it's passed to your web server.

To retrieve the updated w_x.asp file from JangoMail:

1. Login to your JangoMail account.
2. Click the Extract From My Database tab.
3. Click "retrieve the web server file" and follow the directions to download the appropriate file.
4. Click the button that appears at the top of the Extract From My Database page to update your JangoMail account so that data is no longer encrypted with EnDeCrypt before it's passed to your web server.

Do I have to update my w_x.asp file?

We highly recommend that you do the update as soon as possible. The old versions of w_x.asp, with the EnDeCrypt mechanism, will continue to work through the end of the year. In early 2009, the option to use a w_x.asp file with the EnDeCrypt routines will no longer exist.

One final note:

There is a benefit to updating if you maintain multiple JangoMail accounts. The old w_x.asp files, with the EnDeCrypt mechanism, made use of a private key that was hard coded inside the routines, and a private key was unique to a single JangoMail account. Once you update to the new w_x.asp files, there will be no hard coded key, and this will allow the same version of the w_x.asp file to be used with multiple JangoMail accounts.

Feature Update: Link JangoMail to Multiple Salesforce Accounts

We have expanded our Salesforce integration so that you can now connect one JangoMail account to multiple Salesforce accounts.

Now, if you have multiple Sales Agents that use their own Salesforce accounts, they can all use the same JangoMail account for sending.

How do you set this up?

1. From inside Salesforce, click the "JangoMail" tab. If you login to an existing JangoMail account, then the Salesforce account from which you logged in will be ADDED to that JangoMail account's list of linked Salesforce accounts.
   
2. Go to My Options --> Salesforce --> Account Settings. Now instead of the previous single line text field that stored a single Salesforce User ID, there is a text box that can store multiple Salesforce User IDs. Type in any additional IDs here, each on a separate line.
   
   

This multiple connection only works one direction, however. You currently CANNOT have multiple JangoMail accounts linked to the same Salesforce account. A Salesforce account can only be linked to one JangoMail account, but a JangoMail account can be linked to multiple Salesforce accounts.

Image Library Now Accepts .MOV Files

JangoMail has expanded the Image Library so that you can now upload Quicktime .MOV files. Once stored, you may create links in your messages that reference the hosted files much as you would a PDF or other non-image file.

JPG and GIF files remain the only image file types that are recognized by the HTML Editor's Insert Image function because they are the file types that are viewable across most HTML-capable e-mail clients.

Other file types are accepted into the library for hosting. Our tutorial on linking to hosted files (PDFs and others) can be downloaded here.

Bug Fix: JangoMail for Salesforce Personalization Fields

JangoMail has corrected field misalignment that was occurring when sending to campaigns with members from both leads and contacts.

The error resulted in problems with personalization fields not properly matching during sending.

This is now fixed. As a result of the change we have made, some personalization syntax has changed slightly. Before, when you pulled from Contacts, Leads, or Campaigns, the fieldnames would have "Contact." or "Lead." prefixing the actual field's name. So "Contact.FirstName" and "Contact.LastName" for example were the field names. As a part of this fix, the field names are no longer prefixed by the table name. These would simply now be "FirstName" and "LastName" alone.

New Feature: Pre-Process Campaigns Now

You can now choose to have your campaigns pre-process messages scheduled to be sent at a later date when you click on Send E-mail, allowing this task to process in advance and speed later sending.

Every JangoMail campaign starts with "pre-processing," the period where the system creates your final recipient list and assigning your campaign to our bank of senders. We start with building the list of all addresses to which you are attempting to send your message. Then, we cross-check that list for unsubscribes, bounces, duplicates, and invalid addresses.

If you will not be sending your campaign "Now," but at a later date, you can now elect to go ahead and let this pre-processing step take place now so that when the time comes to send out the campaign itself, there won't be any time spent waiting on pre-processing to complete.

How do you use this feature? When you schedule your campaign, just check the box to pre-process now.



Why would this benefit you? If you are sending to a large number of recipients (hundreds of thousands) and/or to a large number of Groups, this period can extend to several hours, based upon the amount of work the system must do to generate your final recipient list.

Security Update: Enhanced Action Logging

JangoMail's internal activity logs now record the paths taken by clients as they work within the JangoMail application. This record of page views both enhances security and aids your JangoMail Support team.

If you suspect that an unauthorized person (former employee, unauthorized employee, etc.) has been accessing your account, it will be easier to track.

From a support perspective, your support team can now review the logs to see what path you've taken as you've navigated through the site on your task -- so we can see where you've been and where you need to be!

Group Scrub Tool Expanded

JangoMail's Scrub Group Members feature has been expanded to better "clean" lists of bounced addresses and to allow you to see what a Scrub will do before actually permitting the Scrub to change your data.

Previously, the Scrub to remove previously bounced addresses would remove those addresses that had bounced X times (per your My Options, Bounce Handling settings) prior, with the default being 3.

Now, you also have the option to remove "definitive" bounces that have occurred only once.

Why? Whitelisting requirements with many ISPs now dictate that definitive bounces are removed after a single bounce. As a result, JangoMail has been removing them "on the fly" during sending, as you see in Sending Complete email results, but this has not been reflected in the Scrub Group Members function until now.

A definitive bounce is one where the receiving server responds with a message indicating that the particular address does not exist on that server. Typically, these are the "user unknown," "mailbox not found," etc. types of addresses.

Concerned that a Scrub might not do what you expect? Now, get a Scrub report without actually changing any data. Use the new option at the top of the Scrub Group Members page to elect a View Only scrub.

Your Email Manager will get the Scrub Job Complete report, showing data as "VIEW ONLY." The total number of Group Members won't change, but the report's detail will show you what data would have been affected had you really run the Scrub.

Then, you can safely go back in and run the real scrub to clean your data, if you choose.

The email notification will have (VIEW-ONLY) in the Subject line, and the report will look like:

Enhancements to Reporting: Click Tracking All Positions

JangoMail has expanded Super Reporting's Click Tracking data.

Previously, Click Tracking reports sorted by URL would show Click Tracking data separately for each position of a URL within a message. If your URL appeared 3 times in a message, the Click Tracking data would be split among the positions, so you could see which position achieved the best results.

Now, in addition to the data split by position, we have included additional columns for Total Clicks All Positions and Unique Clicks All Positions so that you can quickly gauge interest in a particular link, regardless of its page position as well.

Bug Fix: Plain Text Preview

When using Preview/Save on a message under composition, users have the ability to check a box from the pop up to also have a plain text version of the HTML message sent separately so that it can be checked for appearance as well.

We have made two adjustments to the processing of the plain text message for Preview. These issues were NOT affecting campaigns that were actually sent ("Send E-mail" button), but only the Previews.

1. The From Address will no longer show a 4 digit numeric extension. Ex: browniekitchen0042@jangomail.com will now show simply as browniekitchen@jangomail.com.
2. When Click Tracking is enabled for the campaign, but disabled for the plain text version of the message, the additional tracking code will no longer show in the Preview version either. A link in plain text of http://www.browniekitchen.com will remain unchanged.

New Administrative Watch Feature

The JangoMail Support Team has added to its array of administrative tools with a new Alert feature. Your Support Team can now set a watch on your account to be alerted directly by email when a campaign of a given size is being launched.

This allows us to watch over your messages as you explore new features or as we may be assisting you with troubleshooting any concerns with message processing as the message is actually going out. When your Support representative sets the Alert, he/she will be notified by email when a campaign that meets the Alert's settings has been sent. The JangoMail user will not notice any change in how he/she sends, and the Support team can watch the campaign move through each step of the sending process closely.

Group Merge Available in Exported Reports

JangoMail has now updated our Super Reporting pages to again allow for merging Group data with reports during export. To use this feature, you must export by email (the envelope icon). The direct download to CSV will not perform the merge.

If you have sent a campaign to a JangoMail Group, you will be able to select that Group during export to see the list of data in the report, along with the data that was originally stored along with the email address in your Group.

Let's do an example:

• A campaign is sent to a Group containing the following data:
  
  emailaddress, customerID, firstname
  jane@doe.com, 12345, Jane
  smith@yahoo.com, 12346, Bob
  


• The Unsubscribes report shows that Jane unsubscribed, and we export that report.
  


• With a standard export, the email address would be included in the report, along with the date and time the address unsubscribed (jane@doe.com, 06/13/2008 01:00:00 PM).
  


• If the export is Merged with the original Group that received the message, the report would include the email address, the date and time of the unsubscribe, the customerID, and the firstname (jane@doe.com, 06/13/2008 01:00:00 PM, 12345, Jane).

This feature is most often used when exported data needs to be synchronized locally to other stored data. In the example above, we could then update Jane's information easily because we had her customerID -- and that is how our system tracks her.