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.

    Advertisements

    Courier MTA IMAP Server & tiggit version 1.0.11

    October 16, 2008

    Version 1.0.11 is now available for download. This version provides a bug fix for downloading folder lists from Courier MTA IMAP servers.

    Courier IMAP servers are a little different to most mail servers as they do not return the folder list in an linear form – i.e. starting with the root folder, all it that folders children, and for each folder all of that folders children. Rather the folder list appears to arrive in a disorganised order. Version 1.0.8 resolved problems with handling this disorder. This bug fix solves a problem with forcing the INBOX to be set to synchronise once the folder list has been downloaded, resulting in folders not being properly organised.

    Migrating users should note that this upgrade will result in existing mailboxes and folder lists being wiped. Users should re-sync folder lists prior to downloading messages.

    Registered users can download version 1.0.11 by using the download link in their download mail, or by going to http://www.tiggit.com/tiggitmail/eapcheck.html 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 should take care that any data that is stored within tiggit mail is kept elsewhere as this upgrade will cause all of the mailboxes to be erased.

    versions 9 & 10

    October 8, 2008

    Couple of high velocity releases of late, both to fix user reported problems

    Version 1.0.09 fixes problems preventing messages being sent via the tunnel

    Version 1.0.10 fixes problem resulting in message moves failing.

    Registered users can download version 1.0.10 by using the download link in their download mail, or by going to http://www,tiggit.com/tiggitmail/eapcheck.html 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 should take care that any data that is stored within tiggit mail is kept elsewhere as this upgrade will cause all of the mailboxes to be erased.

    starting the idle battery benchmark again

    July 4, 2008

    I am starting the idle battery benchmark again: that is I am charging my 8200 up to full charge and will start it IDLEing with GMail this afternoon, and will leave it going until the battery runs out. I think some of the recent changes will have reduced the battery use when idling.

    I have also written a little application that reports battery charge so that I can more accurately record the battery use each hour. There is a script running on a server that sends an email to my gmail account every two minutes. This is intended to simulate a heavy load. Vibrate to alert for new messages is on. I am not going to use the device in the mean time, so the screen backlight will not be a significant factor.

    Also, I am running this test using my T-Mobile pay as you go SIM, which has the advantage of being able to see how much data is used, so not only will I have a view of battery life, I will have a better understanding of real data use when idling.

    Results follow

    After three hours, the battery is reporting 89%

    After about 2 and a half days the handheld battery is below 10% and so tiggit mail has quietly closed the connection.

    In truth, there were a number of interruptions to the test, with sessions needing to be re-established. There is still plenty to do on the session re-establishment algorithm, but at least all the messages were delivered and for the most of the time the idle session was maintained.

    The real problem is that I did not have a “control” example of a completely idle BlackBerry and one receiving the same number of messages via BIS/BES push.