Its been a long time in the making, but I'm please to announce that LogicMail 2.0 has now gone into beta. This beta marks a major milestone in the project, and is the recommended version for all new installations. For anyone still running 1.1, or anyone seeing this application for the first time, here are some key new features in version 2.0:
- Step-by-step setup wizard
- All network communications now happens in the background, and mail data is now locally cached
- Improved look and feel
- Support for both local and remote Sent/Drafts folders
- Ability to copy messages between folders, even across accounts
- Improved message composition, with an Outbox that holds messages until successfully sent
- Keyboard shortcuts mimicking the native messaging application, and touchscreen device support
- Able to read E-Mails written in many different languages and character encodings.
- Supports OS 4.5, 4.6, 4.7, 5.0, and 6.0
- Any plenty more!
For a walkthrough of downloading and installing with screenshots, visit the new Setup Guide!
P.S. You do still need to know how to setup an E-Mail client to talk to your E-Mail service (via IMAP/POP/SMTP). This really isn't that difficult, and the settings are no different than what you'd use with any other desktop E-Mail client. (I am investigating some autoconfiguration options for future versions.)
Its been over a year since the last 1.x maintenance release, and more than two years since the bulk of my effort shifted to the 2.0 code. With all the people that have been actively running the development builds over the past year, its about time that this code went out to the masses! Through the beta period, we'll be working on fixing any remaining bugs and bringing all the translations up to date. While this first beta build is English-only (for the application text), I hope to have many more translations included in future beta releases.
Now for the caveats... Unfortunately, the most user-requested feature of all time (background message polling, #79, #79, #169, #212) had to be postponed to 2.1. This was a difficult decision, and it took a lot of thought to arrive at it. It took a lot of time and effort to bring the application's architecture up to the point where it was possible to implement this feature in the first place. Now that we're there, its simply a matter of time and resources. Its the sort of feature that may not be too difficult to implement now, but will be a nightmare to test and debug. If I had held out for it, then 2.0 might take another few months to get to release. Given how long its been since 1.1, I felt it was more important to get 2.0 out now, in its current form, and just make 2.1 my next priority.