Wednesday, January 28, 2009

New Feature: FTP Images and Files to Your JangoMail Account

JangoMail has expanded our Image Manager capabilities to support accepting images and other files (PDF, XLS, DOC, etc.) by FTP for addition to your account's Image Library.

Previously, users were required to use the Image Manager tool within JangoMail to upload images and files individually. This upload process copies the files to both our primary and backup server locations.

Now, you have a choice. You can always use the Image Manager tool to upload your files, but you can now also FTP your files directly to your account. This will greatly improve the convenience and speed with which you can work with multiple file uploads.

How do you get started? FTP your files to ftp://client.jangomail.com/Images/. Use your existing account username and password for your login credentials. Images saved to this location via FTP are automatically replicated to the second image server as well, retaining the redundancy we have always maintained.

Feature Update: Enhanced HTML Editor Upgrade

JangoMail had applied several upgrades to the Enhanced HTML Editor available for composing your emails. Previously, some users experienced difficulty with some table commands. The new updates include fixes for reported problems like:
  • Documents with a table at the beginning made it difficult to then select the whole document.
  • Deleting a table at the end of the document sometimes caused the editor to hang.
  • Deleting table rows and columns at the end of the document caused the editor to freeze occasionally.
  • Merging cells in tables with caption tags caused the editor to freeze
You do not need to do anything differently to use the updated Editor. If you are using the Enhanced Editor, the updates will automatically apply as the Editor loads within JangoMail.

API Update: New Option for SendTransactionalEmail

JangoMail has enhanced the new SendTransactionalEmail method to support our customers who may need to allow recipients to unsubscribe from marketing campaigns, but continue to receive transactional emails related to their accounts (confirmations, passwords, receipts, etc.), then we have enhanced the new SendTransactionalEmail.

Now, the SendTransactionalEmail method allows you to specify a parameter within the "Options" to handle this. Set "SkipUnsubCheck=True", to prevent JangoMail from first checking the address against your account's unsubscribe list and removing those who have unsubscribed from regular marketing campaigns. By default, if this parameter is not specified, "SkipUnsubCheck" is "False" and will continue to check for unsubscribes normally.

For detailed documentation on this method, go to:
http://api.jangomail.com/help/html/655d20ca-2164-c483-fb21-d3d0ee049155.htm

Friday, January 23, 2009

Update to DKIM Signatures on Outbound Email Messages

We have updated the DomainKeys Identified Mail (DKIM) signatures that appear in outbound email messages sent from JangoMail.

Specifically, we are now using "v=1" instead of "v=0.5" and "q=dns/txt" instead of "q=dns" in the DKIM-Signature header.

These changes were made to comply to the latest RFC 4871 for the DKIM Base Specification, and so that JangoMail email messages pass the DKIM verifier on all major DKIM reflector services, including those offered by dkim.org, Sendmail, and Port 25.

Sending emails to these email addresses from your JangoMail account will generate a reply email showing the result of the DKIM verifier:

1. check-auth@verifier.port25.com (Port 25)
2. dkim-test@testing.dkim.org (DKIM.org)
3. sa-test@sendmail.net (Sendmail)

Prior to the change, JangoMail emails were failing the Port 25 verifier. Now with the change, JangoMail emails pass all 3 tests.

Wednesday, January 21, 2009

Feature Update: Connect to Database Supports Magic Quotes

For users connecting JangoMail to their MySQL databases via PHP, we have now modified our connection file to make JangoMail less dependant on the customer's local web server configuration.

Previously, users had to turn off a feature known as "magic quotes" before the extraction file would work. Now, JangoMail can make the connection regardless of the magic quotes setting. This makes establishing the initial connection simpler and more direct.

Our new code looks like:

Friday, January 16, 2009

Feature Update: Extract from Excel and Access 2007

JangoMail now has tools to help you use Extract from Local Database to connect to Excel 2007 and Access 2007 files. Now users of the most recent versions of these programs can make direct connection without exporting/importing.

To get started, go to the Extract from My Database page and click to Connect to Local Database. On that screen, you'll choose to Create Profile (experts only).



Then, you'll be able to create a name to save the profile and use the Connection String links to build the proper syntax for linking to your file. In the example below, we are connecting to an Excel 2007 file.



This prepopulates the Connection String box with general information and the name of a "placeholder" file for the "Data Source=" section. In the example, the file is at: c:\myFolder\myExcel2007file.xlsx.



You will replace the placeholder file path and file name with the true path and name of your existing file and modify the SQL Query as appropriate to generate the list desired.

JangoMail Updates: Interface Enhancements

We've implemented a few enhancements to make information a bit more "at your fingertips" when working with JangoMail.

First, we've enhanced Groups and E-Mail Addresses. Now, when you hover over a Group, you'll get a quick view of the attributes of that particular Group.



Once working within a Group, you can hover over a Group member to bring up the full address. This is super-helpful when the address is too wide for that column and cut off by an ellipsis.



Over in Extract from My Database, we've rearranged the main page to reduce scrolling. Now, you will be able to select from the three types of extraction in a horizontal, not vertical, layout.

Wednesday, January 14, 2009

New Option: Transactional Groups

To support Reporting for messages sent under the new SendTransactionalEmail API method, you can now specify Transactional Groups to store data on messages sent via the API. JangoMail shows Reporting for transactional emails sorted by Group so that you can see metrics on these messages combined together.

By default, all accounts come with a Default Transactional Group. When calling SendTransactionalEmail, the message becomes part of the "Default" group unless otherwise specified. All reporting for these mailings will be categorized as part of the Default Group.

If you have multiple types of transactional emails, then you will want to specify the Transactional Group to which the message belongs when you call the method. You can now setup Transactional Groups under My Options --> Transactional Groups.

For example, you can create a specific Group, like "Order Confirmations," and then specify that Group when calling the method, then you'll see Reporting on those messages combined together.