Forward Email (new features)

dngray: > What is to say their source code on github actually matches what is on the server? This is the ultimate email question, Signal has verifiable binaries, and as both sender and receiver use libsignal, we can indeed satisfy mathematically that its indeed e2ee. Now forwardemail has a frontend client, you can verify the hashes against the running code, and encryption can happen on the client side with providers that support keys via API, WKD and other forwardemail users. On the inbound side you are trusting every email service there is no RFC that has made email e2ee yet. dngray: > As a result for a service like email transparency about who is running it, honesty about the service and it’s limitations are crucial. Why not pull Proton from the recommended email services? https://x.com/DoingFedTime/status/2030108076531995016