diff --git a/src/mimefactory.rs b/src/mimefactory.rs
index 6793ea53c..5619c3b76 100644
--- a/src/mimefactory.rs
+++ b/src/mimefactory.rs
@@ -2157,10 +2157,6 @@ fn group_headers_by_confidentiality(
                 }
             }
         } else {
-            // Copy the header to the protected headers
-            // in case of signed-only message.
-            // If the message is not signed, this value will not be used.
-            protected_headers.push(header.clone());
             unprotected_headers.push(header.clone())
         }
     }
diff --git a/src/mimeparser.rs b/src/mimeparser.rs
index 787c59147..d906a058d 100644
--- a/src/mimeparser.rs
+++ b/src/mimeparser.rs
@@ -2188,9 +2188,6 @@ pub(crate) fn parse_message_id(ids: &str) -> Result<String> {
 /// Returns whether the outer header value must be ignored if the message contains a signed (and
 /// optionally encrypted) part. This is independent from the modern Header Protection defined in
 /// <https://www.rfc-editor.org/rfc/rfc9788.html>.
-///
-/// NB: There are known cases when Subject and List-ID only appear in the outer headers of
-/// signed-only messages. Such messages are shown as unencrypted anyway.
 fn is_protected(key: &str) -> bool {
     key.starts_with("chat-")
         || matches!(