james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefano Bagnara (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] [Commented] (MIME4J-109) Support for MIME Parameter Value and Encoded Word Extensions
Date Sun, 03 Apr 2011 13:09:05 GMT

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

Stefano Bagnara commented on MIME4J-109:

The best practice is "to not port code between incompatible licenses" :-(

You probably shouldn't have looked at incompatible licensed source code before implementing
it. From my understanding even if you refactor every single line your work will be a derivative
work and so will have to respect their license. You should forget what you saw in javamail
source code and implement from scratch by just reading the RFC.

I'm sorry for this, but we do this to make sure our users receive what they are looking for
(Apache licensed code with no side-effects).

> 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

View raw message