When to use the Zivver OWA Assisted Mail Submission (OWA-AMS) and how to configure it?

OWA-AMS is an additional feature in the Zivver Outlook Web Access Add-in. Do not use this information for different Zivver clients.

Implement OWA-AMS in your organization to:

1. Make the Zivver Outlook Web Access Add-in compatible with other third-party add-ins for Outlook Web Access.
   • For example an add-in that files sent messages in a Document Management System (DMS).
2. Enable the mail server of the organization to process outbound emails.
   • For example when the mail server adds a signature or a disclaimer to sent messages.
3. Enable a Secure Email Gateway (SEG) to process outbound emails.
   • For example Mimecast’s Secure Email Gateway.

Make the Zivver Outlook Web Access Add-in compatible with other third-party plugins for Outlook Web Access

After you send a Zivver message in Outlook Web Access, you might notice that a third-party add-in does not function at this time. This malfunction can have a relation with the OnSend event of Outlook Web Access. Add-ins use that event to do an action on the sent message. The Zivver Outlook Web Access Add-in triggers on that OnSend event as well and sends a copy to the Zivver backend. The mail flow rule that is setup for the Zivver OWA add-in blocks the further processing of the unsecured message. OWA-AMS can make add-ins compatible with each other.

Background information

If the Zivver Outlook Web Access Add-in mail flow rule would not block the further processing of the unsecured message then would this message be delivered to the recipient as a normal, unsecured message. This is not what you want when you send a secure Zivver message. Because of that, the Zivver Outlook Web Access Add-in mail flow rule blocks further processing of the unsecured message.

However, other third-party add-ins might rely on the unsecured message to do an action on the sent message. This is where Zivver OWA-AMS can play a role.

OWA-AMS makes sure that the unsecured message in Outlook Web Access is still processed when you send a secure Zivver message. The final step is to send the message to the Zivver backend to secure the message. If you implement OWA-AMS on your mail server (or Secure Email Gateway (SEG)), your message is always delivered as a secure message. Because the unsecured message will be processed after you clicked the Send button, every other third-party add-in can do an action on the sent Zivver message.