version 1.1.11 now available for preview

March 2, 2009
Version 1.1.11 is another bug fix release, and is now available for user preview. It provides a number of fixes to message header processing and formulation.
Adds display headers function: Pressing shift, then h will cause tiggit to display all the headers for the message. Use the trackball to scroll through down to see the message.

Here are the details of all the updates and fixes within this version.

  • fixes timezone problem for negative timezones
  • removes un-necessary to and cc header lines
  • removes un-necessary commas from header lines
  • revised reply all parser to handle commas in descriptive names, including support for semi-colon delimiters
  • changed one address per header line for bcc
  • fixes incorrect representation of license expiry month
  • added reload function – Shift L
  • added display headers function – Shift H
  • adds additional sort trigger
  • improved outbox handling
  • improves error handling around IMAP APPEND messages
  • fixes problems with creating messages with non-roman characters including cyrillic, and allows for mixed cyrillic and roman text

The various bug fixes around handling non-Roman character sets now allow receiving and composing messages using mixed character sets.

mixedcharsend2

mixedcharrx2

Registered users can download version 1.1.11, 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

send failures

August 28, 2008

tiggit continues to have difficulties sending mail… In version 1.0.02 I  put loads of extra validation around the smtp protocol handler to be certain that messages have been successfully sent before removing them from the outbox. 

For some email services – notably Yahoo! –  this validation does not appear to work perfectly, resulting in messages being sent, but remaining in the outbox marked as failed.

The difficulty is knowing which messages have been sent, and which have actually failed. tiggit has a handy drop-copy feature that will automatically add a bcc address to all messages that it sends. This can be used to add yourself as a silent addressee to messages that are sent via tiggit, so that when you receive your own message you can delete it from the outbox.

Not really a solution I know, not even a messy work around, but until the bugs are fixed maybe a way of knowing whether a message has been sent.