Return-Path: Delivered-To: apmail-james-mime4j-dev-archive@minotaur.apache.org Received: (qmail 83264 invoked from network); 7 Feb 2009 07:55:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Feb 2009 07:55:22 -0000 Received: (qmail 90685 invoked by uid 500); 7 Feb 2009 07:55:22 -0000 Delivered-To: apmail-james-mime4j-dev-archive@james.apache.org Received: (qmail 90667 invoked by uid 500); 7 Feb 2009 07:55:22 -0000 Mailing-List: contact mime4j-dev-help@james.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mime4j-dev@james.apache.org Delivered-To: mailing list mime4j-dev@james.apache.org Received: (qmail 90656 invoked by uid 99); 7 Feb 2009 07:55:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Feb 2009 23:55:22 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 07 Feb 2009 07:55:20 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 854A9234C4A9 for ; Fri, 6 Feb 2009 23:54:59 -0800 (PST) Message-ID: <1937609427.1233993299531.JavaMail.jira@brutus> Date: Fri, 6 Feb 2009 23:54:59 -0800 (PST) From: "Robert Burrell Donkin (JIRA)" To: mime4j-dev@james.apache.org Subject: [jira] Commented: (MIME4J-113) [SMIME and OpenPGP/MIME] Support For Canonicalication And Normalisation In-Reply-To: <215178576.1233993179714.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/MIME4J-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671421#action_12671421 ] Robert Burrell Donkin commented on MIME4J-113: ---------------------------------------------- http://mail-archives.apache.org/mod_mbox/james-mime4j-dev/200902.mbox/%3ca92573960902061448g647ca695s89dec26f464f0fe4@mail.gmail.com%3e >> I think you've made a good point with #112. I also believe that >> perfect reproduction of a message would be a necessity if a Mime4j DOM >> should ever be used for verifying an S/MIME signature.. > > it's not as simple as that: SMIME (and OpenPGP/MIME) require > canonicalisation and normalisation I know.. we've already had this discussion to some extent. One the one hand we have RFC2633 that is a bit vague when it comes to the concrete canonicalization steps: "The exact details of canonicalization depend on the actual MIME type and subtype of an entity, and are not described here." But at least it describes basic CRLF canonicalization. On the other hand we have some real world MUAs that support S/MIME.. I know for sure that Outlook does not even perform basic CRLF canonicalization. Neither Outlook nor Thunderbird decode transfer encodings before verifying (nor should they if I understand correctly). So in order to support explicit S/MIME signatures Mime4j must not automatically decode transfer encodings the way it does now. This process is never reversible, especially for quoted-printable. CRLF canonicalization does not worry me because it can always be applied with a simple filter stream.. > [SMIME and OpenPGP/MIME] Support For Canonicalication And Normalisation > ----------------------------------------------------------------------- > > Key: MIME4J-113 > URL: https://issues.apache.org/jira/browse/MIME4J-113 > Project: JAMES Mime4j > Issue Type: Wish > Affects Versions: 0.7 > Reporter: Robert Burrell Donkin > > Add canonicalisation and normalisation support suitable for use with SMIME and OpenPGP/MIME -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.