Five new API methods

We've added the following five API/web service methods to improve our transactional email capabilities. All were requested by prospects evaluating JangoMail. Do you have a request for an API method that would make your developer's life easier? Let us know by filling out our Support form.

Click each method name to use its corresponding test form.

Reports_GetBouncesByTransactionalGroup_XML
Retrieves list of bounced addresses for a particular transactional group. Includes SMTP Diagnostic Code and Definitive columns. Returns an XML document.

Reports_GetBouncesByTransactionalGroup_String
Retrieves list of bounced addresses for a particular transactional group. Includes SMTP Diagnostic Code and Definitive columns. Returns a string.

Reports_GetBouncesByTransactionalGroup_DataSet
Retrieves list of bounced addresses for a particular transactional group. Includes SMTP Diagnostic Code and Definitive columns. Returns a .NET DataSet.

DeleteTransactionalGroup
Deletes a transactional group from account. Returns a string.

GetTransactionalGroupID
Gets a transactional group id. Returns a string.

Two bug fixes in SMTP relay service

We've just deployed two fixes to the JangoSMTP transactional email service:

1. Previously, lines in an email message that begin with a single period would result in two periods when delivered to the recipient. This was a bug related to how SMTP treats the escaping of periods. This is now fixed. To read more about issues involving SMTP and periods, see this article: http://db.ilug-bom.org.in/lug-authors/philip/docs/mail-stuff/smtp-intro.html

2. Previously, if an email message was relayed to relay.jangosmtp.net and included both the Disposition-Notification-To and the Return-Receipt-To headers, then JangoSMTP would throw an error on the email message:

System.ArgumentException: An item with the same key has already been added.

This is now fixed, and email messages containing both headers will be delivered properly.