Hello Stefan Falk,
Thank you for posting in Q&A forum.
Here are the suggestions for your references.
1.Please make sure the users can send email via Outlook app.
2.Please check if the problem occurs suddenly (I mean it worked fine in the past or the send way does not work in your environment), if so, you can try to check the changes or updates you made recently.
3.The Explorer shortcut relies on Simple MAPI. If Outlook isn’t correctly registered as the default MAPI handler, the shell call can bounce back with errors. You can try forcing Outlook to re-register its MAPI settings by running (from an elevated command prompt) a command like:
"C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE" /regserver
Please note: Always back up the registry before you make any change.
4.In Terminal Services environments, it’s important that both the calling process (Explorer) and the e-mail client (Outlook) run in the same user context. For example, if Outlook is running elevated (as Administrator) and Explorer is not (or vice versa ) the MAPI call may fail. Ensure that Outlook is started in the same “non‐elevated” user context as the session.
If it does not work above, the recommended “workaround” is to open Outlook and attach files manually (or use drag–and–drop) rather than relying on “Send To → E-mail Recipient.”
While Outlook 2019 does include the underlying MAPI support so that in theory the right‐click “Send To → E-mail Recipient” could work, in practice it may be not a supported or recommended scenario on Windows Server 2019 Terminal Servers.
I hope the information above is helpful.
If you have any questions or concerns, please feel free to let us know.
Best Regards,
Daisy Zhou
============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.