james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Bagnara <apa...@bago.org>
Subject Re: [VOTE] Release Apache James Server and App 3.0-beta4
Date Wed, 07 Mar 2012 14:17:13 GMT
2012/3/7 Eric Charles <eric@apache.org>:
>> I still have to better review
>> https://repository.apache.org/content/repositories/orgapachejames-043/
>> because I see there are a lot of new jars and I think LICENSE/NOTICE
>> is not ok. Maybe a full dependency review is needed (b3 had 33MB libs,
>> b4 have 52MB libs).
>
> The difference should mainly come from hbase/hadoop which are ASL2 and
> should give no problem.
> Maybe some other jars are also present, but they don't jump to my head atm.

I noticed some api jar (servlet-api), core-3.1.1.jar (eclipse
license?), serp-1.13.1.jar (BSD?) jetty (ASL, but have NOTICE stuff we
have to "republish")... and maybe more...

> Will you do the review (just to coordinate ourselves) ?

Not soon.

Each jar have to be checked and either excluded or correctly
referenced in NOTICE/LICENSE. The main problem is that I don't have a
good knowledge of what have to be listed and what not. E.g: jetty has
this notice: http://svn.codehaus.org/jetty/jetty/branches/jetty-6.1/NOTICE.txt
. How should be deal with it in our binary distribution? (should we
include that NOTICE in our main notice?).

IIRC Robert created a tool to help with the creation/maintenance of
the LICENSE file (licensed under .... from ....: list of jars) that
used for b3 release.

Stefano

