Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

I was sent an inline PGP message

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

In the past, enigmail recognised and decrypted these with no problem.

   * What was the outcome of this action?

Now, thunderbird does not recognise that the message is encrypted, and pressing
the OpenPGP button, thunderbird claims that it is not encrypted.

   * What outcome did you expect instead?

I expected Thunderbird to recognise and decrypt the message, just as enigmail
had done in the past.

*** End of the template - remove these template lines ***

Hello Jeffrey,

Am 30.11.20 um 18:58 schrieb Jeffrey Ratcliffe:

is there a particular reason why you want to use inline PGP? This is an
old technique that shouldn't get used any longer, it's a dead horse.
PGP/MIME is the thing users should use instead. Thunderbird uses
PGP/MIME by default and I currently see no way to enforce inline PGP for
sending encrypted emails with Thunderbird?

You are aware that inline PGP is incompatible while using with HTML emails?

Hi Carsten,

Other people send me inline PGP. I would like to be able to read what
they have written.

I am happy sending with PGP/MIME.

Regards

Jeff

Hello Jeff,

Am 01.12.20 um 20:09 schrieb Jeff:
...

yes, of course. But remember my sentence above your answer. If the
sender is using inline PGP with an HTML message the behavior is
undefined, in the end Thunderbird can't decrypt the message and there is
nothing we can do about this.

You need to have a look at the source of the email, Ctrl + U will show
you the message at source level.

Look for 'Content-Type', if you find a line

  Content-Type: text/plain; charset=......

than the message is text only. If you see

  Content-Type: multipart/mixed; (or similar)

than you look at a HTML message.

In my eyes best is to convince the sender to not use inline PGP in the
long run.

If the sender is using MS Exchange you have likely no chance to get a
RFC correct message here.

The following bug from Bugzilla is marked as fixed in 78.5.0, but I
still can't open the attached encrypted example messages.

https://bugzilla.mozilla.org/show_bug.cgi?id=1672851

Without further information what the message is build of you have
problems with we can't do any useful error detection.
I expect you will have the same problems if you use an upstream version
of Thunderbird from Mozilla. If yes your bug report should go into
Bugzilla so MZLNA have a chance to fix the underlying issue (if possible).
Fine, then your setup is correct and futurproof.

Hi Carsten,

No. They are all plain text.

Enigmail had no problem with these messages, and if Thunderbird cannot
recognise them, then I cannot read them any more (including all the
historical ones sitting my my mailbox.)

Regards

Jeff

Hello Jeff,

Am 02.12.20 um 18:11 schrieb Jeff:

then I even more don't understand why people still using inline PGP...
Self-made problems.

Yes, as said, I can't do anything if we can't readjust that behaviour. I
expect that the outcome is the same if you are using a prebuild version
from upstream. I'm also quite sure this all isn't a Debian specific
issue. Means, the report need to get addressed upstream.

So, please check if the same issue is happen if you are using from MZLNA.

If the issue is also happen here please raise a report in the Bugzilla
issue tracker from Mozilla.

Afterwards we can connect this Debian report with the upstream report
and will get informed once the status in Bugzilla is changing.

Somebody beat me to it:

https://bugzilla.mozilla.org/show_bug.cgi?id=1679018

And it looks as though it is fixed in TB79.