-
-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Encrypted messages with attachments don't have protected-headers="v1" in the header #2302
Labels
Comments
The source of the problem is here: |
Marking it as a good first issue because it is clear what the result should be, but I am not sure it is actually easy to implement. |
iequidoo
added a commit
that referenced
this issue
Oct 2, 2023
…ned MIME (#2302) Add protected-headers="v1" directive to Content-Type of an encrypted/signed MIME so that other MUAs like Thunderbird display the true message Subject instead of "...".
iequidoo
added a commit
that referenced
this issue
Oct 3, 2023
…ned MIME (#2302) Add protected-headers="v1" directive to Content-Type of an encrypted/signed MIME so that other MUAs like Thunderbird display the true message Subject instead of "...".
link2xt
pushed a commit
that referenced
this issue
Oct 4, 2023
…ned MIME (#2302) Add protected-headers="v1" directive to Content-Type of an encrypted/signed MIME so that other MUAs like Thunderbird display the true message Subject instead of "...".
link2xt
pushed a commit
that referenced
this issue
Oct 4, 2023
…ned MIME (#2302) Add protected-headers="v1" directive to Content-Type of an encrypted/signed MIME so that other MUAs like Thunderbird display the true message Subject instead of "...".
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This line does not work for
multipart/mixed
parts:deltachat-core-rust/src/mimefactory.rs
Line 591 in 36aef64
The result is still
Content-Type: multipart/mixed; boundary="some-random-string"
, so Thunderbird does not look for protected headers and displays message Subject as...
.The text was updated successfully, but these errors were encountered: