back
Oct 06, 2026

Release Notes v3.0.0

With this release, Sendent for Outlook is renamed to Nextcloud for Outlook. You'll see the new name and logo in Outlook and in our documentation. Functionality, settings, and licenses stay the same, so no action is needed. Read more about the rebrand.

New

  • Rebranding to "Nextcloud for Outlook": The add-in has a new name and branding.
  • Nextcloud theming: The add-in uses the accent colours from your Nextcloud server's theme.
  • Domain allowlist: Admins can set which domains the add-in is allowed to work with.
  • Signature support: The add-in now supports email signatures.

Improved

  • Sign-in: A dialog shows sign-in progress. Sign-in finishes faster when you return to the task pane. If several sign-in windows are open, only the first one to complete is used.
  • Secure Mail attachments: Files you add yourself stay in place if you leave the Secure Mail page, for example to open Settings. Each file now has a label showing whether it came from the email body or from your device.
  • Sending with uploads: You can't start a second upload while one is already running in the on-send dialog, and the dialog buttons are disabled until the upload finishes. The Cancel button was removed from the progress dialog because it never actually stopped the upload.

Fixed

  • Share expiry now uses the "Share expiration days" and "Number of days" settings from the Nextcloud app.
  • The Secure Mail recipient list now stays in sync with the email's recipients.
  • The share link is now inserted correctly when the cursor isn't in the email body.
  • A Secure Mail email containing only text, with no attachments, now goes through the Secure Mail flow. The email body is attached to the Nextcloud share.
  • Embedded images, such as the logo in the share snippet, no longer wrongly open the file intercept dialog.
  • Embedded images are attached correctly when sending from Outlook on the web and the new Outlook for Windows.
  • Replies with embedded images and long conversation history are less likely to fail and end up in Drafts. The commit author could not reproduce this issue, so this fix is unconfirmed.