You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior and actual behavior:
When typing a mail that aims to be encrypted using PGP, PLEASE DO NOT SAVE THE DRAFT IN CLEAR. This is an obvious flaw: I am writing encrypted e-mails so only me and my recipient know the content. But if the server saves the draft in clear, well ... we can be more than 2 to know this content: the e-mail provider will be a third.
Steps to reproduce the problem:
Type a mail. The draft will be saved on the server (I'm using IMAP), in clear text.
Logs or screenshots:
The text was updated successfully, but these errors were encountered:
RainLoop has no way of knowing that you're willing to encrypt the message. as a workaround, does disabling the drafts folder help?
in the long run, perhaps redesigning the pgp UI would be a good choice - some obvious toggle buttons to sign and encrypt (that's one thing that milepile does right, imho), where encrypt button would disable storing the draft on the server, and both would take action after clickling send, not immediately.
RainLoop version, browser, OS:
1.10.5.192, Chromium, Ubuntu 16.04
Expected behavior and actual behavior:
When typing a mail that aims to be encrypted using PGP, PLEASE DO NOT SAVE THE DRAFT IN CLEAR. This is an obvious flaw: I am writing encrypted e-mails so only me and my recipient know the content. But if the server saves the draft in clear, well ... we can be more than 2 to know this content: the e-mail provider will be a third.
Steps to reproduce the problem:
Type a mail. The draft will be saved on the server (I'm using IMAP), in clear text.
Logs or screenshots:
The text was updated successfully, but these errors were encountered: