Difference between revisions of "Outlook Addin"

From regify WIKI
Jump to navigation Jump to search
Line 3: Line 3:
  
 
* Composing regimails
 
* Composing regimails
** No API to reliable get attachments and inline images ([https://github.com/OfficeDev/office-js/issues?q=is%3Aissue+is%3Aopen+inline+attachments source]).
+
** No API to reliable get attachments and inline images ([https://github.com/OfficeDev/office-js/issues?q=is%3Aissue+inline+attachments source]).
** No API to get attachments from forwarded messages ([https://github.com/OfficeDev/office-js/issues?q=is%3Aissue+is%3Aopen+forwarded+ source]).
+
** No API to get attachments from forwarded messages ([https://github.com/OfficeDev/office-js/issues?q=is%3Aissue+forwarded+ source]).
 
** No API to trigger sending after encryption ([https://github.com/OfficeDev/office-js/discussions/5191 source]).
 
** No API to trigger sending after encryption ([https://github.com/OfficeDev/office-js/discussions/5191 source]).
 
* Reading regimails
 
* Reading regimails

Revision as of 15:52, 16 December 2024

Outlook for Web (OWA) and New Outlook

We really tried to develop an add-in for new outlook and OWA. Unfortunately, the API that Microsoft offers does not allow us to create a regimail add-in. The main reason is the lack of API functionality provided. This is what we are missing (12/2024):

  • Composing regimails
    • No API to reliable get attachments and inline images (source).
    • No API to get attachments from forwarded messages (source).
    • No API to trigger sending after encryption (source).
  • Reading regimails
    • No API to set/replace body or delete/replace attachments (source). The alternative would be to create a new message with decrypted content in parallel. But see next point.
    • No API to create a new message in inbox folder with custom content.
    • Only an API to open the compose form, but this does not allow us to save to the correct location except of drafts folder. It would become sent or a draft. Both we don't want.

In addition, the API version provided by the users setup must support the needed API functionality. For on-prem installations of Exchange (2016, 2019), the maximum API requirement set is 1.5 (source) but for the most functions an API requirement set of 1.10 or even higher is needed. Such API requirement set levels are only available if your Outlook is connected to Exchange Online from Office 365 (hosted by Microsoft). Microsoft also did not yet announce, what API requirements set it will support for upcomming Exchange 2025 end of 2025.

Outlook Legacy

Supported versions

The current AddIn for Microsoft Outlook is available for the following versions:

  • Outlook 2019 (32 Bit & 64 Bit)
  • Outlook 2021 / Office 365 (32 Bit & 64 Bit)
  • Outlook 2024 / Office 365 (32 Bit & 64 Bit)

Please respect that we're no longer supporting Outlook before 2019. Running this e-mail client is also no longer secure. Please consider upgrading to a newer version or how about trying Mozilla Thunderbird?

Functions

The AddIn for Microsoft Outlook offers the following functions:

  • create new regify e-mails
  • forward, reply and reply all using regify
  • reconvert regify mails to ordinary e-mails
  • automatically reconvert while receiving
  • configure regify settings (account settings)
  • invite new users to regify

Setup

The Outlook AddIn is installed automatically (in the correct version) during setup of the regify client. If you do not like to install the Outlook AddIn during setup, please refer the "regify client software deployment documentation" for possible options. It is provided to you by your regify provider.