Support early MIME types for S/MIME encrypted messages #9973
+2
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dschmidt
pushed a commit
to dschmidt/roundcubemail
that referenced
this pull request
Nov 12, 2025
Co-authored-by: Mathias Schneider <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I like to propose a small enhancement to make Roundcube recognize S/MIME encrypted messages by the early Content-Type
application/x-pkcs7-mime(RFC 2311, Appendix C.1).By this change those messages get the lock symbol in the message list and the banner text
encryptedmessageis displayed when the message is selected.There might be some clients around still using it, for example if they use openssl for encryption like the example below: