[Remail] RFC: "transport" encryption type

[Thomas Gleixner]

Konstantin,

On Thu, Oct 29 2020 at 09:11, Konstantin Ryabitsev wrote:
> Remail currently provides 2 encryption options: s/mime and pgp. How 
> about adding a third option called "transport" that would basically 
> delegate the task of encryption to the transport layer (effectively, 
> sending cleartext mail to those subscribers). There are cases in which 
> this would make sense, for example:
>
> - the email is delivered to an inbox on the same infrastructure managed 
>   by the same people who have access to the remail encryption keys

This makes definitely sense.

> - the email is delivered to an inbox over an encrypted SMTP+TLS session 
>   and the provider has the user's private keys anyway (e.g. s/mime 
>   option set up via GSuite, where email is decrypted on the Google side 
>   of things)

Yeah, there is not really a point to keep it encrypted. It's already
safe because Gurgle is managing your key :)

> What do you think?

Both use cases make sense and it should be straight forward to
implement.

Thanks,

        tglx