GpgOL - Unsigned S/MIME mails are not integrity protected

I’m not sure I understand what you mean by the Year. In 2019 this will still be the case and was the case in 2017. I prefer the “In this Version of S/MIME” as it is related to the Version of Gpg4win and we will know when we implement authenticated encryption for S/MIME

Also “Old” Mails is sadly not true. There are people and Software out there that send unsigned S/MIME Mails “Now” because signing can be unwanted or a hassle or they don’t know better.

I like the other parts. So here is my new draft:

You are replying to an unsigned S/MIME email.

In this version of S/MIME an attacker could use the missing signature to have you
decrypt contents from a different, otherwise completely unrelated email
and place it in the quote so they can get hold of it.
This is why we only allow quoting to be done manually in this case.

Please copy the relevant contents and insert them manually into the new email.

^ The last sentence was suggested by a customer to have a clear and not too scary action advice. So I put your suggestion with the “this is why” in the explanatory paragraph.
So the structure of the three paragraphs is now:

  1. What this message relates to.
  2. What is going on?
  3. What should I do now.

So if someone does not want to read the long middle part he can just see the last sentence with “What to do now”.

German:

Sie antworten einer unsignierten S/MIME Mail.

In dieser Version von S/MIME kann ein Angreifer das fehlen der Signatur dazu verwenden Inhalte einer vollkommen anderen Mail zu entschlüsseln. Diese würden dann in der Antwort zitiert und möglicherweise dem Angreifer zugänglich.
Aus diesem Grund erlauben wir in diesem Fall nur manuelles zitieren.

Bitte kopieren Sie die relevanten Inhalte und fügen Sie diese manuell in die neue Mail ein.