5/27/2020 Windows 7 Outlook Express Nederlands
Free Spam Filter for Outlook, Outlook Express, Thunderbird, Windows Mail. Spanish, Chinese, French, Italian, Greek, Dutch, Swedish, Norwegian, Suomi. Microsoft Windows XP (SP2), Windows Vista, Windows 7, Windows 8/8.1.
![]() ![]()
New features. 2019-12-09 2-layered header decoder (decodes HTML entities after decoding a header line). 2019-12-10 Compact All - Changes page size to 4K for older databases which may still use 1K (it makes database operations faster). 2019-12-12 RE: and FW: prefixes are now also recognized and stripped for non-English languages (e.g. At last, OE Classic 3.0 brings you IMAP support!At last, IMAP support! Also, new Junk Email special folder.IMAP is a protocol for accessing emails (different than the POP protocol), which allows you to sync emails across multiple devices (e.g. PC, tablet, smartphone, webmail).
When email is accessed on a particular device (for example, a smartphone), the next time you open OE Classic on your PC, it will register all the changes you did on the phone (e.g. Deleted emails, new emails, flagged emails, etc.). The opposite also works - all the changes done in OE Classic will be shown on other devices as well. In order to work, IMAP requires permanent and stable Internet connection. Adding IMAP does not mean that POP is getting removed.
You can choose which protocol you would prefer to use (assuming your email server supports both of them) when configuring an account using the OE Classic account wizard.Here is a summary of what OE Classic can do, using the IMAP protocol:. Synchronize messages across multiple devices (e.g.
Desktop PC, laptop PC, smartphone, tablet, webmail.). Deleting a message, flagging it, marking it as read - such changes will be shown on every device accessing the same mailbox and of course in OE Classic as well. Messages are stored on the IMAP server (in the 'cloud'), meaning, if emails are lost on your computer (e.g.
![]()
By a disk failure), the email messages are backed up on the server, so by adding the IMAP account again in OE Classic, you will be able to access your emails again. Messages are cached locally (on your disk), once they are opened the first time, so opening them is faster if they are unchanged on the server. OE Classic flagging is compatible with iPhone/macOS Mail app – so it supports multicolored flags (red, green, yellow, blue etc.). These flags color coding is identical the iPhone/macOS Mail app, and possibly some other IMAP-capable applications as well. OE Classic is also compatible with non-standard (but commonly used) IMAP flags like $Forwarded and $MDNSent (labeling a message as forwarded and message delivery notification sent mark). OE Classic uses an atomic move to folder operation (MOVE extension) as supported by modern IMAP servers like Gmail.com or Outlook.com.
After long development time, OE Classic 2.9 is finally available. At last, this version brings multilingual support in 11 languages! More languages will be added, depending on interest and translations will improve in subsequent versions. There are also many smaller changes here and there - improved Message Editor, improved Find window and some important bug fixes.
Last but not least, accessibility support has been improved in various areas of the program.OE Classic now speaks 11 languages and the multilingual support will continue to improve in the new updatesFormatting buttons such as Bold, Italic, Underline etc. We are happy to report that OE Classic is one of the most secure programs available based on the independent research regarding the recently discovered 'Mailsploit' set of vulnerabilities. There are as many as 30 other email clients affected by these vulnerabilities including some of the very well known ones.OE Classic is completely unaffected! In fact, it has been unaffected for at least 3 years now, long before the discovery of this.By using OE Classic, you are safe against this one and also many other email threats because OE Classic employs various other security measures to protect you.
As you may know, we carefully monitor everything that happens in the world of computer-security and whenever we learn something new, we implement that in OE Classic to pass on that protection to you as well. You can see more info on all the work done over the years on this page.Over the years, we also warned our users how unsafe it is to use older operating systems and older email clients which don't take security as seriously as we do and we're so glad others are taking notice of that as well!References and links to the research:. New website design is now live! As we moved to a better and modern web server which hosts this web site, we discovered that the contact form within the program has stopped working on Windows XP and older.
This happens because Internet Explorer 8 (or older) on Windows XP does not support secure connections required by the web site.This is not a problem for Internet Explorer 9 and Windows Vista and anything more recent than that so this is not a problem for Windows 7, 8 or 10. Therefore, we will likely not be fixing this problem. Windows XP is simply too old and you cannot fix things forever - everyone else already abandoned it.
Checking for updates still works as that does not use secure connection to the web site (it is not required).The reason why this doesn't work is because Windows XP does not support modern encryption (longer and more secure ciphers) which are now used by our new web site, so we decided to stop support for program built-in contact form for Windows XP in favor of users who already use more recent versions of Windows to provide them with more secure experience. It is not a good decision to leave 97% of our users with weaker encryption because the other 3% just don't want to upgrade from Windows XP. As protection of user's privacy is one of our guidelines and server can only use one encryption, we have to take side and we choose modern encryption. Once again, this does not affect Windows 7, 8 and 10 users at all.
They will see no difference.Users who still wish to run OE Classic on Windows XP can continue to do so, the program will still work, except for the contact form which is tied into the web site. They can still contact us using web page using some other web browser than Internet Explorer (also note that Chrome and Firefox web browser developers have also stopped support Windows XP and Vista for a good while now).Once again, we urge you to upgrade from this obsolete and insecure version of Windows to something more recent (Windows 7, 8 or 10) - if you haven't already done so. We wrote a good number of times how insecure Windows XP and Vista are by modern standards. This update brings so many great new additions to OE Classic.
In fact, there are so many that text description won't do! There is no other word for what we're about to announce!For the last few years OE Classic depended on third party message decoder/encoder which worked OK, but always had certain annoying misbehavior as well as lack of flexibility in message decoding and bugs which were never fixed. For example, some messages were decoded improperly and there was no ability to user-customize them, such as user-selection of code-page so the incorrectly shown characters would be decoded properly for misbehaving messages. It was not very fast either and it offered no ability to skip decoding of unnecessary email items or decode them when they are really needed (on demand).On top of that, some of these components are also very expensive - some of them cost a few thousand USD (per year!). Although we would happily pay for that, assuming they worked per our specification. But they did not.Lacking control over the code and after years of asking (read: almost begging) for developers to fix these and other issues or at least make it more flexible, we finally got tired of all that and promised ourselves that we won't cause our users to suffer because of the lack of their understanding of what message decoder really needs to do.So we decided to roll our own message decoder/encoder. It took about 2 weeks so far but the work done is just AMAZING.
Over 2 times faster than the current one when decoding and over 3 times faster when encoding a message. Full flexibility to finally fix all the misbehaving messages which surfaced over the years.
Ability to give user choice of code-page and much better auto-detection when code-page is not properly specified. And also, much faster evaluation of the message to determine if decoding is really needed or not.The end result of this is that the operations related to message decoding (which is opening or downloading of any message) will be significantly faster and this will give users really great experience.
It is highly addictive to get used to this speed - once we got used we didn't want to go back to the old one, but there is some more work to be done with regard to testing before we can roll it out to the public as we want it to be made with the same highest standards our users have come to expect from us over the years.This means it has already passed through millions of auto-generated messages to test for any possible failures with zero errors. It also went though a few gigabytes of our test store folder.This is big change although it won't be as visible as some other features - but this one literally will be experienced by every user of the program because 100% of the messages will be passing through this decoder/encoder so it is the core of the program. It is of utmost importance for this to be fastest and top quality piece of programming and any compromise with it just wasn't an option.There is still some work to be done and we will be rolling it out gradually, but do expect a great decoding accuracy as well as speed improvement from it once it is merged into the main program! It appears that AT&T / Yahoo based email addresses might have occasional issues with TLS 1.0.
So, if you use any email address ending with @sbcglobal.net, @att.net, @yahoo.com and the like, try using TLS 1.2 in Expert account properties - which might behave more stable than TLS 1.0 with these addresses. If it doesn't work you can always revert back to TLS 1.0. TLS 1.2 is more secure and more future-proof and in this case might cause more reliable connection to the server. But it does not work for all servers, only those which support it.TLS 1.2 setting offers better security but does not work for all email servers.
Have you heard of WannaCry, the latest ransomware attack on Windows XP, exploiting the EternalBlue vulnerability and leaving users of Windows XP with encrypted files with option to either pay the ransom (not recommended) or permanently lose the files (if they have no backup)?Sadly, many have not and still continue to use Windows XP in spite of our warnings that the support for it has ended in 2014, leaving it open to any malware released afterwards. Maybe Windows XP (and Outlook Express) used to be good, but it is time to move on and continuing to use it is just a terrible idea (from the security standpoint).Don't forget that OE Classic works on more recent Windows such as Windows 7 or Windows 10 just as good as it does on Windows XP - in fact, it works better due to built in features of Windows 10 it utilizes.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |