version 1.1.12 available for preview

April 13, 2009

Version 1.1.12 started out with only one objective – to provide support for STARTTLS – to allow sending mail via hotmail. Since then a number of problems and some ideas have come up, that have also been addressed.

Providing support for STARTTLS requires changing an active connection from being in plain text, to being protected by TLS. Folklore says that it should be possible to do this from within the BlackBerry API, but after several weeks of trying, I gave up and started using the TLS capabilities within the open source Bouncy Castle package. tiggit mail now includes a cut down version of Bouncy Castle. The module is called Bouncy Tiggit.

A number of users have asked for the ability to play a sound when a new mail is received by tiggit, and so version 1.1.12 includes the ability to assign a ring tone – via the profile manager – to new messages arriving in tiggit. Also, tiggit will now play audio attachments directly from the message viewer to allow users to listen to emailed voice mail messages.

Version 1.1.12 has an improved network configurator that makes reference to the Service Book to understand the available network settings. The network configurator still attempts to make http and socket connections, but it attempts to make these connections for each entry in the Service Book. In the event that tiggit cannot find a Service Book entry that works it will attempt to make some direct http and socket connections as a last resort. There is also a new setting serviceBook that allows the user to specify the Service Book UID to be used by tiggit.

Service Book based configurator

Service Book based configurator

A number of users have complained that html messages are displayed ‘twice’. Actually this is the HTML attachments being displayed as well as the plain text attachment. Version 1.1.12 no longer displays plain text attachments if there is a HTML attachment.

This version includes refactoring of the message sending code to improve reliability for sending messages and uploading sent messages to a Sent Items IMAP folder. This includes a new technique to send data to smtp and imap servers in blocks, rather than a continuous stream. As a result there are two new configuration paramers – socketBlockSize and socketBlockWait. These set the amount of data that is sent in a single block, and the amount of back off time allowed prior to sending the next block. These values may need to be optimised for different data networks.

Here is the detailed list of changes in version 1.1.12

  • integrated bouncy castle and implemented starttls
  • logic to detect whether starttls should be used for SMTP
  • logic to detect authentication mechanism for SMTP
  • mp3 attachments
  • play sound when mail arrives
  • fixes bug where full message was not always downloaded via POP3
  • fixes bug in handling message move responses
  • improved useability of file chooser when adding and saving attachments
  • servicebook based connections
  • don’t display plain text if HTML has already been displayed
  • new parameters for socketBlockSize and socketBlockWait
  • servicebook based configurator
  • fixes bug in reload functionality
  • fixes bugs in sorting behavior
  • ability to set delete preference
  • Registered users can download version 1.1.12, by clicking here and entering the email address that was originally used to register for tiggit mail. Exisiting license tokens will continue to work with this version. Users are advised to take appropriate precautions when upgrading to this version as all messages on the handheld may be lost.

    proper html rendering at last

    December 6, 2008

    I have just finished the first cut of adding proper html rendering to tiggit mail using the built-in browser object. You can see a  HTML emails on the Storm Simulator below. (Thanks to Apple for the email advert to test with.)




    It is by no means trivial to pass an HTML string to the browser and then get it to render it correctly. It feels like I wrote an entire browser this afternoon! My big worry now, is that it will not be fast enough, especially for those messages that do not come in both plain text and html.

    HTML rendering will be included in version 1.1 preview 4 that will be posted in the next day or two, all being well.