Bugzilla

Good questions. I think perhaps it's better to safe the "move and decrypt" to the filter action (since the move part = delete, is just a button away after copy succeeded). 

I would model it according to the similar items we have:
Copy As Decrypted To > [folderlist flyout]

For multi-selection, seems we should still copy even if some are not encrypted. It would seem the goal is to have an email that can be read by anyone - so that goal is the fulfilled. Say, you have a full folder of messages (some encrypted) that you need to hand over to someone else...

For single selection, please just hide the menu if not encrypted.

In case we cannot decrypt, we should just tell the user that at the end of the operation: "4 of the messages could not be decrypted." - in case that happens. But if there are no problems, we should not prompt.

For insecure encryption and such, I would just do the decryption by any means possible. The resulting message is still insecure in all situation and there are no guarantees about it anymore. Give the user something readable, that's what they asked for.

Good questions. I think perhaps it's better to save the "move and decrypt" to the filter action (since the move part = delete, is just a button away after copy succeeded). 

I would model it according to the similar items we have:
Copy As Decrypted To > [folderlist flyout]

For multi-selection, seems we should still copy even if some are not encrypted. It would seem the goal is to have an email that can be read by anyone - so that goal is the fulfilled. Say, you have a full folder of messages (some encrypted) that you need to hand over to someone else...

For single selection, please just hide the menu if not encrypted.

In case we cannot decrypt, we should just tell the user that at the end of the operation: "4 of the messages could not be decrypted." - in case that happens. But if there are no problems, we should not prompt.

For insecure encryption and such, I would just do the decryption by any means possible. The resulting message is still insecure in all situation and there are no guarantees about it anymore. Give the user something readable, that's what they asked for.