OE Classic discussions and updates

- The info in post #274 is not quite accurate. Doing a "Binary Tree Search" does reduce the amount of comparisons. But the numbers are wrong. If you do this kind of search then the amount of comparisons needed is the square root of the total amount of entries. So, if the user has to search 25,000 entries then the square root of 25,000 is 159, not 8 (as stated above). But the current 159 comparisons is much much better than the previous average of 12,500 comparisons.

 

- OEC's Facebook page brought the message that the developers are "finalizing OEC version v3.0". More details on the Facebook page of OEC. But it didn't contain a release date.

https://www.facebook.com/oeclassic/

 

- OEC version v3.0 available:
https://www.oeclassic.com/
- Details on the major changes/improvements:
https://www.oeclassic.com/news

(I know that "Under the bonnet" there were (much) more (smaller) changes / bug fixes).

 

Thanks Willy.
You beat me . (I've removed my post about it)

 

- My personal recommendation is to make a backup of all the user data before upgrading to v3.0. The new version uses a new database structure that is not compatible with previous versions and something could go wrong during installation.
- The installation program of v3.0 will automatically upgrade the database structure during installation.

 

I hope the developers are aware about the End of Life (EOL) of OpenSSL 1.0.2 at the end of this year. OE Classic uses at the moment 1.0.2t.
See:
https://www.wilderssecurity.com/threads/more-openssl-security-fixes.366904/page-2#post-2876842
https://www.openssl.org/blog/blog/2019/11/07/3.0-update/

 

- New version of OEC v3.1 Beta PRO available.

"Fixed header decoding in few a rare cases". ? ?

 

Little corrections if I may :

It is OE Classic Pro version 3.1 beta
And actually there were two updates:
on 6 Dec 2019 - with that bug fix as you mentioned.
on 7 Dec 2019 - there was no change in the ReadMe text file (which gives the changelog) compared to the one from 6 Dec.

 

In the polls forum section there is a recent thread called "Email 2019": https://www.wilderssecurity.com/threads/email-2019.423944/
As I don't want to hijack that thread, I am carying over some of the postings from there to discuss here.

At reply # 1 @Circuit posted:

At reply # 2 @Buddel posted:

At reply # 3 @Circuit posted:

It is that reply # 3.
@Circuit : What exactly do you mean by that "cloud ( telemetry )"?

 

- Errors corrected in my previous post. Tried to find out where the recent version of the program may have been improved (more) but to no avail.
- Telemetry: I know that the program regularly checks for new versions. And then it sends some data with the version of the program to a server somewhere.

 

Thanks Willy and sorry for my late reply!

Yes, I too knew about the regular checks for updates. (PS: I would like an option by which you can enable/disable this). What exactly it sends for that checking, I don't know.
Anyways, that post "With-out that cloud ( telemetry )" by @Circuit wasn't enough for me. If you post something like that, you have to be more clear IMHO. That's why I posted it.

 

I've got recently an email with information about IMAP on OE Classic. That info can also be found at the News:
https://www.oeclassic.com/news

 

OE Classic 3.1 Pro beta - 13 Dec 2019

New features :

[2018-12-09] 2-layered header decoder (decodes HTML entities after decoding a header line)
[2018-12-10] Compact All - Changes page size to 4K for older databases which may still use 1K (it makes database operations faster)
[2018-12-12] Stripping of RE: and FW: prefixes now also recognizes prefixes in non-English languages (e.g. REF: TR: AW: WG: RIF: I: RES: ENC: etc.)

 

- My personal opinion is that fixing bugs in / improving IMAP should have the highest priority.

 

Here's some background information taken from Facebook.

Source: https://www.facebook.com/oeclassic

 

Sure, but IMAP isn't everything. The introduction of new features is always welcome.

 

Password protected, would be a nice improvement.
Not being able to open/read emails without a password.

 

You can use so-called identities, which are user profiles that can be password protected: https://www.oeclassic.com/online-help-identities
If this is not what you're looking for, you can get in touch with the developers, either from within the program or via their contact page, which can be found here: https://www.oeclassic.com/help

 

Should be time to make it possible to make OEClassic the default emailclient I think ? At last ?

 

- As time goes by the size of the OEC storage files will grow, grow and grow. OEC v2.9 wasn't able to remove ALL unused/wasted space from those files and reduce the size of ALL storage files (think: "Compact All" (File > Folder > Compact All)). That has been fixed in v3.0 (but it wasn't mentioned in the list with bugfixes).

- Agree. But other email clients already support IMAP. To make OEC a serious competitor for those other email clients OEC simply MUST include full support for IMAP. That's why I consider this (full support for IMAP) to be "Top Priority" for the next version of OEC.

- @ JaapOE: the developers also read this thread and I hope it has made onto their "top priority" list. Or go to the OEC website and send them a message reminding them on this topic. Are you a "Paid for" user ? If so, then it certainly has the chance of making it onto their "top priority" list.

 

Thanks for letting us know.

Thanks goes also to @Buddel for additional info often posted, like here.

===

Agree, but I would say that staying updated with OpenSSL is even an higher priority! See here. If you use third party libraries, you have to make sure that you keep yours updated. In general: I'm definitely not the only person who is warning about this. OK, minor updates may not be that important. And I have noticed that OE Classic is getting more quicker to update them. But now there is another situation: the End of Life (EOL) of OpenSSL 1.0.2 at the end of this year. OE Classic uses at the moment 1.0.2t. Whether the developers have some kind of extended support, I don't know.

===

In the meanwhile there was update OE Classic 3.1 Pro beta - 16 Dec 2019

[2018-12-16] Fixed antialiasing issues in the Message Editor toolbar

And the wording of these previous changes were changed in the ChangeLog into:
[2018-12-12] RE: and FW: prefixes are now also recognized and stripped for non-English languages (e.g. REF: TR: AW: WG: RIF: I: RES: ENC: etc.)
[2018-12-07] Fixed header decoding in a few rare cases

===

Merry Christmas to you all !

 

Making it the default emailclient : I did mention that already and it 's on the priority list, but IMAP came first.
I understand that.

Merry Christmas and a Happy New Year !

 

As far as "high priority" is concerned, the posts above this one clearly illustrate that we all have different priorities: making OE classic the default client, IMAP, OpenSSL security, ease of use, adding new features, full multilingual localization etc. The developers of OE Classic probably have their own list of priorities, and my own priorities may differ from other people's priorities. The developers of OE Classic work as hard as they can to implement all our personal priorities, but we should give them the time they need to properly deal with all the suggestions mentioned here and elsewhere. For the time being, let us enjoy using an email client that is getting better and better with every update.

Merry Christmas and a Happy New Year to all of you.

 

@Buddel
Oh yes, you are right about that, it's getting better and better.
But I still think it's important that one can make it the dafault email client.
I don't now any other emailclient that cannot.
Not ideal everytime to copy and paste emailaddresses on a website to send a massage.
But I agree, thay are doing there best .

 

- When I read the post of november 28, 2019 on this webpage
https://www.oeclassic.com/news

on the topic IMAP then it becomes clear that implementing IMAP has taken A LOT OF effort. It had to be compatible with e.g. Apple products. And that seems to have taken A LOT OF time as well. I also know that the first say 6 "IMAP alpha" versions were full of bugs.

Merry Christmas to all (with a Christmas avatar).