Language Selection

English French German Italian Portuguese Spanish

What Thunderbird 1.5 should have been

Filed under
Software

Somewhere between Evolution and Mozilla Thunderbird is my perfect mail client. Evolution has three features that get me salivating: the calendar; the ability to make rules with a simple right-click on a message; and its tight integration with Gnome.

Then there's Thunderbird. Its user interface is cleaner and simpler (I think this has a lot to do with the fonts the developers chose), its super-fast (particularly compared to Evolution), and its IMAP support is excellent.

Its with these criteria in mind that I joyfully downloaded the latest version of Thunderbird - version 1.5 - and went through the rather painful jump from Evolution to the Mozilla mail client. I haven't used Thunderbird for quite some time, so I expected some big changes. Unfortunately they were not forthcoming.

What does version 1.5 give us that version 1.0 didn't? It's got a scam detector that marks just about any newsletter and e-zine as a scam - including Tectonic's weekly newsletter. There's a spell checker that checks as you type. You can get podcasts. And that's about it.

Sure, there are other changes - an improved updates engine and security fixes - but not a whole lot of stuff that really makes a difference to me as a user. Considering the massive amount of development on Thunderbird in its initial year of existence, this version bump is pretty poor, especially since the move is from version 1.0.7. If this is the half-way mark to version 2.0, I'm not holding my breath.

So instead of doing a review of the new Thunderbird - if you've seen version 1.0, then you've seen version 1.5 - I'm going to make a wishlist for my ideal mail client.

Full Article.

ideal mail client

Everyone is entitled to their own 'ideal'. Mine is quite different to the author of this article because I want my mail program to deal with plain text mail, nothing more and nothing less. I see no reason why mail program should include a calendar (aren't there enough calendars on the desktop yet?) or deal with RSS feeds (that's a job for a browser, I think. I don't really use RSS feeds anyway). Importing mail is simple enough with mbox and IMAP both available; anything else should be handled by a separate utility rather than adding bloat to the program with feature used once in a blue moon... Just about the only thing I can agree with is filtering on a mailing list. Yes, that would be handy.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Security Leftovers

10 hot Android smartphones that got price cuts recently

With numerous smartphone getting launched each month, brands always adjust prices to give slightly competitive edge to older smartphone models and also to clear inventories. Here are 10 smartphones that got price cuts recently. Read more

Debian and Ubuntu News

  • Debian Project News - July 29th, 2016
    Welcome to this year's third issue of DPN, the newsletter for the Debian community.
  • SteamOS Brewmaster 2.87 Released With NVIDIA Pascal Support
  • Snap interfaces for sandboxed applications
    Last week, we took a look at the initial release of the "portal" framework developed for Flatpak, the application-packaging format currently being developed in GNOME. For comparison, we will also explore the corresponding resource-control framework available in the Snap format developed in Ubuntu. The two packaging projects have broadly similar end goals, as many have observed, but they tend to vary quite a bit in the implementation details. Naturally, those differences are of particular importance to the intended audience: application developers. There is some common ground between the projects. Both use some combination of techniques (namespaces, control groups, seccomp filters, etc.) to restrict what a packaged application can do. Moreover, both implement a "deny by default" sandbox, then provide a supplemental means for applications to access certain useful system resources on a restricted or mediated basis. As we will see, there is also some overlap in what interfaces are offered, although the implementations differ. Snap has been available since 2014, so its sandboxing and resource-control implementations have already seen real-world usage. That said, the design of Snap originated in the Ubuntu Touch project aimed at smartphones, so some of its assumptions are undergoing revision as Snap comes to desktop systems. In the Snap framework, the interfaces that are defined to provide access to system resources are called, simply, "interfaces." As we will see, they cover similar territory to the recently unveiled "portals" for Flatpak, but there are some key distinctions. Two classes of Snap interfaces are defined: one for the standard resources expected to be of use to end-user applications, and one designed for use by system utilities. Snap packages using the standard interfaces can be installed with the snap command-line tool (which is the equivalent of apt for .deb packages). Packages using the advanced interfaces require a separate management tool.
  • Ubuntu 15.10 (Wily Werewolf) Reaches End Of Life Today (July 28)
  • Ubuntu MATE 16.10 Yakkety Yak Gets A Unity HUD-Like Searchable Menu
    MATE HUD, a Unity HUD-like tool that allows searching through an application's menu, was recently uploaded to the official Yakkety Yak repositories, and is available (but not enabled) by default in Ubuntu MATE 16.10.

Tablet review: BQ Aquaris M10 Ubuntu Edition

As employees have become more and more flexible in recent years thanks to the power and performance of mobile devices, the way we work has changed dramatically. We frequently chop and change between smartphones, tablets and laptops for different tasks, which has led to the growth of the hybrid market – devices such as Microsoft’s Surface Pro 3 and Apple’s iPad Pro – that provide the power and functionality of a laptop with the mobility and convenience of a tablet. Read more