Re: Errors while starting James 3.5 (Sieve)

[Benoit Tellier]

Hello Matt, Hello Christian,

Every time we merge a pull request, we have a working build (both
compilation and unit tests) as our CI run against GitHub pull requests.
So your issues are not expected.

Could you provide us the maven command you issue, the git project you
are trying to build, your JDK version, maven version, as well as the
error, and the exact failing maven project ?

Best regards,

Benoit

Le 19/01/2017 à 00:42, cryptearth a écrit :
> Well, unfortunately I wasn't able to compile the current commit either. It 
> fails on cassandra. As I said: wait a day or two for the next commit, 
> re-clone the repo and try it again. It should work on at least one of the 
> next 5 - 10 commits to get a working one.
> If you want I can do the compilation for you and can provide the built 
> package, but be aware I would only deliever it as is w/o taking any 
> responsebility for issues you might encounter when using the package compiled 
> by me.
> 
> If I can get a working build (I don't have the package I built myself handy) 
> I can provide you with a link (would be send directly to you instead of the 
> list).
> 
> Greetings from Germany,
> 
> Matt
> 
>  Christian Fischer schrieb 
> 
>> Hey there,
>>
>> I tried to build the current beta6 but i did not have sucess
>> I do not know how to do it correctly (building it), and since Google
>> delived me nothing useful (maybe i am searching with wrong arguments ),
>> i would like to ask you, if you have something like an instruction for me ??
>>
>> Thanks
>>
>>
>>
>>
>> 2017-01-03 5:50 GMT+01:00 Mathias Rodenberg :
>>
>>> Hey Christian,
>>>
>>> your log shows not only a fatal Exception regarding the Sieve class, but
>>> also some other serious Exceptions that some configs or classes are corrupt
>>> or missing. As this is beta5 - I'm guessing you just downloaded the binary
>>> files and tried to run them. Sadly, James3 isn't able to run out-of-the-box
>>> that easy and require some tweaking with the tounge at the right angle.
>>> I would recommend you to clone current beta6 git repo and built it from
>>> source. On a Linux system this is very easy by simply installing maven, git
>>> and java-devel packages, this should be easy on a Windows system too.
>>> Be aware: the current james-repo is an active development repo, so it's
>>> possible to clone a commit wich can't be build (happend to my several
>>> times). If so - just wait a day or two and re-clone the newest commit again
>>> - it then should be compileable (or repeat if needed until you get a clean
>>> build).
>>> After unpacking the fresh build there are only template configs, but some
>>> of them need to be activated for James to successfully start up. The
>>> startup sequence will tell you wich config-file can't be loaded - simply
>>> switch to config-dir, enable the needed config, and re-try until james
>>> successfully completely starts up for the first time. You then should be
>>> able to access it remotely with the james-cli config-tool to add your
>>> domain and users. For security reasons the first config you should alter
>>> before enabling it is smtpserver.xml: on line 91 switch the 
>>> tag to "true" to prevent your mail-server being an open relay to the world.
>>> All the other settings should be fine as long as you need them to be
>>> secific values.
>>>
>>> Hope it helps,
>>> oh, and a happy new year to all subscribers
>>>
>>> yours,
>>>
>>> Matt
>>>
>>>
>>> Am 01.01.2017 um 22:43 schrieb Christian Fischer:
>>>
 Hey there,
 i have some errors while starting James ...
 I hope somebody can help me.

 Thanks in advantage !

 INFO  22:41:18,520 |
 org.apache.james.container.spring.context.JamesServerApplicationContext |
 Refreshing
 org.apache.james.container.spring.context.JamesServerApplica
 tionContext@31a5c39e:
 startup date [Sun Jan 01 22:41:18 CET 2017]; root of context hierarchy
 DEBUG 22:41:24,319 |
 org.apache.james.container.spring.context.JamesServerApplicationContext |
 Bean factory for
 org.apache.james.container.spring.context.JamesServerApplica
 tionContext@31a5c39e:
 org.springframework.beans.factory.support.DefaultListableBea
 nFactory@54d1608f:
 defining beans
 [org.springframework.context.annotation.internalConfiguratio
 nAnnotationProcessor,org.springframework.context.annotation.
 internalAutowiredAnnotationProcessor,org.springframework.con
 text.annotation.internalRequiredAnnotationProcessor,org.
 springframework.context.annotation.internalCommonAnnotationProcessor,org.
 springframework.context.annotation.internalPersistence
 AnnotationProcessor,org.springframework.context.
 annotation.CommonAnnotationBeanPostProcessor#0,org.
 springframework.orm.jpa.support.PersistenceAnnotationB
 eanPostProcessor#0,org.apache.james.container.spring.
 lifecycle.LogEnabledBeanPostProcessor#0,logprovider,org.
 

Re: Errors while starting James 3.5 (Sieve)

[Christian Fischer]

Hey there,

I tried to build the current beta6 but i did not have sucess
I do not know how to do it correctly (building it), and since Google
delived me nothing useful (maybe i am searching with wrong arguments ),
i would like to ask you, if you have something like an instruction for me ??

Thanks




2017-01-03 5:50 GMT+01:00 Mathias Rodenberg :

> Hey Christian,
>
> your log shows not only a fatal Exception regarding the Sieve class, but
> also some other serious Exceptions that some configs or classes are corrupt
> or missing. As this is beta5 - I'm guessing you just downloaded the binary
> files and tried to run them. Sadly, James3 isn't able to run out-of-the-box
> that easy and require some tweaking with the tounge at the right angle.
> I would recommend you to clone current beta6 git repo and built it from
> source. On a Linux system this is very easy by simply installing maven, git
> and java-devel packages, this should be easy on a Windows system too.
> Be aware: the current james-repo is an active development repo, so it's
> possible to clone a commit wich can't be build (happend to my several
> times). If so - just wait a day or two and re-clone the newest commit again
> - it then should be compileable (or repeat if needed until you get a clean
> build).
> After unpacking the fresh build there are only template configs, but some
> of them need to be activated for James to successfully start up. The
> startup sequence will tell you wich config-file can't be loaded - simply
> switch to config-dir, enable the needed config, and re-try until james
> successfully completely starts up for the first time. You then should be
> able to access it remotely with the james-cli config-tool to add your
> domain and users. For security reasons the first config you should alter
> before enabling it is smtpserver.xml: on line 91 switch the 
> tag to "true" to prevent your mail-server being an open relay to the world.
> All the other settings should be fine as long as you need them to be
> secific values.
>
> Hope it helps,
> oh, and a happy new year to all subscribers
>
> yours,
>
> Matt
>
>
> Am 01.01.2017 um 22:43 schrieb Christian Fischer:
>
>> Hey there,
>> i have some errors while starting James ...
>> I hope somebody can help me.
>>
>> Thanks in advantage !
>>
>> INFO  22:41:18,520 |
>> org.apache.james.container.spring.context.JamesServerApplicationContext |
>> Refreshing
>> org.apache.james.container.spring.context.JamesServerApplica
>> tionContext@31a5c39e:
>> startup date [Sun Jan 01 22:41:18 CET 2017]; root of context hierarchy
>> DEBUG 22:41:24,319 |
>> org.apache.james.container.spring.context.JamesServerApplicationContext |
>> Bean factory for
>> org.apache.james.container.spring.context.JamesServerApplica
>> tionContext@31a5c39e:
>> org.springframework.beans.factory.support.DefaultListableBea
>> nFactory@54d1608f:
>> defining beans
>> [org.springframework.context.annotation.internalConfiguratio
>> nAnnotationProcessor,org.springframework.context.annotation.
>> internalAutowiredAnnotationProcessor,org.springframework.con
>> text.annotation.internalRequiredAnnotationProcessor,org.
>> springframework.context.annotation.internalCommonAnnotationProcessor,org.
>> springframework.context.annotation.internalPersistence
>> AnnotationProcessor,org.springframework.context.
>> annotation.CommonAnnotationBeanPostProcessor#0,org.
>> springframework.orm.jpa.support.PersistenceAnnotationB
>> eanPostProcessor#0,org.apache.james.container.spring.
>> lifecycle.LogEnabledBeanPostProcessor#0,logprovider,org.
>> apache.james.container.spring.bean.factorypostprocessor.Conf
>> igurationBeanFactoryPostProcessor#0,org.apache.james.contain
>> er.spring.lifecycle.ConfigurableBeanPostProcessor#0,
>> configurationprovider,mailrepositorystore,mailetloader,
>> matcherloader,protocolhandlerloader,org.apache.james.
>> container.spring.bean.factorypostprocessor.FileSyste
>> mBeanFactoryPostProcessor#0,filesystem,sieveparser,configu
>> rationmanager,authenticator,mailqueuefactory,broker,amqConne
>> ctionFactory,blobTransferPolicy,jmsConnectionFactory,jmsTran
>> sactionManager,mailprocessor,mailetcontext,mailspooler,
>> agent,template,consumerTemplate,jamesCamelContext:beanPostPr
>> ocessor,jamesCamelContext,dnsservice,fetchmail,smtpserver,lmtpserver,
>> pop3server,imapserver,imapProcessor,imapDecoderFacto
>> ry,imapDecoder,imapEncoderFactory,imapEncoder,
>> managesieveserver,org.apache.james.container.spring.bean.fa
>> ctorypostprocessor.IndexerConfigurationBeanFactoryPostProces
>> sor#0,messageParser,org.apache.james.container.spring.
>> bean.factorypostprocessor.MailboxConfigurationBeanFactoryPos
>> tProcessor#0,locker,jvm-locker,no-locker,org.springframework
>> .orm.jpa.support.PersistenceAnnotationBeanPostProcessor#1,
>> jpa-mailboxmanager,jpa-messageIdFactory,jpa-subscript
>> ionManager,jpa-sessionMapperFactory,jpa-uidProvider,jpa-modS
>> 

ApacheCon CFP closing soon (11 February)

[Rich Bowen]

Hello, fellow Apache enthusiast. Thanks for your participation, and
interest in, the projects of the Apache Software Foundation.

I wanted to remind you that the Call For Papers (CFP) for ApacheCon
North America, and Apache: Big Data North America, closes in less than a
month. If you've been putting it off because there was lots of time
left, it's time to dig for that inspiration and get those talk proposals in.

It's also time to discuss with your developer and user community whether
there's a track of talks that you might want to propose, so that you
have more complete coverage of your project than a talk or two.

We're looking for talks directly, and indirectly, related to projects at
the Apache Software Foundation. These can be anything from in-depth
technical discussions of the projects you work with, to talks about
community, documentation, legal issues, marketing, and so on. We're also
very interested in talks about projects and services built on top of
Apache projects, and case studies of how you use Apache projects to
solve real-world problems.

We are particularly interested in presentations from Apache projects
either in the Incubator, or recently graduated. ApacheCon is where
people come to find out what technology they'll be using this time next
year.

Important URLs are:

To submit a talk for Apache: Big Data -
http://events.linuxfoundation.org/events/apache-big-data-north-america/program/cfp
To submit a talk for ApacheCon -
http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp

To register for Apache: Big Data -
http://events.linuxfoundation.org/events/apache-big-data-north-america/attend/register-
To register for ApacheCon -
http://events.linuxfoundation.org/events/apachecon-north-america/attend/register-

Early Bird registration rates end March 12th, but if you're a committer
on an Apache project, you get the low committer rate, which is less than
half of the early bird rate!

For further updated about ApacheCon, follow us on Twitter, @ApacheCon,
or drop by our IRC channel, #apachecon on the Freenode IRC network. Or
contact me - rbo...@apache.org - with any questions or concerns.

Thanks!

Rich Bowen, VP Conferences, Apache Software Foundation

-- 
(You've received this email because you're on a dev@ or users@ mailing
list of an Apache Software Foundation project. For subscription and
unsubscription information, consult the headers of this email message,
as this varies from one list to another.)

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

Re: Errors while starting James 3.5 (Sieve)

[cryptearth]

Well, unfortunately I wasn't able to compile the current commit either. It 
fails on cassandra. As I said: wait a day or two for the next commit, re-clone 
the repo and try it again. It should work on at least one of the next 5 - 10 
commits to get a working one.
If you want I can do the compilation for you and can provide the built package, 
but be aware I would only deliever it as is w/o taking any responsebility for 
issues you might encounter when using the package compiled by me.

If I can get a working build (I don't have the package I built myself handy) I 
can provide you with a link (would be send directly to you instead of the list).

Greetings from Germany,

Matt

 Christian Fischer schrieb 

>Hey there,
>
>I tried to build the current beta6 but i did not have sucess
>I do not know how to do it correctly (building it), and since Google
>delived me nothing useful (maybe i am searching with wrong arguments ),
>i would like to ask you, if you have something like an instruction for me ??
>
>Thanks
>
>
>
>
>2017-01-03 5:50 GMT+01:00 Mathias Rodenberg :
>
>> Hey Christian,
>>
>> your log shows not only a fatal Exception regarding the Sieve class, but
>> also some other serious Exceptions that some configs or classes are corrupt
>> or missing. As this is beta5 - I'm guessing you just downloaded the binary
>> files and tried to run them. Sadly, James3 isn't able to run out-of-the-box
>> that easy and require some tweaking with the tounge at the right angle.
>> I would recommend you to clone current beta6 git repo and built it from
>> source. On a Linux system this is very easy by simply installing maven, git
>> and java-devel packages, this should be easy on a Windows system too.
>> Be aware: the current james-repo is an active development repo, so it's
>> possible to clone a commit wich can't be build (happend to my several
>> times). If so - just wait a day or two and re-clone the newest commit again
>> - it then should be compileable (or repeat if needed until you get a clean
>> build).
>> After unpacking the fresh build there are only template configs, but some
>> of them need to be activated for James to successfully start up. The
>> startup sequence will tell you wich config-file can't be loaded - simply
>> switch to config-dir, enable the needed config, and re-try until james
>> successfully completely starts up for the first time. You then should be
>> able to access it remotely with the james-cli config-tool to add your
>> domain and users. For security reasons the first config you should alter
>> before enabling it is smtpserver.xml: on line 91 switch the 
>> tag to "true" to prevent your mail-server being an open relay to the world.
>> All the other settings should be fine as long as you need them to be
>> secific values.
>>
>> Hope it helps,
>> oh, and a happy new year to all subscribers
>>
>> yours,
>>
>> Matt
>>
>>
>> Am 01.01.2017 um 22:43 schrieb Christian Fischer:
>>
>>> Hey there,
>>> i have some errors while starting James ...
>>> I hope somebody can help me.
>>>
>>> Thanks in advantage !
>>>
>>> INFO  22:41:18,520 |
>>> org.apache.james.container.spring.context.JamesServerApplicationContext |
>>> Refreshing
>>> org.apache.james.container.spring.context.JamesServerApplica
>>> tionContext@31a5c39e:
>>> startup date [Sun Jan 01 22:41:18 CET 2017]; root of context hierarchy
>>> DEBUG 22:41:24,319 |
>>> org.apache.james.container.spring.context.JamesServerApplicationContext |
>>> Bean factory for
>>> org.apache.james.container.spring.context.JamesServerApplica
>>> tionContext@31a5c39e:
>>> org.springframework.beans.factory.support.DefaultListableBea
>>> nFactory@54d1608f:
>>> defining beans
>>> [org.springframework.context.annotation.internalConfiguratio
>>> nAnnotationProcessor,org.springframework.context.annotation.
>>> internalAutowiredAnnotationProcessor,org.springframework.con
>>> text.annotation.internalRequiredAnnotationProcessor,org.
>>> springframework.context.annotation.internalCommonAnnotationProcessor,org.
>>> springframework.context.annotation.internalPersistence
>>> AnnotationProcessor,org.springframework.context.
>>> annotation.CommonAnnotationBeanPostProcessor#0,org.
>>> springframework.orm.jpa.support.PersistenceAnnotationB
>>> eanPostProcessor#0,org.apache.james.container.spring.
>>> lifecycle.LogEnabledBeanPostProcessor#0,logprovider,org.
>>> apache.james.container.spring.bean.factorypostprocessor.Conf
>>> igurationBeanFactoryPostProcessor#0,org.apache.james.contain
>>> er.spring.lifecycle.ConfigurableBeanPostProcessor#0,
>>> configurationprovider,mailrepositorystore,mailetloader,
>>> matcherloader,protocolhandlerloader,org.apache.james.
>>> container.spring.bean.factorypostprocessor.FileSyste
>>> mBeanFactoryPostProcessor#0,filesystem,sieveparser,configu
>>> rationmanager,authenticator,mailqueuefactory,broker,amqConne
>>> ctionFactory,blobTransferPolicy,jmsConnectionFactory,jmsTran
>>>