Send an encrypted message and ensure a saved copy is saved in yr mailbox.
If you access this message with another ID that has access to the mail box, the msgbox displays. “Parts of message are encrypted and YADA YADA YADA”
All OK so far.
Create a formula agent that adds a new field and with a value and if the field exists deletes that field
Field TEMP1 := @if(@available(Temp1); @Deletefield; “1”)
Run this agent twice, with the user ID of the OWNER OF MAILBOX AND HAS THE PRIVATE ENCRYPTION KEY.
Now this message is decrypted and all users with permissible access can read the mail.
IS THIS BY DESIGN?
Subject: Encryption and Update Messages - Is This behaviour by DESIGN?
Yazdi,
Just to make sure we’re not glossing over important bits:
-
Encrypting a mail message uses public keys. When you say that the user/owner has the private encryption key, you mean only that it’s the user who can open/decrypt the document, right? You don’t mean that you’re additionally using a SECRET (sometimes called PRIVATE) encryption key.
-
You have no expectation that your new field will be encrypted, right? Your concern is that the BODY field on the email is losing its encryption. You don’t have to open the document to find out, you can do doc properties at the view level and see if the BODY field is available on the second tab. If not, it’s still encrypted.
When I ran my test, I tried it a couple different ways, including using your code. The document always retained the $SEAL and $SEALDATA fields, telling me it remains encrypted.
If you have a scenario that is testable, I’m interested.
regards,
raphael
Subject: Encryption and Update Messages - Is This behaviour by DESIGN?
Yazdi,
Interesting. I cannot recreate this, using your steps and your formula (@IsAvailable instead of @Available). I’m using nd6.5.
regards,
raphael
Subject: RE: Encryption and Update Messages - Is This behaviour by DESIGN?
I may have mistyped the formula, but does the message decrypt ?
Could u also try that with LS Code.
Thanx for the time
Yazdi
Subject: Encryption and Update Messages - Is This behaviour by DESIGN?
Hi Yazdi-
Do you actually have to run the action twice, or does it happen even after running once?
I don’t have alot of experience with encryption, but I can try to help out.
How are you calling the agent, and how is the agent accessing the document? Are you accessing the document with it open, or using Selected Documents from the view?
My assumption is that when you open a document in the GUI, the field becomes unencrypted, and that saving the document afterwards, saves the document with that field in the unencrypted state.
I WOULD suggest to use the NotesDocument Encrypt method prior to the save, but I don’t think this will help either, because Help states:
Since mail encryption works differently, don’t use this method if you want to mail an encrypted document. Instead, set the EncryptOnSend property to True, and use the Send method.
If you are running this with the document open, try running it from an action within a view - On Selected Documents. Perhaps the field won’t be unencrypted as long as the document isn’t opened in the UI.
Sorry I can’t offer any more advice than that.