This guy from Igalia has the new Air laptop thing already, go check it out!

Video by this guy.

The same rfc2047 decoder fixes that Jeffrey did for upstream Camel are of course ported to Tinymail’s parsing code. So E-mail clients like Modest will also parse those broken E-mails correctly (once you update your Modest packages on your Nokia devices, of course).

Of course are Nokia’s testers testing the application with such broken E-mails. We are indeed seeing that more E-mails can be displayed correctly with Jeffrey’s new rfc2047 decoder. Usually spam succeeds more often now. Legitimate E-mails are less frequently broken. I guess spammers want to fool weak rfc2047 decoder implementations in spam detection softwares.

For the last few weeks I have been synchronizing the embedded Camel of Tinymail with Camel upstream. Other than bringing upstream’s bugfixes to Tinymail, this will of course make it more easy to port features back to Camel upstream. I must stress again that a lot of the new features are specific for mobile use cases and that a lot of them are not done in such a way that they can easily be ported. Others are simply not very interesting for a desktop E-mail client, and some are.

First of all, a summary is the overview of your E-mail folder or mailbox. It shows you the cc, to, from, subject of each E-mail. In IMAP terminology people also call this the ENVELOPE of each E-mail. Showing all ENVELOPEs of a folder is showing the summary to the user. Some people want more than just the cc, to, from and subject to be visible. Most E-mail clients also indicate the read and importance status of the E-mails in this view. Some E-mail clients also show the size of the E-mail. Whatever yours shows, that is what I’ll here call … the summary.

Igalia and Dirk-Jan C. Binnema from Nokia just announced the availability of Modest’s first public beta. You can find the one-click install link at their announcements.

[17:03 today] <juergbi> pvanhoof: i’m reading email with a vala tinymail client now :)

I just documented TMut. I think this documentation will help E-mail client developers who are planning to use Tinymail a lot. Some of them will probably take a look at how I did TMut and now they’ll have some documentation about how and why I did certain things.

Also the client developers who’ll start their E-mail client based on TMut will enjoy reading the documentation. If somebody wants to create a client based on TMut, and if for that we need to make TMut a static library in stead, just ask of course (or just send me the patch that adapts the Makefile.am for this).

You can enjoy my normal English as Tinne is at this moment sleeping and I don’t want to wake her up to correct my poor English. The language purists will have to wait for her language correcting until at least tomorrow, or correct it themselves (it’s a wiki, go ahead). Perhaps we should go over all of Tinymail’s and TMut’s documentation once more. It has been a while since we last did a massive spelling correction campaign.

Anyway, here are the most interesting added subjects:

• Creating messages
• Select a folder window
• TMut’s menu, its first screen
• Showing the summary of a folder
• The message view component
• TMut’s frame & window setup

Have fun

Note (edit): Some people prefer me to call IMAP’s Push-Email “notifications”. That’s fine of course. Just replace “Push” with “notification”.

An IMAP server is smarter than a POP server. This, I hope, comes as no surprise to most people. An IMAP server has a MIME parser and can give you the BODYSTRUCTURE of a message. This is useful because that means that you can individually request the parts of a message, rather than always fetching the entire message. In future you can also CONVERT those to for example thumbnail versions. (I already started implementing support for CONVERT in Tinymail)

ps. Build instructions for everything, here. No I don’t know whether that will work with your 770. Yes it’ll work with your N800 and your N810.

By requesting the BODYSTRUCTURE you can get a preview of the structure of a message without having to download it. Most E-mail clients parse this structure to the point of what they need from it. I did some searching and as I expected did few of the opensource E-mail clients do a complete parse. Some just scanned for some words, others did a reasonably well job but skipped information that they are simply not interested in. And that’s fine, if you don’t need it.