[jira] Commented: (MIME4J-148) Track downstream use-case for mime4j library

["Stefano Bagnara (JIRA)" <mi...@james.apache.org>]

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

Stefano Bagnara commented on MIME4J-148:
----------------------------------------

k9mail (http://code.google.com/p/k9mail/), an email client from Android, uses mime4j:
they use the Address parsing methods for:
http://www.google.com/codesearch/p?hl=it#JErEysU_JFY/k9mail/trunk/src/com/fsck/k9/mail/Address.java&q=mime4j%20package:http://k9mail%5C.googlecode%5C.com/svn&d=1
Their MImeUtility uses some utility from the old "decoder" package:
http://www.google.com/codesearch/p?hl=it#JErEysU_JFY/k9mail/trunk/src/com/fsck/k9/mail/internet/MimeUtility.java&q=mime4j%20package:http://k9mail%5C.googlecode%5C.com/svn&d=1
Their MimeMessage uses the MimeStreamParser with a custom contenthandler to build their own MImeMessage:
http://www.google.com/codesearch/p?hl=it#JErEysU_JFY/k9mail/trunk/src/com/fsck/k9/mail/internet/MimeMessage.java&q=mime4j%20package:http://k9mail%5C.googlecode%5C.com/svn&d=1
Their MImeHeader uses our EncoderUtil.encodeEncodedWord

They use their own DOM, even if they seem to have a very similar DOM (maybe it worth contacting them to know why and what could mime4j do to improve this).

> Track downstream use-case for mime4j library
> --------------------------------------------
>
>                 Key: MIME4J-148
>                 URL: https://issues.apache.org/jira/browse/MIME4J-148
>             Project: JAMES Mime4j
>          Issue Type: Task
>    Affects Versions: 0.7
>            Reporter: Stefano Bagnara
>            Assignee: Stefano Bagnara
>            Priority: Minor
>             Fix For: 0.8
>
>
> This issue is here to track the downstream use cases.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.