Skip to content

Conversation

@iequidoo
Copy link
Collaborator

@iequidoo iequidoo commented Nov 1, 2025

This implements the most important parts of https://www.rfc-editor.org/rfc/rfc9788.html. Need to recheck if anything else needs implementation.

Close #7130

@iequidoo iequidoo force-pushed the iequidoo/use-em-dash-after-subject branch from 51b2395 to 9bc2aee Compare November 1, 2025 17:00
Base automatically changed from iequidoo/use-em-dash-after-subject to main November 1, 2025 17:06
@iequidoo iequidoo force-pushed the iequidoo/header-protection branch from 4264ed2 to 23c0d0a Compare November 1, 2025 17:11
@iequidoo iequidoo marked this pull request as draft November 1, 2025 17:24
@iequidoo iequidoo force-pushed the iequidoo/header-protection branch 2 times, most recently from c5ff81e to ff46db6 Compare November 1, 2025 17:59
@iequidoo iequidoo marked this pull request as ready for review November 1, 2025 19:57
@iequidoo iequidoo force-pushed the iequidoo/header-protection branch 3 times, most recently from a187251 to 12621ac Compare November 3, 2025 23:07
…7130)

This is a part of implementation of https://www.rfc-editor.org/rfc/rfc9788 "Header Protection for
Cryptographically Protected Email".
Implement 4.5.3.2 of https://www.rfc-editor.org/rfc/rfc9788 "Header Protection for Cryptographically
Protected Email".
…defined in RFC 9788) (#7130)

But disable it by default for now. We will enable it when most users update to versions capable to
receive protected headers.
Implement 4.5.3.3 of https://www.rfc-editor.org/rfc/rfc9788 "Header Protection for Cryptographically
Protected Email".
@iequidoo iequidoo force-pushed the iequidoo/header-protection branch from 12621ac to be769cd Compare November 3, 2025 23:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Implement standard Header Protection

2 participants