>> Stefano
>>
>> 2012/3/7 Eric Charles<eric@apache.org>:
>>>
>>> Maybe something to do with utf-8 encoding?
>>> Can you try with to type 'chcp 65001' (define UTF-8 encoding) in the dos
>>> box, and then retry ?
>>>
>>> Thx,
>>> Eric
>>>
>>>
>>>
>>> On 07/03/12 12:39, Stefano Bagnara wrote:
>>>>
>>>>
>>>> Moving smtpserver to DEBUG I found this (while writing EHLO test.com).
>>>> It happens at every "first line" in my windows box.
>>>> ---
>>>> INFO  12:36:28,355 | james.smtpserver | Id='866732' User='' Connection
>>>> established from 127.0.0.1
>>>> DEBUG 12:36:32,304 | james.smtpserver | Id='866732' User=''
>>>> org.apache.james.protocols.api.handler.CommandDispatcher received:
>>>> ??▼??
>>>>
>>>> DEBUG 12:36:32,305 | james.smtpserver | Id='866732' User='' Lookup
>>>> command handler for command: ??▼??
>>>> DEBUG 12:36:32,306 | james.smtpserver | Id='866732' User='' Unable to
>>>> parse request
>>>> java.lang.NullPointerException
>>>>         at
>>>>
>>>> org.apache.james.protocols.api.handler.CommandDispatcher.dispatchCommandHandlers(CommandDispatcher.java:170)
>>>>         at
>>>>
>>>> org.apache.james.protocols.api.handler.CommandDispatcher.onLine(CommandDispatcher.java:147)
>>>>         at
>>>>
>>>> org.apache.james.protocols.netty.BasicChannelUpstreamHandler.messageReceived(BasicChannelUpstreamHandler.java:147)
>>>>         at
>>>>
>>>> org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:75)
>>>>         at
>>>>
>>>> org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:558)
>>>>         at
>>>>
>>>> org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:777)
>>>>
>>>>         at
>>>>
>>>> org.jboss.netty.channel.SimpleChannelUpstreamHandler.messageReceived(SimpleChannelUpstreamHandler.java:129)
>>>>         at
>>>>
>>>> org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:75)
>>>>         at
>>>>
>>>> org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:558)
>>>>         at
>>>>
>>>> org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:777)
>>>>
>>>>         at
>>>>
>>>> org.jboss.netty.handler.execution.ChannelUpstreamEventRunnable.run(ChannelUpstreamEventRunnable.java:44)
>>>>         at
>>>>
>>>> org.jboss.netty.handler.execution.OrderedMemoryAwareThreadPoolExecutor$ChildExecutor.run(OrderedMemoryAwareThreadPoolExec
>>>> utor.java:312)
>>>>         at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
>>>> Source)
>>>>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
>>>> Source)
>>>>         at java.lang.Thread.run(Unknown Source)
>>>> ------
>>>>
>>>> Stefano
>>>>
>>>> 2012/3/7 Eric Charles<eric@apache.org>:
>>>>>
>>>>>
>>>>> Hi Stefano,
>>>>>
>>>>> Thx for testing. I tried to reproduce the behavior you describe on 2
>>>>> boxes
>>>>> (macosx with 3.0beta4, and ubuntu with snapshot from 2 weeks ago), and
>>>>> both
>>>>> give me the same correct answer:
>>>>>
>>>>> 220 ... JAMES SMTP Server Server (JAMES SMTP Server ) ready
>>>>> EHLO test.com
>>>>> 250-cll0353.fednot.be Hello test.com [0:0:0:0:0:0:0:1%0])
>>>>> 250-AUTH LOGIN PLAIN
>>>>> 250-AUTH=LOGIN PLAIN
>>>>> 250-PIPELINING
>>>>> 250-ENHANCEDSTATUSCODES
>>>>> 250 8BITMIME
>>>>>
>>>>> Do you have any exception in the log?
>>>>>
>>>>> I will leave the vote open for 1 more week so others can further test
>>>>> and
>>>>> vote.
>>>>>
>>>>> So the vote is prolonged until Wednesday 14 March 2012 09:00 GMT.
>>>>>
>>>>> Thx,
>>>>>
>>>>> Eric
>>>>>
>>>>>
>>>>>
>>>>> On 07/03/12 10:26, Stefano Bagnara wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> I'm not sure where the issue is, but there is something wrong in
the
>>>>>> smtp protocol:
>>>>>>
>>>>>> <      220 bago-dv6 JAMES SMTP Server Server (JAMES SMTP Server
)
>>>>>> ready
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> EHLO test.com
>>>>>>
>>>>>>
>>>>>>
>>>>>> <      451 Unable to process request
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> EHLO test.com
>>>>>>
>>>>>>
>>>>>>
>>>>>> <      250-bago-dv6 Hello test.com [127.0.0.1])
>>>>>> <      250-PIPELINING
>>>>>> <      250-ENHANCEDSTATUSCODES
>>>>>> <      250 8BITMIME
>>>>>>
>>>>>> The first time I "present myself" the command is unrecognized.
>>>>>>
>>>>>> Probably this has not been recognized before because most email
>>>>>> clients first try to present using EHLO and on failure they move
to
>>>>>> HELO.. so probably they are falling back to HELO and still being
able
>>>>>> to send (not using 8bitmime and pipelining of course).
>>>>>>
>>>>>> Can anyone reproduce the issue? If so we should cancel this release
>>>>>> (this could lead to loose incoming email).
>>>>>>
>>>>>> Stefano
>>>>>>
>>>>>> 2012/3/2 Eric Charles<eric@apache.org>:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Hi there,
>>>>>>>
>>>>>>> We are ready to vote for James server application 3.0-beta4 based
on
>>>>>>> the
>>>>>>> latest and greatest Protocols 1.6.2, Mailbox 0.3, IMAP 0.4 and
jSieve
>>>>>>> 0.5.
>>>>>>>
>>>>>>> This vote is a conjoint vote to release server and app 3.0-beta4
>>>>>>> projects.
>>>>>>>
>>>>>>> So please cast your VOTE for Apache James Server 3.0b4 release:
>>>>>>>
>>>>>>> [ ] +1 Please release
>>>>>>> [ ] +0 No time to review
>>>>>>> [ ] -1 Something is wrong
>>>>>>>
>>>>>>> Release Notes:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10411&version=12317240
>>>>>>>
>>>>>>> SVN tags:
>>>>>>>
>>>>>>> https://svn.apache.org/repos/asf/james/app/tags/apache-james-3.0-beta4/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> https://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-beta4/
>>>>>>>
>>>>>>> Source tarballs:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> https://repository.apache.org/content/repositories/orgapachejames-043/org/apache/james/apache-james/3.0-beta4/apache-james-3.0-beta4-app.zip
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> https://repository.apache.org/content/repositories/orgapachejames-042/org/apache/james/james-server/3.0-beta4/james-server-3.0-beta4-source-release.zip
>>>>>>>
>>>>>>> Staging repositories:
>>>>>>>
>>>>>>> https://repository.apache.org/content/repositories/orgapachejames-043/
>>>>>>>
>>>>>>> https://repository.apache.org/content/repositories/orgapachejames-042/
>>>>>>>
>>>>>>> Thx.
>>>>>>> --
>>>>>>> eric | http://about.echarles.net | @echarles
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>>>>>>> For additional commands, e-mail: server-dev-help@james.apache.org
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>>>>>> For additional commands, e-mail: server-dev-help@james.apache.org
>>>>>>
>>>>>
>>>>> --
>>>>> eric | http://about.echarles.net | @echarles
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>>>>> For additional commands, e-mail: server-dev-help@james.apache.org
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>>>> For additional commands, e-mail: server-dev-help@james.apache.org
>>>>
>>>
>>> --
>>> eric | http://about.echarles.net | @echarles
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>>> For additional commands, e-mail: server-dev-help@james.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-dev-help@james.apache.org
>>
>
> --
> eric | http://about.echarles.net | @echarles
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message