Hi Alex,
for OOMS to fuction you are aware that you need PGP Desktop on the clients.
When OOMS is activated PGP Desktop will trigger OOMS in the event that the client can't handle it.
Basicly it means it will transfer the mail for conversion to Universal/SEMS via the Client/Server Connection (in the SSL Tunnel) to the backend. The backend is then doing what the Policy is telling it to do.
In this case either Webmessenger, PDF Messenger, Smart Trailer invite, ....
If the mail encryption can be handled on client level it will happen there (PGP/S/Mime) and not being pushed via OOMS.
So be aware that if OOMS is being used it might happen that you have 2-3 Mail Transfers via the link.
Why ?
If the mail needs to be split and encrypted with the diffrent format you might end up with diffrent mails
Example:
1x Recipeint PGP
1x Recipeint S/Mime
1x Recipeint PDF Messenger
This means that 3 Mails will be generated.
2x Client Level Mails (1x PGP + 1x S/Mime) and one transfered via OOMS to UN/SEMS for PDF.
Hope that makes sense. But the cool part the user will not have any idea what happens (so long he is not reviewing logs or Notifier) and it will simply work for him.
So for OOMS to work PGP Desktop / Symantec Encryption Managment Desktop.