OE Classic discussions and updates

No problem of course!
I just tried it, changing from English to German, from within the program itself. That doesn't seem to work on my system. Anyway, I want it to be in English. I was just curious.

 

It doesn't work here, either. I tried to change from English to German during the installation process - no luck. Then I tried to change languages within the program - that didn't work, either. I'll drop the developer a line later today.

 

Got an email from the developer today. Multi-lingual support is currently restricted to the "Account wizard". I've just tested it, it works. More comprehensive localization will follow within the next few days/weeks.

 

Thanks Buddel!

1. I don't know what "Account wizard" means here. What are exactly the required steps here from within the program itself (in case a person wants to change the language)?
2. Why is there the option (from within the program itself) in Help > Select Language to change the language if that option doesn't work? Strange.

 

(1) Tools > Accounts > Add
(2) Localization is still in the works. This option should work as soon as localization is fully implemented.

 

OK, thanks.
I realize that most updates for the Pro version are beta's, but IMHO it would be better when there would be a clearer explanation of new and/or fixed "features" (and not only on Twitter and Facebook (if they were posted there); some users don't go there)).

 

I agree. There is definitely room for improvement in this respect.

 

there is an update today.
Buddel, my dear friend, may I leave the rest to you, please (way too much eye vision problems again lately here)

 

Great news on OE Classic security!
https://www.oeclassic.com/news_n78

OE Classic v2.8 Pro Released (December 7, 2017)
News

 

Yes, my dear friend, OE Classic Pro 2.8 was updated a couple of hours ago.

New feature: Added multilingual support
Bug fix: No longer jumps to the top of Address Book when items are deleted (Address Book and Main window)

 

@mood The "Mailsploit" vulnerabilities are also discussed at Wilders:
https://www.wilderssecurity.com/thr...il-apps-allow-spoofing-code-injection.398510/
And yes, OE Classic - unlike Mozilla Thunderbird and Microsoft Outlook - is indeed unaffected.

 

Thanks Buddel and mood.

=====

having compared new and previous readme.txt the only difference is:
bug fix [2017-12-07] No longer jumps to the top of Address Book when items are deleted (Address Book and Main window)

=====

it's time libeay32.dll and ssleay32.dll gets updated in OE Classic
they are still at version 1.0.2l
See:
1 - https://www.wilderssecurity.com/threads/more-openssl-security-fixes.366904/page-2#post-2723701
2 - http://www.securityweek.com/two-vulnerabilities-patched-openssl
3 - https://www.openssl.org/news/secadv/20171207.txt :

The vulnerabilities may be rated as low and moderate, but nevertheless.

 

I agree that it should be updated, but 1.0.2n was released on the same day as the new version of OE Classic.
Perhaps the next version of OE Classic includes the new version of OpenSSL (1.0.2n)

 

Hi mood,

Yes I do know that the updated version of OpenSSL 1.0.2 was released on the same day. I do understand that you cannot expect that that update will get included the same day into OE Classic.
But there is more than this:
About a month ago there was a previous update from OpenSSL:
See:
1. reply 42 in this thread.
2. Post by Ron here
3. http://www.securityweek.com/openssl-patches-flaws-found-google-fuzzer
4. https://www.openssl.org/news/secadv/20171102.txt
The OpenSSL organisation did advise there to upgrade to version 1.0.2m.
That vulnerability may not have been the highest rate, but nevertheless.
That is a month ago! That is enough time, I would think.
If a developper uses OpenSSL, then you would expect him/her to keep him/herself informed about upgrades of OpenSSL and to include those upgrades as soon as possible.
The developper can brag all day long about that Mailsploit at the OE Classic site, but keeping upgraded with OpenSSL seems to be too difficult ...

 

Maybe they forgot about OpenSSL
Or it is not a high priority because the Severity is "only" Low and Moderate.
For example OpenSSL v1.0.2.g has one "High" Severity (https://www.openssl.org/news/secadv/20160301.txt) and OE Classic v2.4 was released (including 1.0.2.g) shortly after that.

 

Localizers wanted

If you are interested in localizing OE Classic and making it available in as many languages as possible, please PM me. I will forward your posts to the developers of this email client, who will give you more detailed information. Please mention in your post whether or not you are a Pro user of OE Classic. Thank you.

 

OEClassic 2.8 Beta has just been updated [15 January 2018]

Complete changelog can be found here: https://www.oeclassic.com/news
BTW, the first translation files have been added to the new Beta build.

 

Thanks Buddel. Updated.
Looks like there were several internal builds between 7 Dec 2017 and 15 Jan 2018; that's ok.
Good that there are (hopefully) more languages coming, very good! I had a very quick look at one of them; it seems to be still in the early stage from what I saw, but I guess that at this moment you can't expect more; too early stage.
(I'd better keep my mouth shut about some dll's; a person cannot keep on repeating himself).

(PS: please fix that smiley in your post. The combination of characters 8 and ) in the year).

 

The localization process has only just begun. As far as German is concerned, most words and phrases are localized already but it's far from finished.

PS: Smiley fixed.

 

OEClassic 2.8 Beta has just been updated [19 January 2018]

• [2018-01-18] Added 7 initial language files (Croatian, Dutch, French, German, Italian, Japanese, Spanish)
• [2018-01-19] Option to set default message direction right-to-left

Complete changelog can be found here: https://www.oeclassic.com/news

 

And here is today's OE Classic update [21 January 2018]

• Save As message saving now also offers HTML or Text formats

 

Thanks my friend.
There is now another update [22 January 2018]
The ReadMe.txt files for 21 Jan. and 22 Jan. are the same, as far as I can tell.

PS: Thanks to the translators

 

You're right. The ReadMe.txt files of the two days are identical. Today's update is probably just a minor bug fix.

 

There was another update at 26 January 2018.
Again no newer changelog: the ReadMe.txt file is still the same.
(maybe only some translations were updated; work in progress)

 

Yep, the translations are WIP (work in progress).