GODT-1986: Handle case where an address has no decryption entities

It's possible (but very rare, I don't think proton still allows it)
for an address to have no keys. If we try to load the address keyring
for such an address, this change logs a warning that no decryption
entities were found in the unlocked keyring.

It bumps liteapi to a version that does not return an error when no
keys could be unlocked.
This commit is contained in:
James Houlahan
2022-10-27 05:12:13 +02:00
parent 7f6094750e
commit d066e32719
9 changed files with 97 additions and 8 deletions

View File

@ -58,4 +58,22 @@ Feature: Bridge can fully sync an account
| Folders/one | 2 | 1 |
| Folders/two | 2 | 1 |
| Labels | 0 | 0 |
| Labels/three | 0 | 0 |
| Labels/three | 0 | 0 |
Scenario: If an address has no keys, the account is still synced
Given the account "user@pm.me" has additional address "alias@pm.me"
And the account "user@pm.me" has the following custom mailboxes:
| name | type |
| encrypted | folder |
And the address "alias@pm.me" of account "user@pm.me" has the following messages in "encrypted":
| from | to | subject |
| a@pm.me | a@pm.me | no key |
| b@pm.me | b@pm.me | no key |
And the address "alias@pm.me" of account "user@pm.me" has no keys
When the user logs in with username "user@pm.me" and password "password"
And user "user@pm.me" finishes syncing
When user "user@pm.me" connects and authenticates IMAP client "1"
Then IMAP client "1" eventually sees the following messages in "Folders/encrypted":
| from | to | subject | mime-type |
| a@pm.me | a@pm.me | no key | multipart/encrypted |
| b@pm.me | b@pm.me | no key | multipart/encrypted |