Re: James 3.0 release date

2016-11-22 Thread Matthieu Baechler 

Thank you for you proposition.

Here are some tasks on which we would be ready to mentor contributors :

https://issues.apache.org/jira/browse/JAMES-1862

https://issues.apache.org/jira/browse/MAILBOX-278

https://issues.apache.org/jira/browse/MAILBOX-279

Please let us know if you want to pick one.


Regards,

--

Matthieu Baechler


Le 22/11/2016 à 20:50, Rudi Angela a écrit :

Hi Matthieu,

I’d be glad to help if you have small tasks (as my time is somewhat limited). I 
have years of Java experience, have been using James for some years now and 
have even hacked it a bit, like creating a mailet for my custom needs and even 
adapting the SMTP server to fail fast.
Do you have a list of tasks? I don’t mind bug fixing. Seems easier to me than 
implementing new features.

Rudi


On 22 Nov 2016, at 07:39, Matthieu Baechler > wrote:

There's definitely tasks we could delegate and give some mentoring on, so if 
anybody's interesting to help, we'll be more than happy to share the work.





-
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org

Re: James 3.0 release date

2016-11-22 Thread Rudi Angela 
Hi Matthieu,

I’d be glad to help if you have small tasks (as my time is somewhat limited). I 
have years of Java experience, have been using James for some years now and 
have even hacked it a bit, like creating a mailet for my custom needs and even 
adapting the SMTP server to fail fast.
Do you have a list of tasks? I don’t mind bug fixing. Seems easier to me than 
implementing new features.

Rudi

> On 22 Nov 2016, at 07:39, Matthieu Baechler  > wrote:
> 
> There's definitely tasks we could delegate and give some mentoring on, so if 
> anybody's interesting to help, we'll be more than happy to share the work.

RE: James 3.0 release date

2016-11-22 Thread Dumah 7 
I don't know what kind of tasks you are talking about getting help with, and I 
don't have much (or any) free time, but MAYBE I could help if there is 
something I could handle.

I am a developer (coding anything except Apple-related stuff), but I am not 
such a huge fan of Java, although it is very portable and cross platform, which 
is a good thing.

I have yesterday gotten the `apache-james-3.0-beta4-app`, set it up on a 
dynamic IP domain, and let it run. Soon I will make it use TLS as well. I still 
need to make it use a DB instead of the filesystem, so hopefully I will manage 
to make it use SQL Server soon (hopefully it works - I have no idea if you have 
tested James with SQL Server, but anyway).
So, since I am torturing myself with all these configurations, and reading the 
documentation on your site seems like riddle-solving, maybe I could do 
something related to that... I am not promising anything, since my schedule is 
crazy and my mind already about to explode, but maybe I can do something...
Definitely, I could make a long list of questions for someone to answer which 
you can post as FAQ in your site...

Irrelevant: I know that this is too early to have, but I think that having a 
management UI tool that updates the configs based on the user interaction and 
also manages the mail server would help a lot the users. Although, having used 
other Apache software in the past (Solr), it seems to me that helping newbie 
users out is not a high priority in your list.




-Original Message-
From: Matthieu Baechler [mailto:mbaech...@linagora.com] 
Sent: Tuesday, November 22, 2016 1:40 PM
To: server-user@james.apache.org
Subject: Re: James 3.0 release date

Hi Mahesh,

We found it really difficult to evaluate how much work is left to do for the 
release.

We decided to split things a bit : we'll release a RC1 as soon as planned dev 
tasks are done and we will then focus on performance and stability testing 
starting then and we'll finish website tasks too.

The tentative release date for RC1 is december the 12th.

There's definitely tasks we could delegate and give some mentoring on, so if 
anybody's interesting to help, we'll be more than happy to share the work.


Regards,

-- 

Matthieu Baechler


Le 22/11/2016 à 08:17, Mahesh Sivarama Pillai a écrit :
> Hi Matthieu,
>
>   Did you guys get a chance to meet to talk about James 3.0 release date ?
> Please share.
>
> Thanks
> Mahesh
>
> On Thu, Nov 17, 2016 at 6:05 PM, Mahesh Sivarama Pillai 
> 
> wrote:
>
>> Thanks Matthieu. Eagerly waiting for it :)
>>
>> Thanks
>> Mahesh
>>
>> On 17-Nov-2016 6:02 PM, "Matthieu Baechler" 
>> wrote:
>>
>>> Hi Mahesh,
>>>
>>> Le 17/11/2016 à 10:27, Mahesh Sivarama Pillai a écrit :
>>>
 Hi,

Is there a tentative release date planned for James 3.0 ?


>>> We'll have a meeting about that on monday and we'll communicate on 
>>> the mailling lists.
>>>
>>> Regards,
>>>
>>> --
>>> Matthieu Baechler
>>>
>>> 
>>> - To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
>>> For additional commands, e-mail: server-user-h...@james.apache.org
>>>
>>>


-
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org

Re: James 3.0 release date

2016-11-22 Thread Matthieu Baechler 

Hi Mahesh,

We found it really difficult to evaluate how much work is left to do for 
the release.


