Mailing-List: contact mime4j-dev-help@james.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mime4j-dev@james.apache.org
Date: Sat, 2 Apr 2011 09:26:12 +0000 (UTC)
From: "Oleg Kalnichevski (JIRA)" <mime4j-dev@james.apache.org>
To: mime4j-dev@james.apache.org
Message-ID: 
 <904962119.30358.1301736372882.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MIME4J-109) Support for MIME Parameter Value
 and Encoded Word Extensions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MIME4J-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014975#comment-13014975 ] 

Oleg Kalnichevski commented on MIME4J-109:
------------------------------------------

Folks

JavaMail source appears to be licensed under multiple licenses: CDDL-1.0, BSD, GPL-2.0, GNU-Classpath

http://kenai.com/projects/javamail

This list includes BSD which as far as I understand should be ASLv2 compatible. Nonetheless, I am not sure, though, we could (or should) copy bits of code from JavaMail.

What do you think?

Oleg


> Support for MIME Parameter Value and Encoded Word Extensions
> ------------------------------------------------------------
>
>                 Key: MIME4J-109
>                 URL: https://issues.apache.org/jira/browse/MIME4J-109
>             Project: JAMES Mime4j
>          Issue Type: New Feature
>    Affects Versions: 0.5
>            Reporter: Markus Wiederkehr
>            Assignee: Markus Wiederkehr
>             Fix For: 0.8
>
>         Attachments: rfc2231.patch
>
>
> See RFC 2231.
> Mime4j should be capable of correctly decoding and encoding these extensions.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira