Are you sure it was either not encrypted or a "bounce" that the message
could not be encrypted? If encryption is forced with the subject
trigger, the message will only be "bounced" back to the sender if the
message cannot be encrypted. If you want to always encrypt the message
you either have to set a static password for all recipients, or select
"Send to originator" or setup the OTP password mode.
it was a bounce, the messages never got to the recipients mailbox.
It would be ideal, if it wasn't necessary to define a recipient profile, but the PDF encryption could be forced only by a subject trigger.
But since our client only has a limited number of recipient it would be okay to create a profile for each of them. In this case it is still the questions which parameters settings are necessary for the recipient?
It depends on the needs of your client whether or not you need to
manually add a user object for each recipient or not. Can you give some
more details on what the optimal "use case" for you client would look
like? i.e., how should the gateway work from the senders perspective.
Kind regards,
Martijn Brinkers
ยทยทยท
On 01/-10/-28163 08:59 PM, Stefan Michael Guenther wrote:
Hello Martijn,
Are you sure it was either not encrypted or a "bounce" that the message
could not be encrypted? If encryption is forced with the subject
trigger, the message will only be "bounced" back to the sender if the
message cannot be encrypted. If you want to always encrypt the message
you either have to set a static password for all recipients, or select
"Send to originator" or setup the OTP password mode.
it was a bounce, the messages never got to the recipients mailbox.
It would be ideal, if it wasn't necessary to define a recipient profile, but the PDF encryption could be forced only by a subject trigger.
But since our client only has a limited number of recipient it would be okay to create a profile for each of them. In this case it is still the questions which parameters settings are necessary for the recipient?