We decided to split things a bit : we'll release a RC1 as soon as 
planned dev tasks are done and we will then focus on performance and 
stability testing starting then and we'll finish website tasks too.


The tentative release date for RC1 is december the 12th.

There's definitely tasks we could delegate and give some mentoring on, 
so if anybody's interesting to help, we'll be more than happy to share 
the work.



Regards,

--

Matthieu Baechler


Le 22/11/2016 à 08:17, Mahesh Sivarama Pillai a écrit :

Hi Matthieu,

  Did you guys get a chance to meet to talk about James 3.0 release date ?
Please share.

Thanks
Mahesh

On Thu, Nov 17, 2016 at 6:05 PM, Mahesh Sivarama Pillai 
wrote:


Thanks Matthieu. Eagerly waiting for it :)

Thanks
Mahesh

On 17-Nov-2016 6:02 PM, "Matthieu Baechler" 
wrote:


Hi Mahesh,

Le 17/11/2016 à 10:27, Mahesh Sivarama Pillai a écrit :


Hi,

   Is there a tentative release date planned for James 3.0 ?



We'll have a meeting about that on monday and we'll communicate on the
mailling lists.

Regards,

--
Matthieu Baechler

-
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org





-
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org

Re[2]: Apache James 3.0-beta5 is for early adopters

2016-11-22 Thread Alex Sviridov 
Hi Benoit

Thank you very much for quick answer and nice work.

Best regards, Alex


>Вторник, 22 ноября 2016, 10:33 +03:00 от Benoit Tellier 
>:
>
>You miss some configuration files for the indexer.
>
>Some new configuration files were introduced for Spring. Please check
>https://github.com/apache/james-project/tree/master/dockerfiles/run/spring/destination/conf
>and ensure you have the file showing up there.
>
>Cheers,
>
>Benoit Tellier
>
>Le 22/11/2016 à 14:11, Alex Sviridov a écrit :
>> Hi all.
>> 
>> I downloaded apache james 3 beta 5 (although it is named beta 6 in archive) 
>> from here  https://james.apache.org/download.cgi#Apache_James_Server
>> 
>> And when I do: ./james start  I get the following exception (see below). How 
>> to fix it?
>> 
>> 
>> WARN  10:01:57,621 | 
>> org.apache.james.container.spring.context.JamesServerApplicationContext | 
>> Exception encountered during context initialization - cancelling refresh 
>> attempt
>> org.springframework.beans.FatalBeanException: Unable to config the indexer; 
>> nested exception is org.apache.commons.configuration.ConfigurationException: 
>> Unable to load configuration for component indexer
>> at 
>> org.apache.james.container.spring.bean.factorypostprocessor.IndexerConfigurationBeanFactoryPostProcessor.postProcessBeanFactory(IndexerConfigurationBeanFactoryPostProcessor.java:67)
>> at 
>> org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:696)
>> at 
>> org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:686)
>> at 
>> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:461)
>> at 
>> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:139)
>> at 
>> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:93)
>> at 
>> org.apache.james.container.spring.context.JamesServerApplicationContext.(JamesServerApplicationContext.java:40)
>> at 
>> org.apache.james.app.spring.JamesAppSpringMain.init(JamesAppSpringMain.java:61)
>> at 
>> org.apache.james.app.spring.JamesAppSpringMain.main(JamesAppSpringMain.java:42)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at 
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at 
>> org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:240)
>> at java.lang.Thread.run(Thread.java:745)
>> Caused by: org.apache.commons.configuration.ConfigurationException: Unable 
>> to load configuration for component indexer
>> at 
>> org.apache.james.container.spring.lifecycle.ConfigurationProviderImpl.getConfiguration(ConfigurationProviderImpl.java:135)
>> at 
>> org.apache.james.container.spring.bean.factorypostprocessor.IndexerConfigurationBeanFactoryPostProcessor.postProcessBeanFactory(IndexerConfigurationBeanFactoryPostProcessor.java:47)
>> ... 14 more
>> INFO  10:03:06,335 | 
>> org.apache.james.container.spring.context.JamesServerApplicationContext | 
>> Refreshing 
>> org.apache.james.container.spring.context.JamesServerApplicationContext@643f1d81:
>>  startup date [Tue Nov 22 10:03:06 MSK 2016]; root of context hierarchy
>> WARN  10:03:09,065 | 
>> org.apache.james.container.spring.context.JamesServerApplicationContext | 
>> Exception encountered during context initialization - cancelling refresh 
>> attempt
>> org.springframework.beans.FatalBeanException: Unable to config the indexer; 
>> nested exception is org.apache.commons.configuration.ConfigurationException: 
>> Unable to load configuration for component indexer
>> at 
>> org.apache.james.container.spring.bean.factorypostprocessor.IndexerConfigurationBeanFactoryPostProcessor.postProcessBeanFactory(IndexerConfigurationBeanFactoryPostProcessor.java:67)
>> at 
>> org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:696)
>> at 
>> org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:686)
>> at 
>> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:461)
>> at 
>> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:139)
>> at 
>> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:93)
>> at 
>> org.apache.james.container.spring.context.JamesServerApplicationContext.(JamesServerApplicationContext.java:40)
>> at 
>>