You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Eric Charles <er...@apache.org> on 2012/03/02 16:27:55 UTC
[VOTE] Release Apache James Server and App 3.0-beta4
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
[RESULT][VOTE] Release Apache James Server and App 3.0-beta4
Posted by Eric Charles <er...@apache.org>.
Hi there,
The VOTE passed for the server artifacts
(https://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-beta4/):
+1 Ioan, Eric*, Manolo*, Stefano*
+0 Felix*, Vincenzo*
-1
* Binding
I will push the server artifacts to the maven central and the mirrors.
We miss one binding vote for the app artifacts (same result as for
server, minus Stefano). I opened JAMESAPP-4 and will commit a new NOTICE
file before relaunching a vote for app.
Thx for your reviews and votes,
Eric
On 07/03/12 17:09, Eric Charles wrote:
> I just run rat on the app project, but it only audits the source/conf
> files, not the declared dependencies (the jar).
>
> Maybe this is due to the assembly 'nature' of this maven project?
>
> Robert?
>
> *****************************************************
> Summary
> -------
> Generated at: 2012-03-07T17:07:57+01:00
> Notes: 12
> Binaries: 0
> Archives: 0
> Standards: 58
>
> Apache Licensed: 56
> Generated Documents: 0
>
> JavaDocs are generated and so license header is optional
> Generated files do not required license headers
>
> 2 Unknown Licenses
>
> *******************************
>
> Unapproved licenses:
>
> README.crypto
> src/main/licensing/app/notice-for-binary.txt
>
>
> Thx,
> Eric
>
>
> On 07/03/12 15:17, Stefano Bagnara wrote:
>> 2012/3/7 Eric Charles<er...@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<er...@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<er...@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<er...@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
>>
>
--
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
Re: [VOTE] Release Apache James Server and App 3.0-beta4
Posted by Stefano Bagnara <ap...@bago.org>.
2012/3/7 Eric Charles <er...@apache.org>:
> I just run rat on the app project, but it only audits the source/conf files,
> not the declared dependencies (the jar).
>
> Maybe this is due to the assembly 'nature' of this maven project?
>
> Robert?
The tool used by Robert the last time was not rat but "apache rat
whisker". IIRC it is ant based, but I never used it. I just remember
Robert created it when we had to deal with james b3 release. Maybe
looking through mail archives will help.
Stefano
> *****************************************************
> Summary
> -------
> Generated at: 2012-03-07T17:07:57+01:00
> Notes: 12
> Binaries: 0
> Archives: 0
> Standards: 58
>
> Apache Licensed: 56
> Generated Documents: 0
>
> JavaDocs are generated and so license header is optional
> Generated files do not required license headers
>
> 2 Unknown Licenses
>
> *******************************
>
> Unapproved licenses:
>
> README.crypto
> src/main/licensing/app/notice-for-binary.txt
>
>
> Thx,
> Eric
>
>
>
> On 07/03/12 15:17, Stefano Bagnara wrote:
>>
>> 2012/3/7 Eric Charles<er...@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<er...@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<er...@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<er...@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
>>
>
> --
> 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
Re: [VOTE] Release Apache James Server and App 3.0-beta4
Posted by Eric Charles <er...@apache.org>.
I just run rat on the app project, but it only audits the source/conf
files, not the declared dependencies (the jar).
Maybe this is due to the assembly 'nature' of this maven project?
Robert?
*****************************************************
Summary
-------
Generated at: 2012-03-07T17:07:57+01:00
Notes: 12
Binaries: 0
Archives: 0
Standards: 58
Apache Licensed: 56
Generated Documents: 0
JavaDocs are generated and so license header is optional
Generated files do not required license headers
2 Unknown Licenses
*******************************
Unapproved licenses:
README.crypto
src/main/licensing/app/notice-for-binary.txt
Thx,
Eric
On 07/03/12 15:17, Stefano Bagnara wrote:
> 2012/3/7 Eric Charles<er...@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<er...@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<er...@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<er...@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
>
--
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
Re: [VOTE] Release Apache James Server and App 3.0-beta4
Posted by Stefano Bagnara <ap...@bago.org>.
2012/3/7 Eric Charles <er...@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<er...@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<er...@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<er...@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
Re: [VOTE] Release Apache James Server and App 3.0-beta4
Posted by Eric Charles <er...@apache.org>.
On 07/03/12 13:17, Stefano Bagnara wrote:
> Sorry, it was not about encoding, but a problem in the telnet client I
> used to do the tests.
> This is a new box and I used putty and I forgot to remove the "active
> telnet protocol negotiation", so it was sending garbage to the
> smtpserver during the connection.
>
> So:
> [X] +1 to release
> https://repository.apache.org/content/repositories/orgapachejames-042/
>
Cool. Thx for the review.
> 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.
Will you do the review (just to coordinate ourselves) ?
Thx,
Eric
> Stefano
>
> 2012/3/7 Eric Charles<er...@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<er...@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<er...@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
Re: [VOTE] Release Apache James Server and App 3.0-beta4
Posted by Stefano Bagnara <ap...@bago.org>.
Sorry, it was not about encoding, but a problem in the telnet client I
used to do the tests.
This is a new box and I used putty and I forgot to remove the "active
telnet protocol negotiation", so it was sending garbage to the
smtpserver during the connection.
So:
[X] +1 to release
https://repository.apache.org/content/repositories/orgapachejames-042/
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).
Stefano
2012/3/7 Eric Charles <er...@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<er...@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<er...@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
Re: [VOTE] Release Apache James Server and App 3.0-beta4
Posted by Eric Charles <er...@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<er...@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<er...@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
Re: [VOTE] Release Apache James Server and App 3.0-beta4
Posted by Stefano Bagnara <ap...@bago.org>.
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 <er...@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<er...@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
Re: [VOTE] Release Apache James Server and App 3.0-beta4
Posted by Eric Charles <er...@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<er...@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
Re: [VOTE] Release Apache James Server and App 3.0-beta4
Posted by Stefano Bagnara <ap...@bago.org>.
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 <er...@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
Re: [VOTE] Release Apache James Server and App 3.0-beta4
Posted by Eric Charles <er...@apache.org>.
Hi,
I will close the vote on Wednesday 07 March 2012 09:00 GMT.
Thx, Eric
On 02/03/12 16:27, Eric Charles wrote:
> 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
Re: [VOTE] Release Apache James Server and App 3.0-beta4
Posted by Vincenzo Gianferrari Pini <vi...@gocloud.it>.
[X] +0 No time to review
Sorry guys, but currently I'm unable to follow it. I hope in the future to
be more helpful.
Ciao,
Vincenzo
2012/3/2 Eric Charles <er...@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<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/app/tags/apache-james-3.0-beta4/>
> https://svn.apache.org/repos/**asf/james/server/tags/james-**
> server-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-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<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-043/>
> https://repository.apache.org/**content/repositories/**orgapachejames-042/<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<se...@james.apache.org>
> For additional commands, e-mail: server-dev-help@james.apache.**org<se...@james.apache.org>
>
>
--
Il presente messaggio ed i suoi allegati sono confidenziali in ragione
della loro natura professionale e, in ogni caso, non accessibili al
pubblico. Nel caso in cui il presente messaggio sia ricevuto da soggetto
diverso dal suo diretto destinatario, si prega di darne immediata notizia
al n° +390236680761 e di procedere immediatamente alla distruzione dello
stesso e dei suoi allegati, da effettuarsi senza copiarne o rivelarne ad
alcuno il contenuto. Grazie per la collaborazione.
This e-mail and any attachments thereto are confidential and may be
covered by legal professional privilege or otherwise protected from
disclosure. If you are not the intended recipient, please notify us
immediately by phone at +390236680761 and then immediately destroy this
message and any attachments from your system, without copying or disclosing
the contents to any other person. Thank you for your co-operation.
Re: [VOTE] Release Apache James Server and App 3.0-beta4
Posted by Felix Knecht <fe...@otego.com>.
> [X] +0 No time to review
It seem to work for most devs except me, so this seems to be a problem
of my machine setup..
Regards
Felix
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [VOTE] Release Apache James Server and App 3.0-beta4
Posted by Manuel Carrasco Moñino <ma...@apache.org>.
+1 Please release
- Manolo
On Sat, Mar 3, 2012 at 8:31 AM, Eric Charles <er...@apache.org> wrote:
> [X] +1 Please release
>
> Eric
>
>
>
> On 02/03/12 16:27, Eric Charles wrote:
>
>> 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<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/app/tags/apache-james-3.0-beta4/>
>> https://svn.apache.org/repos/**asf/james/server/tags/james-**
>> server-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-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<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-043/>
>> https://repository.apache.org/**content/repositories/**
>> orgapachejames-042/<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<se...@james.apache.org>
> For additional commands, e-mail: server-dev-help@james.apache.**org<se...@james.apache.org>
>
>
Re: [VOTE] Release Apache James Server and App 3.0-beta4
Posted by Eric Charles <er...@apache.org>.
[X] +1 Please release
Eric
On 02/03/12 16:27, Eric Charles wrote:
> 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
Re: [VOTE] Release Apache James Server and App 3.0-beta4
Posted by Ioan Eugen Stan <st...@gmail.com>.
+1 Please release
Retried build on work machine and it wen well. I believe Debian Maven
installation is broken (it's still in experimental repo so this is not
a surprise).
2012/3/4 Ioan Eugen Stan <st...@gmail.com>:
> Hi Eric,
>
> În data de 03.03.2012 09:31, "Eric Charles" <er...@apache.org> a scris:
>
>
>>
>> On 02/03/12 22:32, Ioan Eugen Stan wrote:
>>>
>>> Netbeans embedded maven version builds without errors. Maven2 (stable)
>>> and Maven3 (experimental) fail with errors in the Server HBase Data
>>> Persistence.
>>
>>
>> Hi Ioan,
>>
>> Can you post the failing tests and the eventual stacktraces ? (in
>> target/surefire-reports).
>
> I will post them as soon as I get internet on the pc. P.s. james builds ok
> on openjdk 7, with netbeans 7.1 embedded maven.
>
>> If have relaunched the build on jenkins server/trunk, and it builds/tests
>> fine (such as the last 2 ones):
>> Success > Console Output #2686 Mar 3, 2012 7:02:03 AM
>> Success > Console Output #2685 Mar 2, 2012 3:32:06 PM
>> Success > Console Output #2684 Mar 2, 2012 11:46:27 AM
>>
>> 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
>>
--
Ioan Eugen Stan
http://ieugen.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [VOTE] Release Apache James Server and App 3.0-beta4
Posted by Ioan Eugen Stan <st...@gmail.com>.
Hi Eric,
În data de 03.03.2012 09:31, "Eric Charles" <er...@apache.org> a scris:
>
> On 02/03/12 22:32, Ioan Eugen Stan wrote:
>>
>> Netbeans embedded maven version builds without errors. Maven2 (stable)
>> and Maven3 (experimental) fail with errors in the Server HBase Data
>> Persistence.
>
>
> Hi Ioan,
>
> Can you post the failing tests and the eventual stacktraces ? (in
target/surefire-reports).
I will post them as soon as I get internet on the pc. P.s. james builds ok
on openjdk 7, with netbeans 7.1 embedded maven.
> If have relaunched the build on jenkins server/trunk, and it builds/tests
fine (such as the last 2 ones):
> Success > Console Output #2686 Mar 3, 2012 7:02:03 AM
> Success > Console Output #2685 Mar 2, 2012 3:32:06 PM
> Success > Console Output #2684 Mar 2, 2012 11:46:27 AM
>
> 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
>
Re: [VOTE] Release Apache James Server and App 3.0-beta4
Posted by Eric Charles <er...@apache.org>.
On 02/03/12 22:32, Ioan Eugen Stan wrote:
> Netbeans embedded maven version builds without errors. Maven2 (stable)
> and Maven3 (experimental) fail with errors in the Server HBase Data
> Persistence.
Hi Ioan,
Can you post the failing tests and the eventual stacktraces ? (in
target/surefire-reports).
If have relaunched the build on jenkins server/trunk, and it
builds/tests fine (such as the last 2 ones):
Success > Console Output #2686 Mar 3, 2012 7:02:03 AM
Success > Console Output #2685 Mar 2, 2012 3:32:06 PM
Success > Console Output #2684 Mar 2, 2012 11:46:27 AM
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
Re: [VOTE] Release Apache James Server and App 3.0-beta4
Posted by Ioan Eugen Stan <st...@gmail.com>.
2012/3/2 Eric Charles <er...@apache.org>:
> Hi Felix,
>
> I'm also having such stacktraces, but build/test are successful.
> (There are also other modules where exceptions are printed or silently
> dropped). But it's true that default configuration with
> hadoop-metrics2.properties would be welcome.
>
> So, do you have failing tests ?
>
> Thx, Eric
Netbeans embedded maven version builds without errors. Maven2 (stable)
and Maven3 (experimental) fail with errors in the Server HBase Data
Persistence.
--
Ioan Eugen Stan
http://ieugen.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [VOTE] Release Apache James Server and App 3.0-beta4
Posted by Eric Charles <er...@apache.org>.
Hi Felix,
I'm also having such stacktraces, but build/test are successful.
(There are also other modules where exceptions are printed or silently
dropped). But it's true that default configuration with
hadoop-metrics2.properties would be welcome.
So, do you have failing tests ?
Thx, Eric
On 02/03/12 20:29, Felix Knecht wrote:
> Still some problems/errors when building:
>
> [INFO] Surefire report directory:
> /tmp/james-server-3.0-beta4/data-hbase/target/surefire-reports
>
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
>
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.apache.james.JamesServerHBaseSuiteTest
> 2012-03-02 20:26:48,381 [main] WARN
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl - Metrics system not
> started: Cannot locate configuration: tried
> hadoop-metrics2-namenode.properties, hadoop-metrics2.properties
> Starting DataNode 0 with dfs.data.dir:
> /tmp/james-server-3.0-beta4/data-hbase/target/test-data/9ff31753-87d1-4a65-ad1e-2ce73affe112/dfs/data/data1,/tmp/james-server-3.0-beta4/data-hbase/target/test-data/9ff31753-87d1-4a65-ad1e-2ce73affe112/dfs/data/data2
>
> 2012-03-02 20:26:48,810 [main] WARN
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl - Metrics system not
> started: Cannot locate configuration: tried
> hadoop-metrics2-datanode.properties, hadoop-metrics2.properties
> 2012-03-02 20:26:48,810 [main] WARN
> org.apache.hadoop.metrics2.util.MBeans -
> Hadoop:service=DataNode,name=MetricsSystem,sub=Control
> javax.management.InstanceAlreadyExistsException: MXBean already
> registered with name Hadoop:service=NameNode,name=MetricsSystem,sub=Control
> at com.sun.jmx.mbeanserver.MXBeanLookup.addReference(MXBeanLookup.java:120)
> at com.sun.jmx.mbeanserver.MXBeanSupport.register(MXBeanSupport.java:143)
> at com.sun.jmx.mbeanserver.MBeanSupport.preRegister2(MBeanSupport.java:183)
>
>
> And no, it's not a Windows machine:
> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Maven home: /etc/alternatives/mvn
> Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/jdk1.6.0_29/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.2.8-3.fc16.x86_64", arch: "amd64", family:
> "unix"
>
> Is it only me having these problems?
>
> Felix
>
>
>
> On 03/02/2012 04:27 PM, Eric Charles wrote:
>> 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.
>
>
> ---------------------------------------------------------------------
> 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
Re: [VOTE] Release Apache James Server and App 3.0-beta4
Posted by Felix Knecht <fe...@apache.org>.
Still some problems/errors when building:
[INFO] Surefire report directory:
/tmp/james-server-3.0-beta4/data-hbase/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.james.JamesServerHBaseSuiteTest
2012-03-02 20:26:48,381 [main] WARN
org.apache.hadoop.metrics2.impl.MetricsSystemImpl - Metrics system not
started: Cannot locate configuration: tried
hadoop-metrics2-namenode.properties, hadoop-metrics2.properties
Starting DataNode 0 with dfs.data.dir:
/tmp/james-server-3.0-beta4/data-hbase/target/test-data/9ff31753-87d1-4a65-ad1e-2ce73affe112/dfs/data/data1,/tmp/james-server-3.0-beta4/data-hbase/target/test-data/9ff31753-87d1-4a65-ad1e-2ce73affe112/dfs/data/data2
2012-03-02 20:26:48,810 [main] WARN
org.apache.hadoop.metrics2.impl.MetricsSystemImpl - Metrics system not
started: Cannot locate configuration: tried
hadoop-metrics2-datanode.properties, hadoop-metrics2.properties
2012-03-02 20:26:48,810 [main] WARN
org.apache.hadoop.metrics2.util.MBeans -
Hadoop:service=DataNode,name=MetricsSystem,sub=Control
javax.management.InstanceAlreadyExistsException: MXBean already
registered with name Hadoop:service=NameNode,name=MetricsSystem,sub=Control
at
com.sun.jmx.mbeanserver.MXBeanLookup.addReference(MXBeanLookup.java:120)
at
com.sun.jmx.mbeanserver.MXBeanSupport.register(MXBeanSupport.java:143)
at
com.sun.jmx.mbeanserver.MBeanSupport.preRegister2(MBeanSupport.java:183)
And no, it's not a Windows machine:
Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Maven home: /etc/alternatives/mvn
Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/jdk1.6.0_29/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.2.8-3.fc16.x86_64", arch: "amd64", family:
"unix"
Is it only me having these problems?
Felix
On 03/02/2012 04:27 PM, Eric Charles wrote:
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org