On 27/10/2019 07.27, lists wrote: > Let me try again. So the email comes in. Some programs gets your public key > and then encrypts the email on the server.
I imagine, in theory it should work like this: New email comes in, and as it moves through the Postfix mail delivery pipeline, at some stage there is a simple filter, which performs an action. There should be some possibility to define simple rules, such as if recipeint = us...@mydomain.com perform action else continue Such process would need to have the users public key, obviously. But that is the least of an issue. I don't understand Postfix enough, to see how this can be implemented in practice. > Then when you retrieve your email, it sends it out in what it believes is > plain text or for that matter can to TLS on the file, but you get a GPG > message that you then decrypt. When I retrieve my message over IMAP, it will be retrieved as any other message, regardless whether it is encrypted or not. Also, TLS is irrelevant here. > So the reason this isn't normally done is a general purpose email server > would have to do this on per client basis, somehow getting the proper public > key for each client. I think the reason why this is not normally done, is that my request is quite exotic. I understand that. I think average mail user does not need this.
