'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix OneNote Email Not Sending via Outlook Exchange
Question details
Users need to resolve an issue where OneNote successfully completes the process to email a page, but the message does not actually send.
- Product
- Microsoft OneNote
- Device & OS
- Windows
- Scenario
- Attempting to share a OneNote page by sending it directly through the built-in email feature.
- Observed behavior
- The email creation process appears to work locally within OneNote, but the generated message fails to leave the Exchange server, often due to an integration conflict with the New Outlook app.
Verify that you have the Classic version of Microsoft Outlook installed on your computer, as the 'New Outlook' application does not fully support OneNote's email integration protocols.
Change the Default MAILTO Protocol to Classic Outlook
Use this solution to route OneNote's email requests through the fully supported Classic Outlook application instead of the incompatible New Outlook.
The New Outlook for Windows handles default protocols differently than previous versions. Because OneNote relies on the MAILTO protocol to trigger email sending, mapping this protocol back to the Classic Outlook application resolves the server communication failure.
Click the Start menu and select the gear icon to open Windows Settings, or simply press the Windows key + I on your keyboard.
In the Settings menu, click on 'Apps' from the left sidebar, then select 'Default apps' from the list of options.
Scroll down the Default apps page and click on 'Choose default apps by protocol' or 'Choose defaults by link type'. Locate the 'MAILTO' protocol in the list, click on the current default application (usually New Outlook), and change it to the classic 'Outlook' desktop app.
Completely close Microsoft OneNote and reopen the application. Try using the 'Email Page' feature again to confirm that the message successfully opens in Classic Outlook and leaves the Exchange server.
Try WPS Office for Hassle-Free Document Sharing
If you frequently encounter integration errors or email syncing issues with Microsoft Office, consider switching to WPS Office. It offers a lightweight, highly compatible alternative with robust built-in sharing features that do not rely on complex Exchange server configurations.
Frequently Asked Questions
Why does OneNote act like the email was sent when it wasn't?
OneNote only confirms that it successfully handed the page data over to the default email client. If the default client (like New Outlook) fails to process the request to the Exchange server, OneNote is unaware of the failure, making it seem like the process was successful.
Can I still use the New Outlook as my primary email app?
Yes, you can continue using the New Outlook for reading and managing emails. You only need to change the specific 'MAILTO' protocol in Windows settings to point to Classic Outlook to fix OneNote's sharing integration.
What if Classic Outlook is not available in my Default Apps list?
If Classic Outlook is missing, you may need to install or reinstall it from your Microsoft 365 dashboard. The New Outlook currently functions as a separate web-based wrapper and does not automatically install the classic desktop client required for deep application integration.
