Derek Martin wrote: > On Tue, Jan 13, 2015 at 08:52:41AM -0800, Kevin J. McCarthy wrote: > > Just to make sure the feature is clear, this patch only encrypts the > > postponed message to $postpone_encrypt_as. Even if the message were > > somehow obtained, signed or unsigned, it would still only be readable by > > you. > > I was going to suggest this anyway, but I think this drives home the > point: postpone_encrypt_as should really be called > postpone_encrypt_to--it specifies the encryption key TO which you > will encrypt the data. Clearly this need not be your own key, though > very little else would normally make sense.
If others agree, I'll be glad to change it. I'm not convinced the name was the reason for Ben's confusion. The "as" was used to indicate ownership of the key being used. However, I did consider using "to", as that is more standard usage for encryption. So, if someone else has a strong opinion on this, please speak up. Thanks, -Kevin
signature.asc
Description: PGP signature
