Return-Path: X-Original-To: apmail-james-mime4j-dev-archive@minotaur.apache.org Delivered-To: apmail-james-mime4j-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5E5996EBB for ; Mon, 16 May 2011 09:48:26 +0000 (UTC) Received: (qmail 80919 invoked by uid 500); 16 May 2011 09:48:26 -0000 Delivered-To: apmail-james-mime4j-dev-archive@james.apache.org Received: (qmail 80886 invoked by uid 500); 16 May 2011 09:48:26 -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 80878 invoked by uid 99); 16 May 2011 09:48:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 May 2011 09:48:26 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [81.188.29.42] (HELO bxlexch.b2boost.local) (81.188.29.42) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 May 2011 09:48:21 +0000 Received: from [192.168.100.34] (192.168.100.2) by bxlexch.b2boost.local (192.168.100.253) with Microsoft SMTP Server id 8.2.176.0; Mon, 16 May 2011 11:47:59 +0200 Message-ID: <4DD0F2CF.4050808@apache.org> Date: Mon, 16 May 2011 11:47:59 +0200 From: Eric Charles User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: mime4j-dev@james.apache.org Subject: JSON parsing in mynajs (was Re: Headless mail renderer) References: <4D3D19CB.4010602@secu.lu> <4D3D578E.5050607@secu.lu> <4D3D8825.3050906@secu.lu> <4D3DB3F2.2010308@apache.org> <4D3E6ED9.8010903@secu.lu> <4DC3B2D8.2060801@secu.lu> <4DCB605D.1000300@apache.org> <4DCBDE44.9010102@apache.org> <4DCCA56B.7050005@apache.org> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Hi Tony, Cool! Tks for this :) Event if index.ejs gives some clues on how to run, it would be great to have a short README that explains how to use it (and how to call it from a Java main class). Tks, Eric On 16/05/2011 04:45, Tony Zakula wrote: > Hi Eric and all, > > I have posted some basic code for parsing emails using Mime4J and JavaScript at > > https://bitbucket.org/tzakula/javascript-email-bounce-processor > > Thanks. > > Tony Z > > > > On Thu, May 12, 2011 at 10:28 PM, Eric Charles wrote: >> Hi Tony, >> >> We've got also the apache-extras [1] which is mercurial (hosted by google >> for addons to apache projects). >> >> I was wondering if the parser can be used without the full myna server. I >> mean, we simply need to parse mail, not to configure a full server with >> users,... ([2]). >> >> Also, is the parser component packaged as a maven module to be easily used >> as dependency somewhere else? >> >> Whatever the response to the 2 above questions, feel free to push it where >> you like. I will look at it :) >> >> Tks, >> - Eric >> >> [1] http://code.google.com/a/apache-extras.org/hosting/ >> [2] http://www.mynajs.org/site/article/MynaPermissionsAdministrator.ejs >> >> >> On 13/05/2011 01:51, Tony Zakula wrote: >>> >>> Hi Eric, >>> >>> JavaScript is also extremely flexible. With Rhino, you get the full >>> power of Java plus a lot of flexibility. >>> >>> What is the preferred spot of release? Github, Bitbuckit, or is there >>> another? >>> >>> Tony >>> >>> >>> On Thu, May 12, 2011 at 8:19 AM, Eric Charles wrote: >>>> >>>> Hi Tony, >>>> >>>> Javascript in james server would be a primeur. >>>> But why not... there is more and more JS "on the other side" (thinking to >>>> Node.js...). I'm using today Jackson to manipulate JSON in Java, but >>>> Javascript has a more natural fit, so I understand why you choose it. >>>> >>>> We will start around end-May with MAILBOX-44, but there today no >>>> discussions/decisions on the chosen format to persist mail. >>>> >>>> I would say "don't hurry, don't put pressure on you, and keep us updated >>>> when you think to release it" :) >>>> >>>> Tks, >>>> - Eric >>>> >>>> On 12/05/2011 14:35, Tony Zakula wrote: >>>>> >>>>> Hi Eric, >>>>> >>>>> I would be more than happy to release the code now even though it is >>>>> not entirely finished if you are interested. The parsing part is >>>>> pretty good, and I am using it in a production project right now. I >>>>> am not sure it will fit your bill though as I am using it on a mail >>>>> server to do message list bounce processing. Although I write Java >>>>> code for a living, I wanted to make it easy to modify this utility on >>>>> a running server so I used an open source project I contribute to at >>>>> Mynajs.org which is built on top of the Mozilla Rhino project. I use >>>>> Mime4J, but my code is written in JavaScript. >>>>> >>>>> I would be more than happy to release the code now if you are >>>>> interested. >>>>> >>>>> Please let me know. >>>>> >>>>> Thanks! >>>>> >>>>> Tony >>>>> >>>>> On Wed, May 11, 2011 at 11:21 PM, Eric Charles >>>>> wrote: >>>>>> >>>>>> Hi Tony, >>>>>> >>>>>> We are starting to work on MAILBOX-44 "Design and implement a >>>>>> distributed >>>>>> mailbox using Hadoop" [1] >>>>>> >>>>>> We will need to store the mail in hadoop and the JSON format (in avro >>>>>> file) >>>>>> may be a option. >>>>>> >>>>>> You said you are "still polishing for release" your JSON transformer. >>>>>> Have you got any plan to release it in opensource so we could use it ? >>>>>> >>>>>> Tks, >>>>>> Eric >>>>>> >>>>>> [1] https://issues.apache.org/jira/browse/MAILBOX-44 >>>>>> >>>>>> >>>>>> On 10/05/2011 10:00, Robert Burrell Donkin wrote: >>>>>>> >>>>>>> On Sun, May 8, 2011 at 2:44 PM, Tony Zakula >>>>>>> wrote: >>>>>>>> >>>>>>>> Not sure on where the project leaders want to go, >>>>>>> >>>>>>> Projects are community led here at Apache (see eg [1][2][3][4]). If >>>>>>> there's development interest from the community and it's in scope for >>>>>>> the project, then that's a direction the code will move in. >>>>>>> >>>>>>>> but I think being >>>>>>>> able to store messages in different formats to be able to plugin to >>>>>>>> systems would be great. Instead of each person writing their own >>>>>>>> parser, most people would just plugin the larger piece to their >>>>>>>> system >>>>>>>> and start there. >>>>>>> >>>>>>> +1 >>>>>>> >>>>>>> This vision seems to fit with the work over at Tika [5] and Lucene >>>>>>> [6]. >>>>>>> >>>>>>>> I did not see where you specified what you are thinking about for >>>>>>>> summer. Is that a link somewhere yet? >>>>>>> >>>>>>> The mailing lists (see [7] and eg [8]) are the primary tools we use >>>>>>> here at Apache. Stuff only tends to get written down later, if at all. >>>>>>> We've been throwing ideas around on the lists, hoping that people >>>>>>> might pick some of them up and run with them ;-) >>>>>>> >>>>>>> Robert >>>>>>> >>>>>>> [1] http://www.apache.org/foundation/how-it-works.html >>>>>>> [2] http://www.apache.org/foundation/getinvolved.html >>>>>>> [3] http://jakarta.apache.org/site/contributing.html >>>>>>> [4] http://www.apache.org/dev/contributors.html >>>>>>> [5] http://tika.apache.org/ >>>>>>> [6] http://lucene.apache.org/ >>>>>>> [7] http://www.apache.org/dev/#mail >>>>>>> [8] http://www.apache.org/dev/contrib-email-tips.html >>>>>> >>>>>> >>>> >>>> >> >>