https://bugs.kde.org/show_bug.cgi?id=439904
Sandro Knauß <skna...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|REPORTED |CONFIRMED
CC| |skna...@kde.org
--- Comment #3 from Sandro Knauß <skna...@kde.org> ---
Your information are not enough to understand what mime structure ProtonMail is
using. Can you provide one encrypted mail uploading it as attachment to this
bug? The content of the encrypted part, i can replace with something that can
be used in tests, but I need a sample of a real mail.
But for sure it seems, like they do not follow the RF 3156 Section 4 (
https://datatracker.ietf.org/doc/html/rfc3156#section-4):
"
OpenPGP encrypted data is denoted by the "multipart/encrypted"
content type, described in [2], and MUST have a "protocol" parameter
value of "application/pgp-encrypted". Note that the value of the
parameter MUST be enclosed in quotes.
The multipart/encrypted MIME body MUST consist of exactly two body
parts, the first with content type "application/pgp-encrypted". This
body contains the control information. A message complying with this
standard MUST contain a "Version: 1" field in this body. Since the
OpenPGP packet format contains all other information necessary for
decrypting, no other information is required here."
It would makes our life much more easier when ProtonMail would follow the RFC.
As all other e-mail clients need a special treatment for those mails too.
Thanks for the patch. Often patches are missed, when provided as part of a
bugreport. Please create MR on https://invent.kde.org/pim/messagelib, than we
can make sure that this is fixed soon.
Btw normally encrypted mails should be handled by
MultiPartEncryptedBodyPartFormatter. The
ApplicationPGPEncryptedBodyPartFormatter was added to parse non conform
Applemail encrypted mails ;)
See https://bugs.kde.org/show_bug.cgi?id=360910
--
You are receiving this mail because:
You are the assignee for the bug.
