Windows Live Mail Download 2022 NEW!
Sharyl Viken
Windows Live Mail (formerly named Windows Live Mail Desktop, code-named Elroy[2]) is a discontinued freeware email client from Microsoft. It was the successor to Windows Mail in Windows Vista, which was the successor to Outlook Express in Windows XP and Windows 98. Windows Live Mail is designed to run on Windows 7 and Windows Server 2008 R2, but is also compatible with Windows 8[1] and Windows 10, even though Microsoft bundles a new email client, named Windows Mail, with the latter.[3] In addition to email, Windows Live Mail also features a calendar, an RSS feed reader, and a Usenet newsreader.
Windows Live Mail moved away from the older Microsoft mail programs, such as Outlook Express, which stored all e-mails comprising a folder (such as the Inbox) in a single .dbx file. In order to provide greater flexibility (and to avoid the problem where corruption of a single .dbx file could delete multiple emails), Windows Live Mail stores each email message as a separate .eml file. Only the folder structure is maintained in a single database file, using the ESE (Extensible Storage Engine) database structure, named Mail.MSMessageStore (which also holds some metadata for each .eml file on the system, so can be a huge file). The program also maintains a backup copy of that file, in the Backup sub-folder, so problems are rare. At a pinch, the Mail.MSMessageStore file can be recreated from the data in the .eml files.[citation needed]
Since around 2013, serious problems with Windows Live Mail 2012 (but not with Windows Live Mail 2011) have been reported on various blog sites (including Microsoft forums). One problem is that deleted emails keep returning day after day.[9] Another development that caused complaints is the Live Mail Sent folder erroneously containing the name of the Sender rather than the Recipient in the To column, while omitting the sender's account name in the Account column (as the fault only affects that folder, a workaround is to move sent items into a new folder, named - for example - "Sent 2019").[10] Discussions on the forums have provided no clear solutions to these issues.
Although use of DeltaSync has been discontinued on Microsoft's servers since 30 June 2016, Windows Live Mail 2011 and 2012 continue to work with Hotmail e-mail accounts by using IMAP (or, less effectively, POP3) instead of DeltaSync.[12][13] Gmail and other service providers still support DeltaSync,[14] so users can still use Windows Live Mail 2011 - connecting with DeltaSync - with non-Microsoft email accounts (but not Windows Live Mail 2012, as DeltaSync support was removed from it). Additionally, Windows Live Mail 2011 and 2012 continue to function with all non-Microsoft e-mail services, by using IMAP (or, less effectively, POP3) instead of DeltaSync.[15]
We have received yet another complaint today about our emails not working in Windows Live Mail. Is there really nothing that can be done to deal with the underlying problem? Despite lack of support from MS, Windows Live Mail, like Outlook Express before it, isn't going to disappear any time soon, and it's much more recent an app than, say, Windows XP where LE didn't work either when first released.
I don't know much about CRL, but is there maybe some way to make a bridge back from OCSP data to CRL, enough to make the obsolete Live mail program work even if revocation isn't possible there, or some way we might be able to patch Live Mail. Might an approach to Microsoft be helpful?
Well, the reason I'm raising it is because it has relevance for more than just me. It took us nearly a year before anyone even bothered telling us that this was a problem - most of the time, as I said, people just move on elsewhere. I suspect many people using images in email have the same problem, just don't know it because none of their recipients has pointed it out to them. Now I know about it, I can indeed tell people that there is a setting they can change, though it seems to be "turn off all images from everyone" from what I can see so far, which won't go down well either. I doubt most people using MS Live Mail know that it is obsolete.
The XP issue was also effectively deemed "impossible to solve" when it was first raised! I'm not looking for miracles, but this is a genuine problem. It may be small in percentage terms, but there must still be millions of active Live mail users out there, for whom images work in emails except where the sender uses a LE certificate.
I think maybe the best answer short of dealing with the problem directly is to use http image links which redirect to https except for the known problem clients. We still do this for IE8 on XP where SNI is a problem, so that mechanism is in place. The main issue then is for the people preparing the mailshot to understand the issue and not blindly put in URLs to the images straight from the website (i.e. Wordpress media library).
I created my public and private key on my server, but I can't work out how to set up digital signing with Windows Live Mail. Just to be clear, I'm talking about my own domain email account and not a hotmail account.
Ideally, you'd use a plug-in for Windows Live Mail, but I highly doubt one exists. If it doesn't, you need to get a front-end for GPG. If the front-end you choose allows you to encrypt the current window (you really want to find one that does this), you can type your email and then use the "Encrypt current window" option to clear sign or encrypt the text. If it doesn't allow you to encrypt the current window, you have to cut the text to the clipboard, sign and/or encrypt the contents of the clipboard, and paste it back into your email.
Q: If I have installed Outlook as the primary email application have I created a sufficient mitigation for the MS10-030 exploit?A: Yes. Outlook is not vulnerable to this specific vulnerability and cannot be attacked. However, we still recommend installing this security update as it addresses the vulnerability in inetcomm.dll, a library which is used by the lightweight e-mail clients Outlook Express, Windows Mail and Windows Live Mail. While Outlook is not vulnerable, these three applications would still be vulnerable if used accidentally by the user. Hence we do recommend installing this security update even to those systems where Outlook is set up as the primary e-mail application.
Q: Do you see any chance for another attack vector changing the existing mail preferences/settings or adding a new mail account that would point to a malicious mail server?A: No such attack vectors have been identified during our investigation. A user would have to manually configure a malicious server and check mail using it, or an attacker would have to alter data in transit on the network for this vulnerability to be exploited (which is the man-in-the-middle scenario). An attacker cannot remotely change mail preferences or settings without convincing the user to make these changes his or her self.
Did you respond via email using the notification you received from the community email? If so, it will not work; you need to manually send an email using the steps here, How do I private message (PM) in the community
So either your From address is somehow wrong, or your email provider needs to update their DNS configuration. The former you may be able to fix yourself, but the latter is up to the IT team of your email provider.
df19127ead