starred/native
1
0
Fork 0
mirror of https://github.com/bulwarkmail/native.git synced 2026-11-01 00:07:01 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: note that stalwart 1.0.1 keeps drafts and sent mail unencrypted at rest

Browse Source
This commit is contained in:
Linus Rath
2026-10-31 03:53:25 +01:00
parent 1bef47199c
commit 853cb5d052
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/api/account-security.ts
+5 -2
View File
@@ -250,8 +250,11 @@ export async function fetchCryptoInfo(): Promise<CryptoInfo> {
* Configure Stalwart's encryption at rest (`x:AccountSettings/set` * Configure Stalwart's encryption at rest (`x:AccountSettings/set`
* `encryptionAtRest`). `Aes128`/`Aes256` need a public key id from * `encryptionAtRest`). `Aes128`/`Aes256` need a public key id from
* {@link fetchPublicKeys}; `encryptOnAppend` also encrypts mail the user * {@link fetchPublicKeys}; `encryptOnAppend` also encrypts mail the user
* files (sent/imported), `allowSpamTraining` lets the classifier read a * files (imported or appended over IMAP), `allowSpamTraining` lets the
* message before it is encrypted. * classifier read a message before it is encrypted. Since Stalwart 1.0.1
* JMAP drafts (`$draft`) and the Sent copy of a JMAP submission are stored
* unencrypted, so they stay editable and go out readable; 0.16 and 1.0.0
* encrypted those too.
*/ */
export async function updateEncryptionAtRest(input: { export async function updateEncryptionAtRest(input: {
type: EncryptionType; type: EncryptionType;