Updated FAQ

FAQ.md

@@ -1033,10 +1033,11 @@ Signed-only messages are supported, and encrypted-only messages are supported si
 
 Common errors:
 
-* *No key*: there is no PGP key available for one of the listed email addresses
+* *No key*: there is no PGP key available for one of the listed email addresses.
 * *No key found!*: the PGP key stored in the identity probably doesn't exist anymore. Resetting the key (see above) will probably fix this problem.
 * *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
 * *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
+* *Message signature valid but not confirmed*: the signature is okay, but the public key still needs to be confirmed in the OpenKeychain app.
 * *OpenPgp error 0: null* / *OpenPgp error 0: General error*: please check the key in the OpenKeychain app and make sure there are no conflicting identities for the key and make sure the email address exactly matches the key, including lower/upper case. Also, make sure the key can be used to sign/encrypt and isn't for encrypting/signing only.
 * *OpenPgp error 0: Encountered an error reading input data!*: your public key has the [AEAD](https://en.wikipedia.org/wiki/Authenticated_encryption) flag set, but the message was encrypted in the older MDC (Modification Detection Code) mode by the sender. For example the Posteo email server does this erroneously. Workaround: [remove the AEAD flag](https://github.com/keybase/keybase-issues/issues/4025#issuecomment-853933127) from the key.
 

index.html

@@ -739,10 +739,11 @@
 <p>Signed-only messages are supported, and encrypted-only messages are supported since version 1.2053.</p>
 <p>Common errors:</p>
 <ul>
-<li><em>No key</em>: there is no PGP key available for one of the listed email addresses</li>
+<li><em>No key</em>: there is no PGP key available for one of the listed email addresses.</li>
 <li><em>No key found!</em>: the PGP key stored in the identity probably doesn’t exist anymore. Resetting the key (see above) will probably fix this problem.</li>
 <li><em>Missing key for encryption</em>: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.</li>
 <li><em>Key for signature verification is missing</em>: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.</li>
+<li><em>Message signature valid but not confirmed</em>: the signature is okay, but the public key still needs to be confirmed in the OpenKeychain app.</li>
 <li><em>OpenPgp error 0: null</em> / <em>OpenPgp error 0: General error</em>: please check the key in the OpenKeychain app and make sure there are no conflicting identities for the key and make sure the email address exactly matches the key, including lower/upper case. Also, make sure the key can be used to sign/encrypt and isn’t for encrypting/signing only.</li>
 <li><em>OpenPgp error 0: Encountered an error reading input data!</em>: your public key has the <a href="https://en.wikipedia.org/wiki/Authenticated_encryption">AEAD</a> flag set, but the message was encrypted in the older MDC (Modification Detection Code) mode by the sender. For example the Posteo email server does this erroneously. Workaround: <a href="https://github.com/keybase/keybase-issues/issues/4025#issuecomment-853933127">remove the AEAD flag</a> from the key.</li>
 </ul>