User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0

Steps to reproduce:

On a fresh install (77b2) I activated an email account and clicked in to an email, which happened to be PGP encrypted.

Actual results:

If you happen to click an encrypted email in a fresh install before configuring a private key, you get this confusing error message:

"This is an encrypted OpenPGP message, but support for OpenPGP decryption is not available."

Expected results:

This error message makes it seem like OpenPGP is not a possible thing, instead of simply that it lacks any private keys / configuration at this stage. Depending on where else this string is used, it could read something like:

"This is an encrypted OpenPGP message, but OpenPGP decryption is not set up. [Configure OpenPGP keys here] to set up OpenPGP"

Or

"This is an encrypted OpenPGP message, but you do not have a matching OpenPGP decryption key or have not configured OpenPGP. [Configure OpenPGP keys here] "

(or similar, to indicate that OpenPGP (or S/MIME, if it has the same flow) is "available" for use, but needs configuration.)

Related: bug 1627762 (openPGP onboarding) and bug 1627736 (PKCD) suggest a new UX approach for new (to TB) accounts and keys, which (hopefully) would eliminate this string from appearing altogethe

That should really never happen I think - it's what we used to show when you got a PGP message but Enigmail was not installed.
https://searchfox.org/comm-central/search?q=PGPMIME_STR_NOT_SUPPORTED_ID&case=true&path=

For citing bugs, just type bug and the number after to autolink. As bug 1627762 and bug 1627736.

(In reply to Jon from comment #0)

If you happen to click an encrypted email in a fresh install before configuring a private key, you get this confusing error message:
"This is an encrypted OpenPGP message, but support for OpenPGP decryption is not available."

I can no longer reproduce this bug with 77b3. It's probably a duplicate of bug 1637690.

Can you confirm? You should get the "decrypt failure" status icon.

A better error message for this scenario has been suggested in bug 1634496.

Confirming I cannot reproduce this now.

thanks for confirming!