MS unwanted updates tonight...

....w¡ñ§±¤ñ wrote:
Frank Slootweg wrote:
...w¡ñ§±¤ñ wrote:
Frank Slootweg wrote:
...w¡ñ§±¤ñ wrote:
Frank Slootweg wrote:

If not, then I don't consider it to be an alternative, because it's
totally different and offers no migration/import part from OE/WM.

IMAP for many email accounts has been the easiest migration route to
Windows 10 Mail client since both OE and Vista, like Windows 10, support
IMAP.

IMAP is neither needed nor easy (except is the simplest of cases).

The other optional route for email accounts was available from 2008
through the fall of 2016 for MSA(Microsoft Accounts).
That migration route was DeltaSync for Outlook.com, Hotmail, Live, and
MSn accounts in Windows Live Mail which was an installable client on XP
and Vista.
- One need not use the WLM client thereafter but the route to 'push'
your mail and contacts to Outlook.com(fka Hotmail, Live. Msn.com) was
the method MSFT provided. Whether one like the approach or not, it
'was' available and is still available today, once installed[1] since
WLM12 still has the ability to import OE and WM mail into WLM for
copy/move into any email account supporting IMAP. While not all email
accounts support IMAP, the majority do provide IMAP and POP3 support.

I went from OE to WM to WLM, so I'm aware of what they can (not) do.

The bottom line, if you really needed to migrate the options were/are
available...but to do so the underlying requirement and expectedly so
was the need for a MSA account(Outlook/Live/Hotmail/MSn.com or 3rd party
registered email address as an MSA) or the use of IMAP.

Nope, because:

[...]

3. Windows Live Mail is another choice. I also think that's a poor
choice, but it too is a choice.

See my other response. WLM is bug-ridden, bordering on unuseable.

*If* WLM would be a realistic migration path, I would still be on it.

WLM has never been everyone's cup of tea, but when migration is the
concern - it was MSFT provided route. Not using then or now[1] doesn't
negate the option being available from MSFT.

You 'overlooked' my "WLM is bug-ridden, bordering on unuseable."
comment.

Hence WLM was *not* the "MSFT provided route". WLM was not even
adapted to work correctly on Windows 8[.1]. For example not looking at
Contacts and not being backed up by File History (because the WLM Store
Folder is in the wrong place).

WLM is also broken in other areas, such as FUBARring the structure
of imported WM folders and - as I mentioned before - not removing
expired messages from the POP server.

And these are only the WLM bugs which I can somewhat easily recollect
after some three years. There are probably others which I've forgotten.

[1] WLM while no longer available for download from MSFT's servers it
can be obtained via 3rd party hosting sites.

WLM no longer being available from Microsoft is probably a good thing.

[...]

Thus stating that no migration path was/is available from MSFT would be
in error especially since the option was available for over 8 years,
more than sufficient time for OE/WM users implementation.

Was it the best and easiest route? No.
Was/Is a migration route available? Yes

A 'migration route' which ends up with a broken MUA FUBARring your
existing mail, isn't one. Period.

[Dodging each and every argument duly noted.]

You missed the point. The methods for migration was/is available. Not
perfect but available - which was the basis of your point.

I did 'miss' any point, mainly because there *was* no 'point'.

You are clearly unable to counter the arguments, 'so' you shoot the
messenger. So I repeat:

A 'migration route' which ends up with a broken MUA FUBARring your
existing mail, isn't one. Period.

Unfortunately, if still waiting for migration from a a 21 year old
application(OE) or 14 yr old(Vista WM) - it's not going to be something
provided from MSFT's end - development and resources for those programs
ended 12 yrs. ago.

Don't move the goalposts, by rewriting history! WLM was broken from
the time that WM on Vista was still a current and supported product and
that support ended only (slightly less than) *one* year ago.

But feel free to keep riding that dead horse, that saddle isn't going
anywhere.

Feel free to be a Microsoft apologist who can't be bothered by facts
or arguments and has no other 'ammunition' than denial, belittlement,
shooting the messenger, etc..

Lol...still not understanding WLM design intent.

(Not) LOL, still dodging (and probably not understanding) the
arguments.

_ = For use with syncable(Contacts, Calendar, SkyDrive) MSA accounts
- Live, Hotmail, MSn and temporarily for Outlook.com until the DeltaSync
backend server was shutdown in favor of Office365 backend functionality.

The only OE targeted users were those who were using WebDav for Hotmail
and MSn accounts. WM users were never targeted since WM didn't support
WebDav. POP3 users of Hotmail and MSN were only targeted to switch to
WebDAV.

You must really love red herrings, considering how many you throw
around.

First you blabbered about IMAP and now WebDav. That shows that you
have no clue what is and what isn't involved in importing existing local
mail.

[Rewind/repeat:]

WM users were never targeted

*If* "WM users were never targeted", then *why*, oh wise one, can WLM
import from a WM Store Folder or from a WM Export [1] [2]!?

Hopefully you like egg and pie.

[More irrelevant drivel deleted.]

Moral: Limit your comments to subject matter which you actually
understand / know something about.

[1]

"Windows Live Mail Import

Import Complete

Your messages were imported in 'Windows Mail' format"

Note *'Windows Mail'*.

[2] And can import existing WM accounts (.iaf)