could not verify signature - retry button/link

[tomholub]

[tomholub]

My response:

It appears that this could be an error when reaching [customer] WKD (eg a network error), especially if it works the second time and thereafter for the same sender. In these situations, we should offer a retry button. That would make for a better UX.

Therefore, to fix this, I propose that the text will become:

could not verify signature: missing pubkey ${pubkey}. <a href="#">Retry Pubkey Lookup</a>

Where the link will be visible and clickable, and will cause the signature verification to be re-run (including re-fetching) and the signature badge re-rendered.

[tomholub]

Actually, I may have a simpler and better fix to do first, not involving UI.

We have a pretty aggressive timeout for WKD lookups - probably 4 seconds. This may be the root cause of the flakiness. 4 seconds timeout is because for most users most of the time, we don't expect WKD to be there (most consumer users or other recipients don't have it).

But for customers that run Email Key Manager, we know they have very likely WKD running too. So we could increase WKD request timeout in these situations to 10 seconds.

In the following situations, there will be a timeout of 10 seconds on WKD lookups:

• if my own account is using email key manager, AND
• I'm looking up a WKD email on the same domain as my own account

In remaining situations let's leave the timeout at 4 seconds as before.

[tomholub]

Un-assigning - can do #4320 first which should address the root cause. Thanks!

[rrrooommmaaa]

It happens right after manual import of a public key attached to the message