-
Notifications
You must be signed in to change notification settings - Fork 815
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible MAPI obsoletion with Windows 7 and Outlook 2016 EOL (October 14th 2025) #2368
Comments
Got an answer: Microsoft 365 will keep including Outlook, and « All versions of Outlook classic are built on and implement MAPI » (microsoft/MAPIStubLibrary#58 (comment)) despite the official Microsoft docs not mentioning that anywhere. Both Microsoft 365 and Outlook 2024 and set to be supported until at least October 9th, 2029: |
On a similar note, concerning ActiveX this time, according to this article: https://www.windowslatest.com/2024/09/15/microsoft-will-turn-off-activex-controls-in-office-2024-for-windows-11-and-windows-10/
Other source: https://www.techrepublic.com/article/microsoft-office-activex-disable-default/ and https://mc.merill.net/message/MC884011:
Also: MicrosoftEdge/WebView2Feedback#1371 (comment)
So maybe we can say bye-bye to ActiveX in 2029 as well 🤞 |
I'm opening this issue as a reminder and for documentation/archival purposes.
This concerns https://github.com/mhammond/pywin32/tree/main/com/win32comext/mapi
#2218 removed considerations for Windows CE, but it' still referenced in
pywin32/com/win32comext/mapi/src/mapi_headers/EdkMdb.h
Line 2175 in a83b36c
I went looking for possibly updated headers, but the link to MAPI headers download in https://github.com/mhammond/pywin32/tree/main/com/win32comext/mapi/src/mapi_headers is dead.
The same link has been removed from Microsoft's documentation
Jun 27, 2022
in https://github.com/MicrosoftDocs/office-developer-client-docs/pull/596/files#diff-a5a255563c0b615259f57792bb3e277c8e9827bfa24c7766f3c425cd0e12c146The following are now all dead links:
https://learn.microsoft.com/en-us/office/client-developer/outlook/mapi/outlook-mapi-reference and its subpages mention that MAPI only applies to Outlook 2013 and Outlook 2016.
https://learn.microsoft.com/en-us/exchange/new-features/discontinued-features?view=exchserver-2019#discontinued-features-from-exchange-2013-to-exchange-2019 mentions that
According to https://learn.microsoft.com/en-us/lifecycle/products/outlook-2016, Outlook 2016's support Mainstream End Date was
Oct 13, 2020
, and the support Extended End Date isOct 14, 2025
.From https://learn.microsoft.com/en-us/office/client-developer/outlook/mapi/installing-the-mapi-subsystem:
According to https://learn.microsoft.com/en-us/lifecycle/products/windows-7, Windows 7's support Mainstream End Date was
Jan 13, 2015
, the support Extended End Date isJan 14, 2020
, the support Extended Security Update Year 3 endedJan 10, 2023
and it doesn't look like there was a 4th year.The last Python version to support Windows 7 was Python 3.8 (https://www.python.org/downloads/windows/) and 3.8's end of life is around October 2024 (https://peps.python.org/pep-0569/)
PR to drop Python 3.8 support in pywin32: #2413
It doesn't even seem possible to download Outlook 2016 anymore, everything seems to redirect to newer Office 365:
Sidenote: I found that mingw-w64 is hosting MAPI headers, but I have no idea where/how they got it from: https://github.com/mingw-w64/mingw-w64/blob/master/mingw-w64-headers/include/mapi.h & https://sourceforge.net/p/mingw-w64/code/HEAD/tree/trunk/mingw-w64-headers/include/mapi.h
Sidenote 2: Thanks to the Wayback Machine, I found a 2020 archive of https://mapistublibrary.codeplex.com/documentation which redirects to https://archive.codeplex.com/?p=mapistublibrary which is archived with a message that leads to https://github.com/stephenegriffin/MAPIStubLibrary, which finally redirects to https://github.com/microsoft/MAPIStubLibrary
I opened a PR to fix Microsoft's own doc concerning MAPI source: MicrosoftDocs/office-developer-client-docs#777
The text was updated successfully, but these errors were encountered: